postmortem-writing SKILL.md skillA

postmortem-writing from higoralves/orc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add higoralves/orc/postmortem-writing@git:20261020.7a1f356

Pins git:20261020.7a1f356 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: higoralves/orc
Path: orc/skills/postmortem-writing/SKILL.md
Versions recorded: 2
Latest version: git:20261020.7a1f356, committed Oct 20, 2026
First version recorded: Aug 5, 2026
Size: 5,523 bytes
Repository stars: 7
License: MIT

Author blameless incident postmortems — timeline, root cause(s), contributing factors, action items.

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

> **Defer to `orc:doc-writing`** for the shared scaffolding: the doc-type map (postmortem vs PRD/TRD/RFC/ADR, and how it differs from `systematic-debugging`), the shared section outline, the publication & numbering convention, and the review gates. This skill carries only the postmortem-specific template, blameless rules, and tone. Note: postmortems are date-keyed, not monotonically numbered (see the publication note in `orc:doc-writing`).

A postmortem is the artifact that turns an incident into organizational learning. The fix lands in code; the postmortem lands in the team's collective memory.

## When to write one

Write one for:

- Any **customer-visible** incident (degraded service, errors, data loss, security event).
- Any incident that triggered an **on-call page**, regardless of customer impact.
- **Near-misses** caught before customer impact but caused by a real defect (a manual override, last-minute deploy revert, etc.).
- **Recurring incidents** of the same kind — even if individually minor, the recurrence itself is the incident.

Don't write a full postmortem for:
- Bugs caught in QA or by a pre-deploy CI signal
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add higoralves/orc/postmortem-writing@sha256:dc8f0b4238e847f9

The line at the top of this page pins the label git:20261020.7a1f356, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_44yjpu2vcnxqz675.svg)](https://markdownregistry.com/a/art_44yjpu2vcnxqz675)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Aug 5, 2026 and Oct 20, 2026, about one every 76 days.

version	committed	commit	size	audit
git:20261020.7a1f356 latest	2026-10-20	7a1f356	5,523 B	A	view · diff
git:20260805.600ee50	2026-08-05	600ee50	8,720 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5523 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

GitHub

higoralves/orc · 7 stars · license MIT · pushed 2026-11-06 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_44yjpu2vcnxqz675
GET https://markdownregistry.com/api/v1/resolve?ref=higoralves/orc/postmortem-writing
GET https://markdownregistry.com/api/v1/blob/dc8f0b4238e847f976eecf115e5e0daebb27567a13e49e096cd8a3ec77c3f379

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.