postmortem-review-board SKILL.md skillA
postmortem-review-board from amey-thakur/ai-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amey-thakur/ai-skills/postmortem-review-board@git:20260728.fac4544Pins git:20260728.fac4544 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amey-thakur/ai-skills
- Path
skills/big-tech-processes/postmortem-review-board/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260728.fac4544, committed Jul 28, 2026
- First version recorded
- Jul 18, 2026
- Size
- 3,789 bytes
- Repository stars
- 14
- License
- MIT
Run an org-level board that grades incident postmortems against a quality bar, promotes cross-cutting fixes to owned work, and reads across incidents for trends. Use when your organization writes enough postmortems that reviewing them one at a time hides the systemic pattern.
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
# Postmortem review board One postmortem closes one incident. A board exists to see what a single document cannot: the third outage this quarter with the same trigger, the action items filed and never shipped, the failure class spreading quietly between teams. Without it, each team learns its lesson alone and the organization pays for the same lesson again at a higher price. ## Method 1. **Gate entry on severity and impact, never on volunteering.** Every SEV1 and SEV2, plus any incident above a stated customer or revenue threshold, comes to the board. Route lower severities to team-local review so the board reads the incidents that carry org-wide signal instead of drowning in all of them. 2. **Grade against a written rubric before the discussion starts.** A pass needs a real timeline, a root cause that survives "five whys" past the first human in the chain, contributing factors, and action items with named owners and dates. "Operator error" is where the analysis quit, not a root cause. Bounce failing writeups instead of workshopping them live. 3. **Keep it blameless, out loud and every time.** The board judges the system …
Read the whole file at its exact version.
How to install
mdr add amey-thakur/ai-skills/postmortem-review-board@sha256:1312f31e4f5cff18The line at the top of this page pins the label git:20260728.fac4544, 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_ybmlmgdg43ytvrer)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 18, 2026 and Jul 28, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260728.fac4544 latest | 2026-07-28 | fac4544 | 3,789 B | A | view · diff |
| git:20260718.ea9bc00 | 2026-07-18 | ea9bc00 | 3,785 B | A | view · diff |
| git:20260718.7c1285c | 2026-07-18 | 7c1285c | 3,622 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 (3789 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
amey-thakur/ai-skills · 14 stars · license MIT · pushed 2026-09-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ybmlmgdg43ytvrer GET https://markdownregistry.com/api/v1/resolve?ref=amey-thakur/ai-skills/postmortem-review-board GET https://markdownregistry.com/api/v1/blob/1312f31e4f5cff183b235b90eda1df1542f97e81f3d9c8f53fa7d5570373ac97
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.