process-manager

Manage processes by PID across Windows, Linux, and macOS.

15|1|Updated Sep 13, 2025
One-click install
npx skills add https://github.com/EdanStarfire/claudecode_webui --skill process-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-manager
Source: https://github.com/EdanStarfire/claudecode_webui/tree/main/.claude/skills/process-manager
Command: npx skills add https://github.com/EdanStarfire/claudecode_webui --skill process-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe and reliable way to start, monitor, and stop background processes by their unique Process ID (PID) across Windows, Linux, and macOS, preventing accidental termination of critical services and resolving port conflicts.

Core Features & Use Cases

  • PID-Based Control: Start processes in the background, find their PIDs, and terminate them precisely, avoiding dangerous name-based kills.
  • Port Conflict Resolution: Quickly identify and stop processes occupying a specific port, allowing you to start your desired application.
  • Cross-Platform Support: Utilize platform-specific commands (netstat, lsof, kill, taskkill) for consistent process management.
  • Use Case: When a test server fails to start because its port is already in use, use this Skill to identify the process occupying that port by its PID, then safely terminate it without affecting other running applications.

Quick Start

Start a Python server on port 8001 in the background, then find its PID and gracefully stop it, verifying its termination.

Frequently Asked Questions about process-manager

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

FAQPage Schema
How do I find and stop a process using a specific port on Windows or Linux?

Identify the process occupying a port using platform-specific commands: `netstat` on Windows or `lsof` on Linux/macOS to locate the PID, then terminate it safely by PID rather than by name to avoid killing unrelated services.

Why should I kill processes by PID instead of by name or pattern?

PID-based termination is precise and safe—it targets only the exact process you intend to stop, preventing accidental shutdown of critical services that share similar names or patterns across your system.

Can I start a background server and cleanly shut it down while verifying termination?

Yes. Start your process in the background, capture its PID, then use PID-based kill commands with post-action verification to confirm the process has terminated before attempting to restart or reassign its port.

How do I resolve port conflicts when starting a test server?

Query the port to find which process owns it by PID, safely terminate that process using platform-specific commands, and verify successful shutdown before launching your test server on the now-available port.

Does cross-platform process management work the same way on Windows, Linux, and macOS?

Process management requires platform-specific commands: Windows uses `taskkill`, while Linux and macOS use `kill` and `lsof`. This Skill abstracts those differences to provide consistent PID-based control across all three platforms.

What happens to orphaned processes, and how do I clean them up?

Orphaned processes remain in memory consuming resources. Locate them by port or PID using platform tools, then terminate them safely by PID to reclaim system resources and prevent port conflicts with new services.