
Description
postmortem-writing is an agent skill from the wshobson/agents collection for writing blameless postmortems, the written reviews that follow an incident and turn it into lessons. A blameless postmortem looks at how a system and its processes allowed an incident to happen, rather than who made a mistake, which keeps people willing to report what happened. The skill covers the parts of a useful postmortem: a timeline of events, root cause analysis that looks for the contributing factors behind the trigger, and action items that are specific, owned and tracked so the same incident is less likely to recur. Its core concepts start with the blameless culture the rest of the document depends on. It applies when conducting post-incident reviews, writing postmortem documents, facilitating a blameless review meeting, identifying root causes and contributing factors, creating follow-up items that will actually be done, and building a habit of organizational learning from failure. The skill is useful to on-call engineers, site reliability teams and engineering managers who want incident reviews to improve the system rather than assign blame. The agent can draft the document from notes and a timeline, and the people who lived the incident should check the facts and decide the action items. It is installed with the skills CLI from the wshobson/agents repository. Its skills.sh page showed about 10.6K installs and passing results from three security audits at the time of the scan.…
Highlights
- Blameless postmortem structure
- Timelines of incident events
- Root cause and contributing factor analysis
- Specific, owned action items
- Guidance for facilitating review meetings
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate postmortem-writing.
People also visit
postmortem-writing FAQ
What is a blameless postmortem?
A review of an incident that looks at how the system and its processes allowed it, rather than who made a mistake.
What should a postmortem contain?
A timeline, root cause and contributing factors, and follow-up action items.
Can it draft the document?
The agent can draft a postmortem from notes and a timeline, and the people involved should check the facts.
Who decides the action items?
The team does. The skill helps write them as specific, owned follow-ups.
How do I install it?
Run npx skills add https://github.com/wshobson/agents --skill postmortem-writing.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best postmortem-writing alternatives?
Popular alternatives to postmortem-writing include on-call-handoff-patterns, chaos-engineer and sre-engineer. See all postmortem-writing alternatives






