agentleFS
Sign inStart free
neurofooneurofoo/agent-skills/postmortem/SKILL.md

postmortem

Skill111 starsChanged 10 months agoMITView on GitHub

Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All times in [timezone].

    line 31

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blameless Post-Mortem

Conduct a thorough, blameless analysis of an incident to understand what happened and prevent recurrence.

Instructions

Work through each section systematically. Focus on systems and processes, not individuals. The goal is learning, not blame.

Output Format

Executive Summary

Incident: [One-line description] Date/Time: [When it occurred] Duration: [How long] Severity: [Critical/High/Medium/Low]

Summary [2-3 sentence overview: what happened, impact, resolution]

Timeline

All times in [timezone].

TimeEventActor
HH:MM[What happened][Who/what did it]
HH:MM[Detection][How it was noticed]
HH:MM[Response action][Who responded]
HH:MM[Resolution][What fixed it]

Key Moments

  • Trigger: [What initiated the incident]
  • Detection: [How/when we knew something was wrong]
  • Mitigation: [When bleeding was stopped]
  • Resolution: [When fully resolved]

Impact

Customer Impact

  • Users affected: [number]
  • Duration of impact: [time]
  • Symptoms experienced: [what users saw]

Business Impact

  • Revenue impact: [if applicable]
  • SLA/SLO breach: [yes/no, details]

Root Cause Analysis

Root Cause [The fundamental reason this happened—not the trigger, but why the trigger caused an incident]

Trigger [The immediate cause—what set things in motion]

Contributing Factors

FactorHow It Contributed
[factor][explanation]

Why Wasn't This Caught?

  • Why didn't tests catch it?
  • Why didn't monitoring alert earlier?

What Went Well

What WorkedWhy It Helped
[thing][explanation]

What Went Poorly

What FailedImpact
[thing][impact]

Action Items

Immediate (This week)

ActionOwnerDue
[action][owner][date]

Short-term (This month)

ActionOwnerDue
[action][owner][date]

Lessons Learned

  1. [lesson]
  2. [lesson]
  3. [lesson]

Guidelines

  • Blameless: "The deploy script didn't validate" not "Alice deployed without checking"
  • Thorough timeline: Include everything, even embarrassing delays
  • Specific actions: "Add memory alerting" not "Improve monitoring"
  • Assigned owners: Unowned actions don't happen

$ARGUMENTS

Download now (ZIP)

  • Other versions42 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 42

    1. dotnet/fsharp★ 4.3ksame name
    2. SethGammon/Citadel★ 927same name
    3. boshu2/agentops★ 452same name
    4. flonat/flonat-research★ 145same name
    5. Dimon94/dverity★ 107same name
    6. Dimon94/skills★ 107same name
    7. EthanReedLabs/sulde★ 99same name
    8. Hongyu-yu/matsci-ai-skills★ 19same name
    9. Hassaan146/claude-skills★ 18same name
    10. clonable-eden/cekernel★ 17same name

    32 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use hypothesis-driven-debugging, status-report and 9 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • Sturla22Skill

      hypothesis-driven-debugging

      Debug by ranking concrete hypotheses and running discriminating checks. Use when a bug is hard to localize, many plausible failure points exist, logs are noisy or misleading, a symptom appears intermittently, or trial-and-error edits haven't worked.

      Also in 3 projects that use this

    • AnthropicSkill

      status-report

      Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.

      Also in 3 projects that use this

    • seongjaeryuSkill

      organize

      Organize knowledge into Sets

      Also in 3 projects that use this

    • SaluteYBSkill

      skill-eval

      Evaluate, tune, and regression-check AgentSkills. Use when creating a new skill or improving an existing one and you need structured should-trigger, should-not-trigger, boundary-case, and execution-quality examples. Also use when auditing overlapping skills and sharpening trigger descriptions before release.

      Also in 3 projects that use this

    • AnthropicSkill

      incident-response

      Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

      Also in 4 projects that use this

    • OpenAISkill

      threat-model

      Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

      Also in 3 projects that use this

  • In this repository22 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free