incident-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.
incident-postmortem from khaledsaeed18/dotclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add khaledsaeed18/dotclaude/incident-postmortem@git:20260921.8d3f9ebPins git:20260921.8d3f9eb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- khaledsaeed18/dotclaude
- Path
skills/engineering/incident-postmortem/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260921.8d3f9eb, committed Sep 21, 2026
- Size
- 4,384 bytes
- Repository stars
- 5
- License
- MIT
Write a blameless incident postmortem from the timeline, logs, chat transcripts, and the fix: impact with numbers, a minute-by-minute timeline, root cause as a chain of contributing factors rather than a single culprit, what went well and what did not in detection and response, and action items with owners and dates that address the causes rather than the symptom. Use after an outage, a data incident, a security event, or a near miss, or when an existing postmortem reads as blame or as a fix…
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
A postmortem exists so the same failure cannot happen the same way again. It is blameless because the person who typed the command is never the root cause; the system that let that command do damage is. Write it within a week, while the timeline is still recoverable. ## Gather - The timeline sources: alerts (first fired), chat channel export, deploy log, commits, dashboards (screenshots with timestamps), customer reports, the incident ticket. - The fix: the PR or command that resolved it, and when the symptom cleared. - Metrics for impact: requests failed, users affected, duration, data affected, revenue or SLO budget consumed. Convert every timestamp to one timezone (UTC) with the local offset stated once. ## Structure ```markdown # Postmortem: <short title> (INC-1234) Date of incident: 2026-09-18 | Duration: 47 min (14:03 to 14:50 UTC) | Severity: SEV2 Authors: ... | Reviewed: ... | Status: action items open (3 of 5) ## Summary Three sentences: what broke, who it affected and how much, what fixed it. ## Impact …
Read the whole file at its exact version.
How to install
mdr add khaledsaeed18/dotclaude/incident-postmortem@sha256:65aefd205596ce62The line at the top of this page pins the label git:20260921.8d3f9eb, 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_z3hxwhsv4nscvb2s)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 21, 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 (4384 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
khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z3hxwhsv4nscvb2s GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/incident-postmortem GET https://markdownregistry.com/api/v1/blob/65aefd205596ce6298e2a946da93fc6efe607d42e9660073e8d8862ef18dc259
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 khaledsaeed18/dotclaude
Every file in khaledsaeed18/dotclaude