agentleFS
Sign inStart free
CreativeActtechCreativeActtech/llm-skills/skills/example-skill/incident-post-mortem-generator/SKILL.md

incident-post-mortem-generator

Skill2 starsChanged 7 months agoMITView on GitHub

Generate standardized SRE incident reports and Root Cause Analysis (RCA). Use when users provide incident logs, timelines, or outage descriptions and need a professional post-mortem document.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    IF no timeline is provided:

    line 52
  2. Distinctive:

    ASK for the start and end times of the incident to calculate metrics.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Incident Post-Mortem Generator

Standardizes the transformation of chaotic incident data into professional, actionable Root Cause Analysis (RCA) reports based on SRE best practices.

🎯 When to Use

  • User shares a Slack log or timeline of a production outage.
  • User says: "Help me write the RCA for the database crash."
  • Do NOT use for real-time monitoring or alerting.
  • Do NOT use for performance tuning (use SQL Optimizer instead).

🧠 Core Workflow

Step 1 — Timeline Reconstruction Parse timestamps to identify: Time to Detection (TTD), Time to Acknowledgement (TTA), and Time to Resolution (TTR).

Step 2 — Impact Assessment Identify service unavailability percentages, user count affected, and data loss risks. Categorize severity (SEV-1 to SEV-3).

Step 3 — Root Cause Analysis (5 Whys) Iteratively analyze the failure chain (e.g., Human error -> Missing validation -> Faulty CI/CD).

Step 4 — Action Item Generation Generate "Preventative" (stop it happening again) and "Mitigative" (detect it faster) tasks.

📋 Output Format

{
  "incident_summary": "Summary of what happened",
  "metrics": { "ttd_mins": 0, "ttr_mins": 0, "severity": "SEV-1" },
  "root_cause": "Detailed technical explanation",
  "five_whys": ["...", "...", "..."],
  "action_items": [
    { "task": "Add health check", "priority": "high", "owner": "SRE" }
  ]
}

⚠️ Fallback Behavior

IF no timeline is provided:

  • ASK for the start and end times of the incident to calculate metrics.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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