power-word-kill

Hard terminate a misbehaving process and document the kill decision.

105|13|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill power-word-kill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: power-word-kill
Source: https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/containment-and-intervention/power-word-kill
Command: npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill power-word-kill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End a misbehaving process immediately when graceful shutdown is not possible or has failed, preventing cascading failures and data loss.

Core Features & Use Cases

  • Immediate hard-termination of a runaway process or service.
  • Provides clear post-termination guidance: blast-radius assessment and incident seed.
  • Suitable for emergency containment scenarios where time is critical.

Quick Start

Identify the target process and execute the hard kill when graceful shutdown is not viable.

Frequently Asked Questions about power-word-kill

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

FAQPage Schema
How do I hard terminate a runaway process when graceful shutdown fails?

To hard terminate a runaway process when graceful shutdown fails, you execute an immediate kill command. This ensures instant shutdown to prevent cascading failures and data loss in emergency containment scenarios.

What is the difference between graceful shutdown and a hard process kill?

A graceful shutdown attempts to safely end a process, while a hard process kill forces immediate termination. Hard termination is applicable when graceful shutdown fails or during a security breach requiring instant containment.

When should I perform an emergency shutdown of a misbehaving process?

You should perform an emergency shutdown of a misbehaving process when it becomes a runaway, when graceful shutdown is not viable, or during a security breach requiring instant termination to prevent cascading failures.

What should I do after terminating a rogue process to assess the blast radius?

After terminating a rogue process, you must perform a blast-radius assessment and document the kill decision. This provides clear post-termination guidance and generates an incident seed for further analysis.

Can I use a hard kill to stop a runaway process without causing data loss?

Using a hard kill to stop a runaway process carries a risk of data loss because it forces immediate shutdown. However, it is necessary to prevent larger cascading failures when graceful shutdown is not an option.