incident-postmortem-writer
Skill50 starsChanged 21 days agoMITView on GitHub
Turns incident notes and timelines into a blameless postmortem with impact, root cause, timeline, what went well and action items. Use when the user needs to write up an outage, a failed deploy, a data problem or a security incident.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Amazon-Quick/Amazon-Quick-official-catalogtheir own version, first seen Oct 28, 2026
- 00PrabalK00/claude-skillstheir own version, first seen Mar 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Amazon-Quick/Amazon-Quick-official-catalog★ 50same name
- 00PrabalK00/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- api-endpoint-testerSkill
- changelog-generatorSkill
- commit-message-writerSkill
- cron-explainerSkill
- csv-profilerSkill
- docker-compose-reviewerSkill
- dockerfile-linterSkill
- env-file-auditorSkill
- git-conflict-resolverSkill
- json-diffSkill
- jwt-inspectorSkill
- log-analyzerSkill
- markdown-link-checkerSkill
- meeting-notes-to-actionsSkill
- openapi-summarizerSkill
- pr-description-writerSkill
- python-code-smellsSkill
- readme-doctorSkill
- regex-explainerSkill
- release-checklistSkill
- requirements-auditorSkill
- secure-code-reviewSkill
- skill-authorSkill
- sql-query-reviewerSkill
- todo-extractorSkill
- unit-test-writerSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 59
Never invent: Do not make up times, numbers, owners or causes.
- Distinctive: line 60
Find the system cause: Ask "why" until the answer is a missing check, a gap in monitoring or a weak default, not a human mistake.
- Distinctive: line 64
Keep secrets out: Remove tokens, customer data and internal hostnames that do not need to be shared.
- Distinctive: line 68
If the notes have no times, produce the format with the timeline marked "to be filled in" and list the questions that would fill it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Incident postmortem writer
A postmortem explains what happened and how to make it less likely, without blaming a person.
When to use
- The user pastes chat logs, alerts or notes from an incident and wants a write-up.
- A review meeting is coming and the document is not started.
- The user asks how to structure a postmortem.
Format
# Postmortem: <short title>
**Date:** YYYY-MM-DD **Duration:** Xh Ym **Severity:** SEV-N **Status:** draft
## Summary
Two or three sentences: what broke, who was affected, how it was fixed.
## Impact
Users or systems affected, for how long, with numbers when known (requests failed, orders lost).
## Timeline (UTC)
| Time | Event |
| --- | --- |
| 14:02 | Alert fired for elevated error rate |
## Root cause
The technical cause, then the contributing factors that let it happen or delayed detection.
## Detection and response
How it was noticed, how long it took, what slowed the response.
## What went well
## What went wrong
## Where we got lucky
## Action items
| Action | Owner | Due | Type (prevent, detect, mitigate) |
| --- | --- | --- | --- |Rules
- Blameless. Describe actions and systems, not people. Write "the deploy script did not check the schema", not "Sam forgot to check".
- Facts before conclusions. Build the timeline first from the sources. Mark gaps as unknown.
- Never invent. Do not make up times, numbers, owners or causes. Write
unknownorto be confirmed. - Find the system cause. Ask "why" until the answer is a missing check, a gap in monitoring or a weak default, not a human mistake.
- Action items must be checkable. Each has an owner and a date, and fixes one cause. Prefer few strong items over a long list.
- Keep secrets out. Remove tokens, customer data and internal hostnames that do not need to be shared.
Errors
If the notes have no times, produce the format with the timeline marked "to be filled in" and list the questions that would fill it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

