Incident postmortem
AI-agent skills for software engineering — works with Claude Code, Codex, Cursor
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.
2 things to look at
- 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.2 KB, 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.
Gives 1 of the 12 instructions most incident response skills give
Counted across 224 of the 224 authors here whose files we hold, read 2026-08-06
- Conduct a blameless postmortem within 48 hoursin 24 of 224, across 14 files
- perform root cause analysis using five whyshere, and in 24 of 224, across 20 files
- write a blameless postmortemin 22 of 224, across 19 files
- Update stakeholders every 15 to 30 minutesin 19 of 224, across 9 files
- assign an owner and due date to every action itemin 18 of 224
- Classify incident severity within 5 minutesin 17 of 224, across 7 files
- Create a post-mortem documentin 17 of 224, across 14 files
- Assign all action items with deadlinesin 14 of 224, across 6 files
- Implement immediate mitigation prioritizing user restorationin 13 of 224, across 3 files
- assign one incident commanderin 12 of 224
- Stop and ask for clarification if inputs are missingin 10 of 224, across 2 files
- Escalate earlyin 10 of 224, across 2 files
Said here and by no other author read
- document incident to prevent recurrence
- summarize what happened in two sentences
- describe who and what was affected
- record timeline with timestamps
- review detection, tooling, and response effectiveness
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.