agentsclimarketplace

Postmortem writing

Skill charlieviettq/awesome-agent-skill/.cursor/skills/reliability-ops/postmortem-writing

Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).

Install
npx -y skills add charlieviettq/awesome-agent-skill --skill postmortem-writing

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

  • 22 stars22 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

Write blameless incident postmortems—timeline, impact, root cause, contributing factors, and actionable follow-ups. Use after outages, SEV incidents, or significant near-misses. Triggers: "postmortem", "incident review", "RCA", "blameless", "SEV".

SKILL.md

1.6 KB, as published. Nobody here has run it

Postmortem writing

Principles

  • Blameless — focus on systems and process, not individuals.
  • Accurate — timeline in UTC with evidence (logs, deploys, tickets).
  • Actionable — every finding maps to owner + due date or ticket.

Required sections

  1. Summary — what happened, duration, user/business impact
  2. Timeline — detection, escalation, mitigation, recovery
  3. Root cause — technical chain; distinguish trigger vs underlying gap
  4. Contributing factors — process, monitoring, dependency, change management
  5. What went well
  6. Action items — prevent recurrence, improve detection, reduce blast radius

Timeline table

Time (UTC)Event
...Alert fired
...Mitigation applied
...Service restored

Action item quality

WeakStrong
"Be more careful""Add alert on queue depth > X with runbook"
"Improve testing""Integration test for failover path in service Y"

Severity-appropriate depth

  • SEV1/2: full postmortem + review meeting.
  • SEV3/4: lightweight doc still with timeline and actions.

Template

See reference.md for full markdown template.

Follow-up

Track action items to closure; link superseding ADRs or runbook updates.

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.