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.
Install
npx skills add eshmith7/claude-skills-library --skill tech-postmortemgit 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-postmortemPersonal 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
Details
- Skill name
tech-postmortem- Repository
- eshmith7/claude-skills-library
- 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
Content Brief
5eshmith7/claude-skills-library
Turn a vague content request into a brief a writer can execute without a second conversation: one question, reader, intent, angle, structure, evidence required. Use for content briefs.
Content Performance Audit
5eshmith7/claude-skills-library
Turn a performance export into one decision per asset: keep, refresh, rewrite, consolidate or delete, with cannibalisation groups found first. Use for content audits or pruning.
Content Prepublication Check
5eshmith7/claude-skills-library
Check a draft before publishing: every claim registered with its source, numbers verified, headline against body, originality and compliance flags. Use before anything goes out.
Tech Rollout Plan
5eshmith7/claude-skills-library
Classify a change by reversibility, phase it by blast radius, and set abort criteria and a tested rollback before it starts. Use for rollouts, migrations or cutovers.
Ops Supplier Scorecard
5eshmith7/claude-skills-library
Turn PO and receipt data into a supplier scorecard on OTIF, lead time variability, quality, price and dependency risk. Use for vendor reviews, supplier performance or consolidation.
Tech Status Brief
5eshmith7/claude-skills-library
Turn technical facts into a brief a non-technical reader can decide from, with the consequence first, hypotheses separated from what is known. Use for exec updates or escalations.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.