Incident postmortem
Write a blameless postmortem after a production incident. Use when documenting an outage or serious bug. Captures timeline, impact, root cause, and concrete follow-up actions — focused on systems, not people.From its SKILL.md
npx -y skills add vaibhavsaxena022/skills --skill incident-postmortemAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 171 tokens by cl100k_base, as published. Nobody here has run it
Incident Postmortem
Document the incident so the same class of failure can't recur.
Structure
- Summary — what happened, in two sentences.
- Impact — who/what was affected, for how long, and severity.
- Timeline — detection → diagnosis → mitigation → resolution, with timestamps.
- Root cause — the actual cause and contributing factors (use "5 whys").
- What went well / what didn't — detection, tooling, response.
- Action items — concrete, owned, dated fixes: prevention and faster detection.
Rules
- Blameless: describe systems and decisions, never blame individuals.
- The root cause is a why, not a who.
- Every action item is specific, assignable, and verifiable.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.