agent-incident-postmortem SKILL.md skillA
agent-incident-postmortem from mohitagw15856/pm-claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mohitagw15856/pm-claude-skills/agent-incident-postmortem@git:20261006.b9ea321Pins git:20261006.b9ea321 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mohitagw15856/pm-claude-skills
- Path
plugins/pm-agentops/skills/agent-incident-postmortem/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261006.b9ea321, committed Oct 6, 2026
- First version recorded
- Jul 1, 2026
- Size
- 5,565 bytes
- Repository stars
- 1,475
- License
- MIT
Run a blameless postmortem for an incident caused by an AI agent or LLM feature — hallucinated facts shipped to users, runaway tool use, prompt injection, cost blowouts, or wrong actions taken autonomously. Use when asked to write up an AI incident, analyse why an agent did something wrong, or produce corrective actions after an LLM failure. Produces a structured postmortem with trace reconstruction, a root-cause layer analysis, and corrective actions including a permanent regression case. For…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Agent Incident Postmortem Skill AI incidents differ from outages: the system didn't go down — it did something wrong, confidently, and maybe only once. This skill adapts blameless postmortem practice to nondeterministic systems, where "can we reproduce it?" needs traces, not just steps. ## What This Skill Produces - A **blameless postmortem document** with timeline and user/business impact - A **trace reconstruction** of what the agent saw, decided, and did - A **root-cause analysis across the AI failure layers** (not "the model hallucinated" as a conclusion) - **Corrective actions** — always including a new permanent case in the regression suite ## Required Inputs Ask for (if not already provided): - **What the agent did** and what it should have done - **The trace** — the full request: system prompt, context, tool calls and results, output. If no trace exists, that absence is itself a finding - **Blast radius** — how many users/requests, over what window, and whether it's ongoing - **Detection** — how it was noticed (user report? monitor? luck?) and how long after it started ## Root-Cause Layers …
Read the whole file at its exact version.
How to install
mdr add mohitagw15856/pm-claude-skills/agent-incident-postmortem@sha256:d10311599faebba9The line at the top of this page pins the label git:20261006.b9ea321, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wwoybauzptt7lzu7)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 1, 2026 and Oct 6, 2026, about one every 96 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.b9ea321 latest | 2026-10-06 | b9ea321 | 5,565 B | A | view · diff |
| git:20260701.241d773 | 2026-07-01 | 241d773 | 5,408 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5565 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mohitagw15856/pm-claude-skills · 1,475 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wwoybauzptt7lzu7 GET https://markdownregistry.com/api/v1/resolve?ref=mohitagw15856/pm-claude-skills/agent-incident-postmortem GET https://markdownregistry.com/api/v1/blob/d10311599faebba9922eb03f09225841fc9204ef00155f9c28dc5f5b2f4ef408
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from mohitagw15856/pm-claude-skills
Every file in mohitagw15856/pm-claude-skills