Kill OS Processes and Docker Containers

VerifiedCaution

Terminates OS processes or Docker containers by PID, name, or container ID. Useful for freeing blocked ports, killing resource-heavy processes, or stopping lingering containers. Supports both graceful stop and force kill.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude CodeCursorWindsurf
#process-management#docker#troubleshooting#port-management

Recommended for

Automated summary

Terminates OS processes or Docker containers by PID, name, or container ID.

Strengths

  • Quickly frees blocked ports.
  • Handles both system processes and Docker containers.
  • Offers graceful and force termination options.

Limitations

  • Requires appropriate permissions for some system processes.
  • Can be dangerous if used without verification.
  • Does not cover other environments like Kubernetes pods.
When to use it

When a process or container blocks a port, consumes too many resources, or becomes unresponsive.

When not to use it

For fine-grained process management that requires dependency analysis or scheduled shutdown.

Security analysis

Caution
Quality score88/100

The skill grants the AI agent the ability to forcefully terminate processes and containers. While legitimate for development and system administration, these commands are powerful and could disrupt system stability if misapplied. The skill includes safety notes but the risk remains.

Findings
  • •Provides direct access to kill and pkill with wildcard, which could be used to terminate critical system processes if misused.
  • •Docker stop/kill can terminate containers that may be running important services.
How this analysis is made

Examples

Kill a process by PID
/kill 12345
Kill processes by name
/kill node
Free up a blocked port
/kill port 3000

name: kill description: Terminate OS processes or Docker containers by PID, name, or container ID allowed-tools:

  • Bash(kill *)
  • Bash(pkill *)
  • Bash(docker stop *)
  • Bash(docker kill *)
  • Bash(lsof *)
  • Bash(ps *)

Kill Skill

Terminate processes or Docker containers that are blocking ports, consuming resources, or otherwise interfering with development. Like a strike to a vital pressure point, this skill removes obstacles with clinical efficiency.

Capabilities

OS Process Management

  • Kill by PID: Terminate processes by PID: kill <pid> or kill -9 <pid> for force kill.
  • Kill by Name: Terminate processes by name: pkill <name> or pkill -9 <name> for force kill.
  • Find Port Owners: Find processes using a specific port: lsof -i :<port>.
  • List Processes: List running processes: ps aux or ps aux | grep <pattern>.

Docker Container Management

  • Stop Containers: Stop containers gracefully: docker stop <container>.
  • Kill Containers: Force kill containers: docker kill <container>.
  • List Containers: List running containers with docker ps to identify targets.

Usage Examples

Kill a process by PID:

/kill 12345

Kill processes by name (Area Sweep):

/kill node

Free up a blocked port (Free the Chi):

/kill port 3000

Stop a Docker container:

/kill container my-app

Safety Notes

  • Always attempt graceful termination before force kill.
  • Verify the target process/container before termination.
  • Be cautious with system processes. A true master knows which targets to avoid.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/kill-os-processes-and-docker-containers-mm5t8amt/download' --output '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md.part' && mv '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md.part' '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md' && test -s '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/kill' && cp -R '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt' '.claude/skills/kill'

Cursor
test -f '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md' && test -s '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/kill' && cp -R '.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt' '.cursor/skills/kill'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt'

openskills read 'kill-os-processes-and-docker-containers-mm5t8amt'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/kill-os-processes-and-docker-containers-mm5t8amt/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills