agentsclimarketplace

Incident log to postmortem

Skill alexzhu0/agent-ready-skills/skills/incident-log-to-postmortem

Ten practical AI-agent skills for turning messy work into clear context, evals, reviews, and launch-ready artifacts.

Install
npx -y skills add alexzhu0/agent-ready-skills --skill incident-log-to-postmortem

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.

What its author says it does

Copied from the file, not written here

Use when summarizing incident logs, outage timelines, status updates, alerts, or team notes into a clear postmortem with impact, timeline, root-cause candidates, and follow-up actions.

SKILL.md

1.5 KB, as published. Nobody here has run it

Incident Log To Postmortem

Purpose

Turn scattered incident material into a readable postmortem draft without overstating the root cause.

Fit

  • Use when incident evidence needs to become a postmortem draft or follow-up action list.
  • Do not use when the incident is still active and the priority is live mitigation.

Inputs

  • Incident timeline, alerts, logs, status updates, or chat notes.
  • Impact details, affected users, duration, and remediation steps if available.
  • Current uncertainty or disputed explanations.

Workflow

  1. Build a chronological timeline from earliest signal to recovery.
  2. Separate confirmed facts from hypotheses.
  3. Identify impact, detection, mitigation, recovery, and prevention gaps.
  4. List root-cause candidates with evidence and confidence.
  5. Convert prevention ideas into owner-ready follow-up actions.

Output

Produce Markdown with:

  • Incident Summary
  • Impact
  • Timeline
  • Root-Cause Candidates
  • What Worked
  • What Failed
  • Follow-Up Actions
  • Open Questions

Validation

  • Timeline entries include timestamps or clear ordering.
  • Root cause is not claimed when only candidates exist.
  • Impact is scoped to evidence.
  • Follow-up actions have owners or owner placeholders.
  • Blame language is removed; system factors are emphasized.

Gives 0 of the 12 instructions most incident response skills give

Counted across 224 of the 224 authors here whose files we hold, read 2026-08-06

  • Conduct a blameless postmortem within 48 hoursin 24 of 224, across 14 files
  • perform root cause analysis using five whysin 24 of 224, across 20 files
  • write a blameless postmortemin 22 of 224, across 19 files
  • Update stakeholders every 15 to 30 minutesin 19 of 224, across 9 files
  • assign an owner and due date to every action itemin 18 of 224
  • Classify incident severity within 5 minutesin 17 of 224, across 7 files
  • Create a post-mortem documentin 17 of 224, across 14 files
  • Assign all action items with deadlinesin 14 of 224, across 6 files
  • Implement immediate mitigation prioritizing user restorationin 13 of 224, across 3 files
  • assign one incident commanderin 12 of 224
  • Stop and ask for clarification if inputs are missingin 10 of 224, across 2 files
  • Escalate earlyin 10 of 224, across 2 files

Said here and by no other author read

  • List root-cause candidates with evidence
  • Convert prevention ideas into follow-up actions
  • Scope impact to evidence
  • Emphasize system factors over blame

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. 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.