nw-post-mortem-framework
From the author
Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning
Install
npx skills add nWave-ai/nWave --skill nw-post-mortem-framework -a claude-code
Installs to .claude/skills/nw-post-mortem-framework/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
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 84
Security100
Provenance74
Maintenance85
Licence100
Adoption46
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.
- postmortem-writingwshobson/agentsWrite effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.Writing★ 41.6K
- premortemparcadei/Continuous-Claude-v3Identify failure modes before they occur using structured risk analysisOther★ 3.9K
- nw-fp-principlesnWave-ai/nWaveCore functional programming thinking patterns and type system foundations, language-agnosticOther★ 622
- recall-reasoningparcadei/Continuous-Claude-v3Search past reasoning for relevant decisions and approachesOther★ 3.9K
- nw-fp-domain-modelingnWave-ai/nWaveDomain modeling with algebraic data types, smart constructors, and type-level error handlingOther★ 622
- write-a-postmorteminkeep/open-knowledgeWrite 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.Writing★ 4.7K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in