Postmortem writing
Skill charlieviettq/awesome-agent-skill/.claude/skills/postmortem-writing
Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).
npx -y skills add charlieviettq/awesome-agent-skill --skill postmortem-writingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 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 blameless incident postmortems—timeline, impact, root cause, contributing factors, and actionable follow-ups. Use after outages, SEV incidents, or significant near-misses.
SKILL.md
1.5 KB, as published. Nobody here has run it
Postmortem writing
Principles
- Blameless — focus on systems and process, not individuals.
- Accurate — timeline in UTC with evidence (logs, deploys, tickets).
- Actionable — every finding maps to owner + due date or ticket.
Required sections
- Summary — what happened, duration, user/business impact
- Timeline — detection, escalation, mitigation, recovery
- Root cause — technical chain; distinguish trigger vs underlying gap
- Contributing factors — process, monitoring, dependency, change management
- What went well
- Action items — prevent recurrence, improve detection, reduce blast radius
Timeline table
| Time (UTC) | Event |
|---|---|
| ... | Alert fired |
| ... | Mitigation applied |
| ... | Service restored |
Action item quality
| Weak | Strong |
|---|---|
| "Be more careful" | "Add alert on queue depth > X with runbook" |
| "Improve testing" | "Integration test for failover path in service Y" |
Severity-appropriate depth
- SEV1/2: full postmortem + review meeting.
- SEV3/4: lightweight doc still with timeline and actions.
Template
See reference.md for full markdown template.
Follow-up
Track action items to closure; link superseding ADRs or runbook updates.