Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

incident-postmortem · jnmetacode | DecimalAI

devopsby jnmetacode

incident-postmortem

jnmetacode/incident-postmortem

Source jnmetacode/skillet ↗License MIT

Write a blameless, actionable incident postmortem from the raw facts. Use after an outage/incident, or when asked to write up "what happened" for the team.

SkillScore91Maintained

Automatic

DevOps & SRE pack

Last verified 8/3/2026

What it changes

Passed 20 of 22 test cases with the skill, and 12 of 22 without it.

Without skill55%

With skill91%

Checks it passed that the model alone missed

Timeline timestamp entries explicitly include the time zone.
Every remediation item includes an assigned owner and a due date.
The root cause chain terminates at a broken or unverified assumption.

and 9 more in the full report

8 fixed12 passed either way2 still failing0 broke

Pass-rate lift: +36 pp
Tokens: +2%
Agent turns: 0%
Response time: -18%

Model gemini-3.6-flashMeasured 8/3/2026v120 of 22 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/jnmetacode-incident-postmortem/SKILL.md https://app.decimal.ai/s/jnmetacode-incident-postmortem/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add jnmetacode-incident-postmortem, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/jnmetacode-incident-postmortem/ and pins it in .decimal/skills.lock

decimalai skills add jnmetacode-incident-postmortem

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/jnmetacode-incident-postmortem/SKILL.md https://app.decimal.ai/s/jnmetacode-incident-postmortem/SKILL.md

Raw file: /s/jnmetacode-incident-postmortem/SKILL.md ↗ · machine-readable summary at /s/jnmetacode-incident-postmortem.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 8

Prompt

We just wrapped up our response to an incident where our primary database partition ran out of disk space during peak hours yesterday, causing read/write failures across the customer portal for about 45 minutes. Here are the raw notes from our response channel: 14:02 UTC alert fired for high disk usage, 14:10 DB went read-only, 14:25 devops identified unrotated audit logs filling the volume, 14:47 logs purged and service fully restored. Please assemble these notes into a complete incident postmortem document detailing the event, timeline, root cause, and follow-up action items.

What was checked, without and with the skill
Checked	Without skill	With skill
The root cause uses a causal chain linked with explicit because statements ending at an underlying assumption.	Missed	Passed
The document includes a section explicitly addressing what went well or what got lucky.	Passed	Passed
Action items explicitly evaluate or test if each item would have helped on the documented timeline.	Missed	Passed

case-01 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md40 linessingle file

incident-postmortem

A postmortem exists to change the system, not to assign blame or to perform remorse. Optimize for the engineer two years from now who hits something similar at 3am.

Procedure

Timeline first, from artifacts. Build it from logs, alerts, deploy records and chat timestamps — not memory. Every entry: time (with zone), what happened, what was known at that moment. Mark detection, diagnosis, mitigation, resolution.
Impact, quantified. Who/what/how long/how many: "checkout failed for 12 customers over 3h; all recovered" beats "some users were affected".
Root cause as a causal chain, not a single line. Use "because" links: webhooks dropped → because the endpoint 500'd on duplicates → because a unique-constraint violation was treated as fatal → because the handler assumed Stripe never retries. The last "because" is usually an assumption, and assumptions are what you fix.
Blameless mechanically: name systems and decisions, not people. "The deploy script allowed a config-less rollout" — not "X forgot the config". If a person had to be careful for the system to be safe, that's the finding.
What went well / what got lucky. Luck is a finding too ("we noticed only because someone happened to be watching dashboards").
Action items that would have prevented or shortened THIS incident, each with an owner and a date. Test each one: "would this have helped on the timeline above?" If not, cut it. 3–5 strong items beat 15 aspirational ones.

Skeleton

# 2026-04-02 — Payments webhook outage (3h, 12 failed checkouts)

**Summary** (3 sentences: what broke, impact, fix)
**Timeline** (timestamped, detection → resolution)
**Root cause** (causal chain, ending at the broken assumption)
**What went well / what got lucky**
**Action items** (owner · due date · "would it have helped?")

Track record

Benchmark

20 / 22

test cases passed, vs 12 / 22 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/1/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

jnmetacode / skillet

skills/incident-postmortem/SKILL.md

View on GitHub ↗

License MITImported 8/1/2026Version v1

Other skills for the same job

Published skills whose descriptions closely match this one, with their headline benchmark lift.

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

incident-postmortem

Procedure

Skeleton

Track record

Benchmark

Adoption

SkillSafety

Source

Other skills for the same job

Related skills