Skills for Real Engineers. Straight from my .agents directory.
write-a-postmortem
Agent skill frominkeep/open-knowledge
Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use write-a-spec), record a decision (use record-a-decision), or review a design (use review-a-design) — a postmortem documents an incident that already happened, it does not propose, specify, decide, or critique future work.
How to install write-a-postmortem
npx skills add inkeep/open-knowledge# or add only this skill to Claude Code: copy the folder
packages/server/assets/skills/packs/software-lifecycle/write-a-postmortem/
# into
~/.claude/skills/write-a-postmortem/ (all projects)
.claude/skills/write-a-postmortem/ (one project)
More skills in open-knowledge
Similar skill repositories
An agentic skills framework & software development methodology that works.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Public repository for Agent Skills
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
An AI skill that provides design intelligence for building professional UI/UX across multiple platforms.
