mcpbeat

Incident Response

w95/incident-response

Triage and manage production incidents. Trigger with "we have an incident", "production is down", "something is broken", "there's an outage", "SEV1", or when the user describes a production issue needing immediate response.

360 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
134
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/w95/awesome-claude-corporate-skills --skill incident-response

The instruction itself

5 sections, as written by the author

Incident Response

Guide incident response from detection through resolution and postmortem.

Severity Classification

| Level | Criteria | Response Time |

|-------|----------|---------------|

| SEV1 | Service down, all users affected | Immediate, all-hands |

| SEV2 | Major feature degraded, many users affected | Within 15 min |

| SEV3 | Minor feature issue, some users affected | Within 1 hour |

| SEV4 | Cosmetic or low-impact issue | Next business day |

Response Framework

  • Triage: Classify severity, identify scope, assign incident commander
  • Communicate: Status page, internal updates, customer comms if needed
  • Mitigate: Stop the bleeding first, root cause later
  • Resolve: Implement fix, verify, confirm resolution
  • Postmortem: Blameless review, 5 whys, action items

Communication Templates

Provide clear, factual updates at regular cadence. Include: what's happening, who's affected, what we're doing, when the next update is.

Postmortem Format

Blameless. Focus on systems and processes. Include timeline, root cause analysis (5 whys), what went well, what went poorly, and action items with owners and due dates.

How to use it

Copy the folder

Take w95/incident-response from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.