agentsclimarketplace
Sign in

Incident postmortem builder

Skill sisodiabhumca/agent-skills/skills/incident-postmortem-builder

Use after a production incident to build a blameless postmortem. Pulls timeline from PagerDuty/Slack/observability, computes MTTD/MTTR, drafts impact, root cause, contributing factors, and action items.From its SKILL.md

Install
npx -y skills add sisodiabhumca/agent-skills --skill incident-postmortem-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 336 tokens by cl100k_base, as published. Nobody here has run it

Incident Postmortem Builder

When to invoke

  • "Write the postmortem for INC-1234."
  • "Draft a blameless postmortem from this Slack timeline."
  • "Compute MTTD/MTTR for the May 3 outage."

Inputs needed

  1. Incident ID / title
  2. Timeline source — Slack export, PagerDuty incident, or a CSV (timestamp,event,actor)
  3. Impact data — affected services, % users, revenue impact (if known)
  4. Detected at / mitigated at / resolved at

Workflow

  1. Build timeline — normalize timestamps, attach actors and sources.
  2. Compute metrics — TTD, TTM, TTR, customer-minutes lost.
  3. Five-whys + contributing factors — guided prompts; never blame people.
  4. Action items — each must have owner, due date, type (prevent / detect / mitigate).
  5. Render — Markdown postmortem ready for the doc.

Output format

Standard SRE postmortem: Summary, Impact, Timeline, Detection, Response, Root cause, Contributing factors, What went well, What went wrong, Action items.

Guardrails

  • Blameless language — describe systems and decisions, never individuals.
  • Every action item MUST have owner + due date + type.
  • TTR/TTM/TTD must be computed from timestamps, never approximated.

Reference code

build.py ingests a timeline CSV (or Slack export JSON) and renders the postmortem.

What ships with it: 2 files

5.8 KB alongside SKILL.md, 1 of them executable

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.