SkillCurated by metahubEval warningsprompts

incident-postmortem

Name: incident-postmortem
Author: oxbshw

Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.

pinned to #7f8ee3cupdated 3 months ago

7/11Verified publisherCurated by MetaHubActively maintainedLicensedDocumentedStructuredClean repo

Ask your AI client: “install skills/incident-postmortem”.

Requires the metahub MCP server installed in your client. Set up MCP.

mh install skills/incident-postmortem

metahub 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.

Claim this repo

Stars

533

Last commit

3 months ago

7f8ee3c

Latest release

published

3 months ago

#ai
#ai-agent
#ai-agents
#fine-tuning
#finetuning-llms
#freamework
#llm
#llmops
#local-development
#mcp-server
#memory
#rag
#rag-chatbot
#voice-agent

Evaluation report

WarningsView full report

Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.7f8ee3c· 3 months ago

Documentation

4 passed1 warning

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.
Description 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)
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking

Release history

releasecurrent7f8ee3cwarn3 months ago

View on GitHub

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-runbook instead)
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.