incident-postmortem SKILL.md skillA
incident-postmortem from okhp3/skillz is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add okhp3/skillz/incident-postmortem@git:20260828.866dec6Pins git:20260828.866dec6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- okhp3/skillz
- Path
community/incident-postmortem/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260828.866dec6, committed Aug 28, 2026
- Size
- 7,349 bytes
- Repository stars
- 3
- License
- MIT
Use when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem. Triggers on phrases like "write a post-mortem", "incident review", "what went wrong", "outage report", "root cause analysis", or "RCA". Covers timeline reconstruction, contributing factor analysis, impact quantification, and action item generation with owners.
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
# Incident Post-Mortem Guide a team through writing a structured, blameless post-mortem after a production incident. The output is a document that builds shared understanding, identifies root causes without blame, and produces concrete action items to prevent recurrence. ## Blameless Principle Systems fail, not people. The goal is to understand HOW the incident happened — not WHO caused it. Avoid language like "X forgot to", "Y should have known". Use "the system did not", "the process lacked", "the alert did not fire". ## When to Use - Production outage or service degradation has been resolved - A significant near-miss occurred (would have been an incident if caught later) - User-facing errors, data loss, or SLA breach happened - Team wants to capture learnings before context fades **Not for:** Minor bugs caught in staging, planned maintenance windows, or incidents with no learning value. ## Input Requirements Gather these details before writing the post-mortem. Ask for anything missing: ### Incident Metadata - Incident title (short, descriptive) - Date and time of detection (with timezone) - Date and time of resolution - Severity / impact level (P1–P4 or equivalent) …
Read the whole file at its exact version.
How to install
mdr add okhp3/skillz/incident-postmortem@sha256:0492b8e05eba16cfThe line at the top of this page pins the label git:20260828.866dec6, 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_hhbiye34dximhgln)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 28, 2026.
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 (7349 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
okhp3/skillz · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hhbiye34dximhgln GET https://markdownregistry.com/api/v1/resolve?ref=okhp3/skillz/incident-postmortem GET https://markdownregistry.com/api/v1/blob/0492b8e05eba16cf045041b519536f906b06b278c77a0a33b4b947ed0b79176b
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.