write-a-postmortem SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
write-a-postmortem from inkeep/open-knowledge-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add inkeep/open-knowledge-skills/write-a-postmortem@git:20261014.2bb8524Pins git:20261014.2bb8524 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- inkeep/open-knowledge-skills
- Path
skills/starter-packs/software-lifecycle/write-a-postmortem/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261014.2bb8524, committed Oct 14, 2026
- First version recorded
- Aug 4, 2026
- Size
- 17,832 bytes
- Repository stars
- 17
- License
- MIT
Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec…
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
# Write a postmortem The platform `/open-knowledge` skill still governs every markdown operation here — folder scope, the read/write tool surface, linking, and preview. This skill layers postmortem craft on top of it; it does not replace those rules. A postmortem is not a status update and not a blame ledger. It is a durable, blameless reconstruction of one incident, built from evidence, that makes the system's failure mode legible and produces action items someone will actually verify. The value compounds only when postmortems that share a subsystem link to each other — that is how a repeat class stops being invisible. This pack scaffolds `proposals/`, `decisions/`, `specs/`, `postmortems/`, and `guides/` at the project root. Postmortems live in `postmortems/`, one file per incident, filename `YYYY-MM-DD-name.md`, template id `postmortem`. Action items that are guide-shaped produce `runbook` stubs in `guides/`. …
Read the whole file at its exact version.
How to install
mdr add inkeep/open-knowledge-skills/write-a-postmortem@sha256:6e935cbe8e1694caThe line at the top of this page pins the label git:20261014.2bb8524, 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_p4ufwb27hhotxvnd)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 4, 2026 and Oct 14, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.2bb8524 latest | 2026-10-14 | 2bb8524 | 17,832 B | A | view · diff |
| git:20260825.dda5ab1 | 2026-08-25 | dda5ab1 | 17,811 B | A | view · diff |
| git:20260824.159d280 | 2026-08-24 | 159d280 | 17,775 B | A | view · diff |
| git:20260813.be5d62e | 2026-08-13 | be5d62e | 17,798 B | A | view · diff |
| git:20260805.99a8b17 | 2026-08-05 | 99a8b17 | 17,831 B | A | view · diff |
| git:20260804.8a506ba | 2026-08-04 | 8a506ba | 17,828 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 (17832 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
inkeep/open-knowledge-skills · 17 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p4ufwb27hhotxvnd GET https://markdownregistry.com/api/v1/resolve?ref=inkeep/open-knowledge-skills/write-a-postmortem GET https://markdownregistry.com/api/v1/blob/6e935cbe8e1694ca5d933f9beee4e8de4723564943053e4c0f91eb052ebeacc3
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 inkeep/open-knowledge-skills
Every file in inkeep/open-knowledge-skills