post-incident-review SKILL.md skillA
post-incident-review from better-isms/grcskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add better-isms/grcskills/post-incident-review@git:20261027.94f7f3ePins git:20261027.94f7f3e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- better-isms/grcskills
- Path
skills/tristan-roth/post-incident-review/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261027.94f7f3e, committed Oct 27, 2026
- First version recorded
- Oct 19, 2026
- Size
- 7,951 bytes
- Repository stars
- 56
- License
- MIT
Use this skill when an incident or a serious near miss is closed and the team must learn from it, or an auditor asks for lessons learned, and someone says "run the post-mortem", "post-incident review", "lessons learned", "retro on the outage", "blameless review", "root cause of the incident" or "what do we change after this breach". Builds the timeline from records before the meeting, runs a blameless discussion, finds the contributing factors, and turns them into a few owned, dated actions…
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
Use this after every SEV1 and SEV2, for a sample of SEV3s (one per recurring theme per quarter, with the reason it was picked recorded in the review), and for any near miss that would have been a SEV1. You get two files per incident in a new folder, `./post-incident-review/`: the written review with the timeline, what contributed and what went well (`<incident-id>-review.md`), and a spreadsheet you can open in Excel listing the follow-up actions with owner, due date and how to check each worked (`<incident-id>-actions.csv`). This skill drafts for a human to review and sign; this skill never marks a control effective. Hold the review within about five working days, while memory is fresh and before the next incident pushes it out. End `<incident-id>-review.md` with `## Not checked`: what this run did not read or could not open, what it assumed and what it did not verify, specific to this run. ## Inputs to gather …
Read the whole file at its exact version.
How to install
mdr add better-isms/grcskills/post-incident-review@sha256:73224c139bea2975The line at the top of this page pins the label git:20261027.94f7f3e, 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_y4egstd337lzbgrq)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 19, 2026 and Oct 27, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.94f7f3e latest | 2026-10-27 | 94f7f3e | 7,951 B | A | view · diff |
| git:20261019.20937b5 | 2026-10-19 | 20937b5 | 7,707 B | A | view · diff |
| git:20261019.3c6cd53 | 2026-10-19 | 3c6cd53 | 7,568 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 (7951 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
better-isms/grcskills · 56 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y4egstd337lzbgrq GET https://markdownregistry.com/api/v1/resolve?ref=better-isms/grcskills/post-incident-review GET https://markdownregistry.com/api/v1/blob/73224c139bea297576e24f4f6141bae68636cdce318b1b33164660d88ec072f7
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.