Tech Postmortem

Turn incident evidence into a timeline that reconciles, contributing factors in the plural, and action items that will actually happen. Use for postmortems, RCAs or incident reviews.

5 stars 1 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add eshmith7/claude-skills-library --skill tech-postmortem
Manual install
git clone --depth 1 https://github.com/eshmith7/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/tech-skills/tech-postmortem ~/.claude/skills/tech-postmortem

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Incident Postmortem

The postmortem gets written by the person who was up all night, three days later, for an audience that includes their manager. So it names one root cause, the timeline has holes where nobody was taking notes, and the actions are the five things somebody thought of in the meeting. Eight months later the same incident happens and nobody connects them.

## When to use this

Trigger on: postmortem, post-mortem, RCA, root cause analysis, incident review, incident report, blameless postmortem, five whys, problem record, "write up the incident", "what actually happened".

## Before you start

Required: the raw material. Alert timestamps, chat or bridge logs, deploy records, tickets, graphs described in words, and whatever people remember.

Ask, briefly:
1. **The timezone of every timestamp, and whether they are all in one.** Logs are UTC, chat is local, the pager is something else. This is the commonest defect in a postmortem and it invalidates every duration in the document.
2. Who was involved, by role. Roles go in the document. Names do not.
3. **What the user actually experienced, and for how long**, which is usually different from what the system did and is the number leadership cares about.
4. Whether this has happened before, and the earlier postmortem if so. A recurrence is a far more serious finding than a novel failure.
5. The audience: an internal review, a customer summary, or a client or regulator deliverable.

## Roles, not names
Read the full skill on GitHub

Details

Skill name
tech-postmortem
Path
tech-skills/tech-postmortem/SKILL.md
Repo updated
9 September 2026

FAQ

What does the Tech Postmortem skill do?

Turn incident evidence into a timeline that reconciles, contributing factors in the plural, and action items that will actually happen. Use for postmortems, RCAs or incident reviews.

How do I install the Tech Postmortem skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add eshmith7/claude-skills-library --skill tech-postmortem. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Tech Postmortem popular?

It lives in eshmith7/claude-skills-library, which has 5 GitHub stars and 1 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.