postmortem SKILL.md skillA
postmortem from alirezarezvani/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alirezarezvani/claude-skills/postmortem@git:20261031.a0c7b8fPins git:20261031.a0c7b8f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alirezarezvani/claude-skills
- Path
c-level-advisor/executive-mentor/skills/postmortem/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261031.a0c7b8f, committed Oct 31, 2026
- First version recorded
- Mar 6, 2026
- Size
- 7,905 bytes
- Repository stars
- 29,490
- License
- MIT
Use after a failed launch, missed quarter or bad hire. Runs a blameless 5-Whys with a change register.
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
# /executive-mentor:postmortem — Honest Analysis of What Went Wrong **Command:** `/executive-mentor:postmortem <event>` Not blame. Understanding. The failed deal, the missed quarter, the feature that flopped, the hire that didn't work out. What actually happened, why, and what changes as a result. --- ## Why Most Post-Mortems Fail They become one of two things: **The blame session** — someone gets scapegoated, defensive walls go up, actual causes don't get examined, and the same problem happens again in a different form. **The whitewash** — "We learned a lot, we're going to do better, here are 12 vague action items." Nothing changes. Same problem, different quarter. A real post-mortem is neither. It's a rigorous investigation into a system failure. Not "whose fault was it" but "what conditions made this outcome predictable in hindsight?" **The purpose:** extract the maximum learning value from a failure so you can prevent recurrence and improve the system. --- ## The Framework ### Step 1: Define the Event Precisely Before analysis: describe exactly what happened. - What was the expected outcome? - What was the actual outcome? - When was the gap first visible? …
Read the whole file at its exact version.
How to install
mdr add alirezarezvani/claude-skills/postmortem@sha256:5d4072ed68a3a793The line at the top of this page pins the label git:20261031.a0c7b8f, 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_vlpm27g7pmardftg)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 6, 2026 and Oct 31, 2026, about one every 60 days. Its first recorded version is graded C and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261031.a0c7b8f latest | 2026-10-31 | a0c7b8f | 7,905 B | A | view · diff |
| git:20261030.b078bb8 | 2026-10-30 | b078bb8 | 7,900 B | A | view · diff |
| git:20260611.aecfb8e | 2026-06-11 | aecfb8e | 8,005 B | A | view · diff |
| git:20260309.8902ba7 | 2026-03-09 | 8902ba7 | 7,829 B | A | view · diff |
| git:20260306.e145ac4 | 2026-03-06 | e145ac4 | 7,731 B | C | 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 (7905 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
alirezarezvani/claude-skills · 29,490 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vlpm27g7pmardftg GET https://markdownregistry.com/api/v1/resolve?ref=alirezarezvani/claude-skills/postmortem GET https://markdownregistry.com/api/v1/blob/5d4072ed68a3a793636c45dacd78c012813115a08260e5fc903c0f9ffc43d6a6
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 alirezarezvani/claude-skills
Every file in alirezarezvani/claude-skills