Incident Response
SEV classification, incident command system, communication, and incident response procedures.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill incident-responsegit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/engineer-toolkit/skills/incident-response ~/.claude/skills/incident-responsePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Incident Response Responding to incidents systematically; minimizing impact, communicating clearly. ## Context You are responding to an incident. Classify severity; follow procedures. ## Domain Context - **SEV 1**: Critical; P1; all-hands; fix now - **SEV 2**: Major; P2; urgent; fix in minutes/hours - **SEV 3**: Minor; P3; normal; fix in hours/days - **ICS**: Incident Command System; roles: Commander, Comms, Tech Lead - **Status Page**: Communicate to users; keep it real-time ## Instructions 1. **Assess Severity**: How many users? Full outage? Degraded? 2. **Declare Incident**: Create incident in tools; set severity 3. **Assign Roles**: Commander (leads), Comms (external), Tech (diagnosis) 4. **War Room**: Video call; everyone muted except speaker 5. **Diagnosis**: What's broken? Which service? Root cause? 6. **Fix**: Rollback? Scale? Restart? Safest fix first 7. **Status Page**: Update regularly; users want to know status ## Anti-Patterns - No severity classification; treat everything as fire - Too many people in war room; noise, confusion - No commander; decisions by committee too slow - Not communicating to users; they imagine worse - Fixing without understanding cause; same bug tomorrow - Blaming person; focus on systems - Not documenting; can't learn ## Further Reading - Google SRE book on incident response - Blameless postmortems (Google SRE) - Incident Command System (FEMA)
Details
- Skill name
incident-response- Repository
- sethdford/claude-skills
- Path
engineer/engineer-toolkit/skills/incident-response/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Incident Response skill do?
SEV classification, incident command system, communication, and incident response procedures.
How do I install the Incident Response skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Incident Response popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Index Design
48sethdford/claude-skills
B-tree indexes, composite indexes, covering indexes, UNIQUE indexes, and index trade-offs.
Iam Policy Design
48sethdford/claude-skills
Design and implement least-privilege IAM policies for cloud and on-premise environments.
Input Validation Patterns
48sethdford/claude-skills
Design and implement input validation patterns (whitelisting, boundary checks, type validation) to prevent injection and buffer overflow attacks.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.