Skip to content
Skills Library
DevOps & cloud · Writing

postmortem

/postmortem

Use only when the user explicitly asks for a postmortem, RCA, or incident review after an incident is resolved.

Licence
MIT
Last repository change
15.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use only when the user explicitly asks for a postmortem, RCA, or incident review after an incident is resolved.

Original author description

Use only when the user explicitly asks for a postmortem, RCA, or incident review after an incident is resolved.

How it works

  1. Inputs
  2. Rules
  3. Anti-patterns to flag
  4. Output
  5. Workflow context
  6. Output contract
Original SKILL.md headings · 41 lines, 252 words
SKILL.md preview
---
name: postmortem
description: "Use only when the user explicitly asks for a postmortem, RCA, or incident review after an incident is resolved."
---

# Postmortem (blameless)

## Inputs
- Incident start and end time, and the incident log from `incident-response` if one exists
- Customer impact (who, how, how long)
- Symptoms, mitigation steps, and links to dashboards, logs, deploys

## Rules
1. **Systems, not people**: "the deploy process allowed an untested config change", not a name.
2. **Causes beyond the trigger**: ask why the system allowed it, why it was not caught, why it was not
   detected sooner. Record contributing factors separately from root causes.
3. **Precise timeline**: minute-level, in UTC, each entry with its source (log, deploy, alert, chat).
   Mark when impact started, when it was detected, when mitigated, and when resolved.
4. **Money and data incidents**: state which records or transactions were affected, how they were
   reconciled or corrected, and whether any remain open.
5. **Action items are specific, owned, dated, and verifiable**: "add a burn-rate page on checkout
   errors, owner Platform, due <date>, verified by a test alert". "Be more careful" is not an action.
6. **Near misses count**: record what almost went wrong.

## Anti-patterns to flag
- Blame language; a single root cause when contributing factors exist
- Action items without owner, date, or verification method
- No detection or response gap analysis

## Output
Fill `assets/postmortem.md`.

## Workflow context
- Follows `incident-response` once the incident is resolved; `debug-triage` supplies the investigation detail.
- Action items feed `monitoring-plan`, `runbook`, and `test-plan`.

## Output contract
```yaml
produces:
  - type: "postmortem"
    format: "markdown"
    path: "claudedocs/<feature>-postmortem.md"
    sections: [timeline, root_causes, contributing_factors, action_items]
```
Files in this package (3)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB
  • assets/postmortem.md 1 KB

Versions

RepositoryScoreLicence
This page · omexit/claude-skills-pack100MIT
duronext/jig100MIT
boshu2/agentops100Apache-2.0
fabioc-aloha/Alex_Skill_Mall100MIT
qa-aman/claude-skills100MIT
biliboss/skills90MIT
alecs5am/ralphy87Apache-2.0

Database snapshot: 13.11.2026 · package version 1c228c4ac084 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100incident-postmortem
    Write a blameless postmortem after a production incident is resolved. Use for an RCA, or when the user says postmortem/RCA/writeup. Produces timeline, 5-whys root cause, and tracked action items.
  • 100incident-postmortem
    Write a blameless postmortem after a production incident is resolved. Use for an RCA, or when the user says postmortem/RCA/writeup. Produces timeline, 5-whys root cause, and tracked action items.
  • 100incident-postmortem
    This skill should be used when the user shares an incident timeline, Slack/Teams thread, alert history, logs from an outage, or asks to "write a postmortem", "write an incident report", "RCA", "root cause analysis", "post incident review", "PIR", or "summarise this outage".…
  • 90incident-postmortem
    Write a blameless postmortem or incident report from logs, alerts, chat transcripts, tickets and notes. Use when the user says "write the postmortem", "incident report", "RCA", "what happened during the outage", or pastes an incident timeline or Slack thread.
  • 100incident-postmortem-template
    Manage incident postmortem template operations. Auto-activating skill for Technical Documentation. Triggers on: incident postmortem template, incident postmortem template Part of the Technical Documentation skill category. Use when working with incident postmortem template…
  • 100incident-postmortem
    Write a blameless postmortem from incident notes, chat logs, alerts and deploy history, with a UTC timeline, impact numbers, root cause and contributing factors, and owned, dated action items. Use after an outage or security incident is resolved, when the user shares incident…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.