blameless-post-mortem SKILL.md skillA
blameless-post-mortem from event4u-app/agent-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add event4u-app/agent-config/blameless-post-mortem@git:20260707.4f7f4a8Pins git:20260707.4f7f4a8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- event4u-app/agent-config
- Path
src/skills/blameless-post-mortem/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260707.4f7f4a8, committed Jul 7, 2026
- First version recorded
- Jun 15, 2026
- Size
- 7,809 bytes
- Repository stars
- 19
- License
- MIT
Use after an incident or outage is resolved — blame-free facilitation, root cause, corrective actions, memory write-back — even for a near-miss. Consumes the incident-commander skeleton.
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
# blameless-post-mortem > Facilitate a blame-free post-mortem after an incident or near-miss. > Consumes the `incident-commander` skeleton, derives or fills the root > cause, writes the corrective-action plan, and drafts an > `incident-learnings` memory candidate. Systems and processes are > examined — never individuals. ## When to use - An incident or outage is resolved and the team needs a structured write-up. - A near-miss happened and a post-mortem is being drafted (near-miss mode — same flow, different severity framing). - The `incident-commander` hands off a post-mortem skeleton (empty root cause is accepted — do not block on it). - German triggers: "Post-mortem", "Nachbesprechung", "was ist schiefgelaufen?", "Vorfallsanalyse". Do NOT use when: - The incident is still active — route to [`incident-commander`](../incident-commander/SKILL.md) first. - The goal is root-cause analysis only, no write-up needed — route to [`root-cause-frameworks`](../root-cause-frameworks/SKILL.md). - The concern is a future risk, not a past event — route to [`risk-officer`](../risk-officer/SKILL.md). ## Procedure ### 1. Consume the incident-commander skeleton …
Read the whole file at its exact version.
How to install
mdr add event4u-app/agent-config/blameless-post-mortem@sha256:916c2a0ff401e05bThe line at the top of this page pins the label git:20260707.4f7f4a8, 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_g6vbptdl7t55lx72)
7 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 15, 2026 and Jul 7, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260707.4f7f4a8 latest | 2026-07-07 | 4f7f4a8 | 7,809 B | A | view · diff |
| git:20260706.dc79203 | 2026-07-06 | dc79203 | 7,707 B | A | view · diff |
| git:20260615.a7b44ad | 2026-06-15 | a7b44ad | 7,772 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 (7809 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
event4u-app/agent-config · 19 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_g6vbptdl7t55lx72 GET https://markdownregistry.com/api/v1/resolve?ref=event4u-app/agent-config/blameless-post-mortem GET https://markdownregistry.com/api/v1/blob/916c2a0ff401e05b8c6fbc6ac4ec9d265a22f87e1cfcf42bbb5baa88570f8db1
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.