incident-postmortem
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
pinned to #7f8ee3cupdated 2 weeks ago
Ask your AI client: “install skills/incident-postmortem”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/incident-postmortemmetahub onboarded this repo on the author's behalf.
If you own github.com/oxbshw/LLM-Agents-Ecosystem-Handbook on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
533
Last commit
2 weeks ago
Latest release
published
- #ai
- #ai-agent
- #ai-agents
- #fine-tuning
- #finetuning-llms
- #freamework
- #llm
- #llmops
- #local-development
- #mcp-server
- #memory
- #rag
- #rag-chatbot
- #voice-agent
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.7f8ee3c· 2 weeks ago
Documentation
41Description quality
18 words · 112 chars — "Use after an incident is resolved — drafts a blameless postmortem from timeline …"
README is present and substantial
19,199 chars · 20 sections · 2 code blocks
Tags / topics declared
14 total — ai, ai-agent, ai-agents, fine-tuning, finetuning-llms, freamework (+8)
README has usage / example sectionswarn
README has no Usage / Example / Quick start / Installation heading at any level
Add a `# Usage`, `## Quick start`, or similar section so end users can copy/paste a working invocation. Code blocks alone work too if there are several.
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrent7f8ee3cwarn2 weeks ago
Contents
When to use
- After an incident with customer impact
- After a near-miss worth documenting
- For drills / GameDay exercises
When NOT to use
- Live incidents (use
incident-runbookinstead) - Pure private learnings (use a personal log)
Inputs
| Name | Type | Required | Notes |
|---|---|---|---|
timeline | text or paths | yes | Source notes, alert links, chat extracts |
severity | S0–S3 | yes | Severity at peak |
incident_id | string | yes | e.g. INC-2026-04-12-001 |
Outputs
postmortem.md with: Summary, Impact, Timeline, Direct cause, Contributing factors, What went well, What didn't, Action items.
Workflow
- Reconstruct the timeline (UTC), one row per notable event
- State impact in user-facing terms (requests failed, dollars lost, customers affected)
- Identify the direct cause in one sentence — what specifically broke
- List contributing factors (the conditions that made the incident possible / hard to mitigate)
- Separate what went well (genuine wins, not platitudes) and what didn't
- Owners + dates on every action item; hard fail if missing
- Tone: blameless. Describe systems failing, not people.
References
Success criteria
- Every action item has an owner and a date
- Direct cause is one sentence
- No names attached to fault; only roles / systems
- Timeline times in UTC
Failure modes
- Missing source data → list gaps explicitly; don't fill with guesses
- Conflicting timelines → record both, flag for review
Reviews
No reviews yet. Be the first.
Related
Browser Use
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
Gpt Researcher
An autonomous agent that conducts deep research on any data using any LLM providers
Guizang Ppt Skill
AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts, social covers, and a WebGL/low-power presentation runtime.
mh install skills/incident-postmortem