siteview-cleanup

Remove unused PipeCrew site-view server instances via port-based scanning.

16|2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/pipecrew-ai/pipecrew --skill siteview-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: siteview-cleanup
Source: https://github.com/pipecrew-ai/pipecrew/tree/main/skills/siteview-cleanup
Command: npx skills add https://github.com/pipecrew-ai/pipecrew --skill siteview-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminate surplus site-view servers left after重启Claude或UI会话。

Core Features & Use Cases

  • Discover and Kill Servers: Identifies all running site-view servers using a common probe method and kills their PIDs.
  • Preview before Deletion: Offers flags like --keep-port, --keep-run, --keep-latest, and --dry-run to prevent accidental server deletion. The default is --dry-run, showing what would be deleted.
  • Use Case: For cleaning up servers post-reboot without causing data loss or operational interruptions.

Quick Start

/siteview-cleanup

Frequently Asked Questions about siteview-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up obsolete site-view server instances left after a system restart?

To clean up obsolete site-view servers after a restart, this Skill scans running cluster instances by port and kills their PIDs. It defaults to a dry-run mode to safely show what will be removed before actual deletion.

Can I preview which site-view servers will be deleted before killing their processes?

Yes, you can preview site-view server deletion safely using the default --dry-run flag. This probe method shows exactly which running instances match the cleanup criteria without terminating any active processes.

How do I keep specific site-view servers running while removing unused ones?

You can keep specific site-view servers running by applying retention flags like --keep-port, --keep-run, or --keep-latest during the cleanup process. These flags prevent targeted instances from being killed.

What is the best way to manage PipeCrew site-view server cleanup without data loss?

The best way to manage PipeCrew site-view cleanup without data loss is running the process in dry-run mode first, then applying retention flags to protect active instances before executing port-based PID termination.

Why do I have surplus site-view servers running after restarting Claude or UI sessions?

Surplus site-view servers remain running after restarting Claude or UI sessions because previous operational processes are left active. This Skill identifies those unused instances via port scanning and removes them from the cluster.

Does the site-view cleanup process require any specific dependencies to run?

No, the site-view cleanup process requires no external dependencies to run. It independently identifies running PipeCrew instances through port-based scanning and manages process removal directly within the cluster environment.