Skip to content

write-a-postmortem

inkeep/open-knowledge ↗

From the author

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.

Install

npx skills add inkeep/open-knowledge --skill write-a-postmortem -a claude-code

Installs to .claude/skills/write-a-postmortem/ · Each command fetches the skill straight from GitHub with the open skills CLI.

No download: this skill’s licence (GPL-3.0) does not let us redistribute its files. The install commands fetch them from GitHub instead.

Want your agent to suggest skills while you type? See how to use skills from your IDE.

Safety checks on SKILL.md

No warnings.

Why 89

Security100
Provenance84
Maintenance100
Licence80
Adoption58

aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.

Similar skills

Closest to this one by what they do and when they are used.

Ratings & reviews

—

no reviews

Tried this skill? Rate it to help others. Sign in

    Discussion

    Join the discussion. Sign in