Incident Response
SkillMonitoring & opsTriage 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Incident Response skill
What this skill tells your AI
The instructions your AI receives, as published by w95/awesome-claude-corporate-skills in 08-it-engineering/incident-response/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 195
- Forks
- 49
- Last commit
- Feb 2026
Advanced
- Catalog kind
- skill
- Gateway key
incident-response-w95- Source
- github.com/w95/awesome-claude-corporate-skills