incident-postmortem SKILL.md skillA
incident-postmortem from fattain-naime/engineering-docs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fattain-naime/engineering-docs/incident-postmortem@git:20260717.2f82174Pins git:20260717.2f82174 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fattain-naime/engineering-docs
- Path
skills/incident-postmortem/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260717.2f82174, committed Jul 17, 2026
- First version recorded
- Jul 8, 2026
- Size
- 17,004 bytes
- Repository stars
- 6
- License
- MIT
Write a blameless post-incident review (post-mortem / RCA) that documents what happened, the timeline, root cause analysis, impact assessment, and concrete action items to prevent recurrence. Follows Google SRE blameless post-mortem culture.
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
## Purpose Produce a blameless post-mortem that captures what happened, why it happened at every causal layer, and what specific, measurable actions will prevent recurrence. **A post-mortem that blames a person is a post-mortem that will not be written honestly next time.** The goal is to find and fix system failures, not to assign individual culpability. ## Input **Works best with:** A description of the incident. **Also valuable:** Timeline of events, monitoring data, the alert that fired, what was done to mitigate, any on-call notes from the incident. **Example invocation:** `Write a post-mortem for the incident on 2026-07-09 where the payment gateway returned 500 errors for 22 minutes affecting 8% of payment attempts. The root cause was a database connection pool exhaustion triggered by a slow query introduced in the v2.3.0 deployment 2 hours earlier.` ## Key Concepts ### Blameless Culture (Google SRE) People do not cause incidents. **Systems do.** When an engineer makes a mistake that leads to an incident, the real questions are: - Why did the system allow that mistake to have this impact? - What alerting, testing, or deployment control would have prevented it? …
Read the whole file at its exact version.
How to install
mdr add fattain-naime/engineering-docs/incident-postmortem@sha256:57681d8a6b4a8397The line at the top of this page pins the label git:20260717.2f82174, 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_djet7klc7adosmnh)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 8, 2026 and Jul 17, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260717.2f82174 latest | 2026-07-17 | 2f82174 | 17,004 B | A | view · diff |
| git:20260712.59c5852 | 2026-07-12 | 59c5852 | 5,098 B | A | view · diff |
| git:20260712.7e3d1bb | 2026-07-12 | 7e3d1bb | 5,175 B | A | view · diff |
| git:20260709.03fe43c | 2026-07-09 | 03fe43c | 4,980 B | A | view · diff |
| git:20260708.a309efd | 2026-07-08 | a309efd | 4,096 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 (17004 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
fattain-naime/engineering-docs · 6 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_djet7klc7adosmnh GET https://markdownregistry.com/api/v1/resolve?ref=fattain-naime/engineering-docs/incident-postmortem GET https://markdownregistry.com/api/v1/blob/57681d8a6b4a83978a2efca182d3a96a924b3ab6c19f7323b84909e404532179
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 fattain-naime/engineering-docs
Every file in fattain-naime/engineering-docs