Post Mortem
thananon/9arm-skills
Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through.
Runs this framework's blameless postmortem workflow — reconstruct the incident timeline from evidence, drive five-whys to a mechanism-level root cause, and produce owner-and-due-date action items…
Install Postmortem
$ npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework postmortem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/operations/postmortem .claude/skills/postmortem && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "postmortem" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/operations/postmortem into .claude/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/operations/postmortemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework postmortem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/operations/postmortem .agents/skills/postmortem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "postmortem" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/operations/postmortem into .agents/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework postmortem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/operations/postmortem .cursor/skills/postmortem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "postmortem" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/operations/postmortem into .cursor/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dralgorhythm/claude-agentic-framework.git --path .claude/skills/operations/postmortem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework postmortem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/operations/postmortem .gemini/skills/postmortem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "postmortem" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/operations/postmortem into .gemini/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dralgorhythm/claude-agentic-framework postmortemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/operations/postmortem .github/skills/postmortem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "postmortem" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/operations/postmortem into .github/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dralgorhythm/claude-agentic-framework postmortem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dralgorhythm/claude-agentic-framework.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/operations/postmortem .opencode/skills/postmortem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "postmortem" agent skill from https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/operations/postmortem into .opencode/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
postmortem- GitHub stars
- 124
- Token cost
- ~708 tokens
- SKILL.md length
- 350 words
- Files
- 4
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- None found
At a glance
Runs this framework's blameless postmortem workflow — reconstruct the incident timeline from evidence, drive five-whys to a mechanism-level root cause, and produce owner-and-due-date action items…
- Works in 6 steps: Timeline — reconstruct from evidence:… → Root Cause — five-whys down to a… → Impact — fill the User Impact and… → …
- An incident just resolved
- SKILL.md covers Timing and Framing, Workflow, Handoffs and Resources, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Postmortem is an agent skill from dralgorhythm/claude-agentic-framework. Runs this framework's blameless postmortem workflow — reconstruct the incident timeline from evidence, drive five-whys to a mechanism-level root cause, and produce owner-and-due-date action items with a regression guard. Use when an incident just resolved, running an outage retrospective, writing a postmortem, or doing a "what went wrong" analysis.
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `evals/README.md`, `evals/evals.json` and `resources/postmortem.template.md`).
It sits in DevOps & Cloud, covering Runbooks and postmortems and Root cause analysis. The repository describes itself as: A More Effective Agent Harness for Claude.
When your agent uses it
- An incident just resolved
- Running an outage retrospective
- Writing a postmortem
- Doing a what went wrong analysis
Example prompts
- “what went wrong”
- “/postmortem”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Timeline — reconstruct from evidence: logs, deploy history, alert-firing times, dashboards. Cite the source for every row; "I remember it…
- Root Cause — five-whys down to a MECHANISM (a missing check, an untested path, an alert that never existed). Stop at a process/system…
- Impact — fill the User Impact and Business Impact tables with real numbers before writing prose. Unquantified impact under-motivates the…
- Action Items — every row needs an owner, a due date, and a tracking issue link. No row ships with any of the three blank.
- Prevention — the trigger identified in Root Cause becomes a test, an alert, or a hook. Pick the strongest rung the trigger can support on…
- File it — artifacts/postmortem_[incident-id].md, per CLAUDE.md's artifact table.
What it can do on your machine
Read from SKILL.md and the folder at commit 6436a20. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Postmortem loads about 708 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 350 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 350 words (~708 tokens).
“Work through resources/postmortem.template.md section by section — reference its actual headings, don't invent parallel ones.”
- name
- postmortem
- metadata.category
- encoded-preference
Files
SKILL.md and 3 other files in .claude/skills/operations/postmortem of dralgorhythm/claude-agentic-framework.
- SKILL.md
- evals/README.md
- evals/evals.json
- resources/postmortem.template.md
Open the folder on GitHubat commit 6436a20
Compare with similar skills
Postmortem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Postmortem this skilldralgorhythm/claude-agentic-framework | 124 | — | ~708 | Automated safety check: Pass | None | |
| Post Mortemthananon/9arm-skills | 3.2k | — | ~3.4k | Automated safety check: Pass | None | |
| Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan | 108 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Postmortemalirezarezvani/claude-skills | 28k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Conducting Post Incident Lessons Learnedmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Incident Postmortemgithub/awesome-copilot | 40k | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Post-Incident Debrief
VeryGoodOpenSource/vgv-wingspan
Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.
Postmortem
alirezarezvani/claude-skills
/em:postmortem — Honest analysis of what went wrong. An agent skill from alirezarezvani/claude-skills.
Conducting Post Incident Lessons Learned
mukul975/Anthropic-Cybersecurity-Skills
Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.
- Official
Incident Postmortem
github/awesome-copilot
A skill your agent uses when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem.
Quality Postmortem
petrkindlmann/qa-skills
Analyze escaped defects and test suite health through blameless postmortems.
More from dralgorhythm/claude-agentic-framework
All 20 skills in this repoSwarm Coordination
dralgorhythm/claude-agentic-framework
Rules for several agents sharing one repository: an orchestrator tracks work in two tiers, workers write to scratch files, and every handoff leaves a pointer to an artifact.
Threat Modeling
dralgorhythm/claude-agentic-framework
Finds security threats in a design with a STRIDE pass per component, rates severity and records fixes, with extra checks for AI agent and tool risks.
Architecture Decision Record Writer
dralgorhythm/claude-agentic-framework
Writes Architecture Decision Records with title, status, context, decision, rationale and consequences for significant technical choices, kept short and numbered.
Codebase Health Auditor
dralgorhythm/claude-agentic-framework
Runs a user-invoked, swarm-style audit of a whole codebase for SOLID and DRY violations, code smells, complexity, dead code and pattern consistency, with a prioritized report.
Dependency Upgrade Protocol
dralgorhythm/claude-agentic-framework
Sequences safe dependency upgrades: read the changelog, verify the version exists upstream, pin it, and keep major bumps in separate commits behind a full gate run.
Designing Systems
dralgorhythm/claude-agentic-framework
Produces this framework's ADR and system-design artifacts from bundled templates with trade-off analysis.
Related
Categories
Questions about Postmortem
What does Postmortem do?
Runs this framework's blameless postmortem workflow — reconstruct the incident timeline from evidence, drive five-whys to a mechanism-level root cause, and produce owner-and-due-date action items…. Postmortem is an agent skill from dralgorhythm/claude-agentic-framework. Runs this framework's blameless postmortem workflow — reconstruct the incident timeline from evidence, drive five-whys to a mechanism-level root cause, and produce owner-and-due-date action items with a regression guard.
When should I use Postmortem?
Postmortem fits situations like: an incident just resolved; running an outage retrospective; writing a postmortem; doing a what went wrong analysis.
How do I install Postmortem in Claude Code?
Run `npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a claude-code`. Or copy the skill folder (.claude/skills/operations/postmortem in dralgorhythm/claude-agentic-framework) into .claude/skills/postmortem in your project. Claude Code loads it when a task matches its description.
How do I install Postmortem in Codex?
Run `npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a codex`. Or copy the skill folder (.claude/skills/operations/postmortem in dralgorhythm/claude-agentic-framework) into .agents/skills/postmortem in your project. Codex loads it when a task matches its description.
Can I use Postmortem in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dralgorhythm/claude-agentic-framework --skill postmortem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/postmortem, .gemini/skills/postmortem, .github/skills/postmortem and .opencode/skills/postmortem in your project.
What does Postmortem need to run?
SKILL.md names no scripts, command-line tools or credentials: Postmortem is instructions for the agent only.
Does Postmortem access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Postmortem safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Postmortem use?
No licence was found for Postmortem or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Postmortem use?
About 708 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Postmortem?
Skills that share tags, products or a category with Postmortem: Post Mortem (thananon/9arm-skills, 3.2k stars), Post-Incident Debrief (VeryGoodOpenSource/vgv-wingspan, 108 stars), Postmortem (alirezarezvani/claude-skills, 28k stars) and Conducting Post Incident Lessons Learned (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Postmortem?
dralgorhythm (a GitHub user) maintains it in dralgorhythm/claude-agentic-framework, which has 124 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on July 24, 2026.
Source: dralgorhythm/claude-agentic-framework on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.