agentsclimarketplace
Sign in

Incident postmortem drafter

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

Vendor-neutral skill to draft a blameless incident postmortem from structured incident inputs (timeline, impact, contributing factors) and produce an actionable report.From its SKILL.md

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

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.6 KB, 301 tokens by cl100k_base, as published. Nobody here has run it

When to invoke

  • You have an outage/incident timeline and need a consistent postmortem draft.
  • You want to standardize incident write-ups across teams.

Inputs needed

  • Incident metadata: title, date/time, duration, severity.
  • Impact summary: customer impact, internal impact, key metrics.
  • Timeline of events (timestamp + event).
  • Contributing factors (optional) and what went well/poorly.
  • Action items (optional; can be generated placeholders).

Workflow

  1. Validate required fields and normalize timestamps.
  2. Derive key milestones (start, detection, mitigation, resolution).
  3. Summarize impact and customer communication.
  4. Generate a blameless narrative: what happened and why (avoid personal attribution).
  5. Produce corrective and preventive actions (CPAs) with owners and due dates if provided; otherwise create placeholders.

Output format

Markdown report with:

  • Summary
  • Customer impact
  • Timeline
  • Root cause / contributing factors (blameless)
  • Detection and response analysis
  • What went well / what didn’t
  • Action items (table)
  • Follow-ups and references

Guardrails

  • Do not assign blame to individuals; focus on systems and process.
  • If inputs are missing, call them out explicitly rather than inventing facts.
  • Keep timestamps and units consistent.

Reference code

  • postmortem_drafter.py reads a JSON incident file and writes a Markdown postmortem.

What ships with it: 2 files

9.7 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.