Incident Postmortem skillA
Incident Postmortem is agent-read markdown (skill) from wyre-ai/msp-claude-plugins: Assembling a blameless postmortem grounded in systems of record: timeline reconstruction merging the incident tool's event log with correlated observability anomalies (Sentry error spikes, Datadog/Grafana metric anomalies, including precursor signal that predates formal detection) and deploy history from connected platform connectors, all normalized to one stated timezone; the root-cause versus contributing-factor distinction and the test for telling them apart; and how to label a root cause tha.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Incident Postmortem ## Overview A postmortem is a reconstruction exercise, not a summary of memory. The value of a blameless postmortem comes entirely from how well it's grounded in actual system records — timestamps from the incident tool, error spikes from the observability stack, and the deploy that shipped twenty minutes before things went wrong. A postmortem built from what the on-call engineer remembers is faster to write and far less useful: it misses precursor signals, gets timestamps wrong across timezones, and tends to converge on whatever explanation feels intuitive rather than what the evidence actually shows. This skill assembles that reconstruction from the systems of record, and structures the analysis so contributing factors don't get collapsed into a single "root cause" that oversimplifies what actually happened. ## Anti-triggers - **Creating or editing a postmortem record in the vendor** — templates, action-item tracking, and Rootly's automatic timeline import are its own surface; use `rootly-postmortems`. This skill reconstructs the timeline from every connected system, including tools the incident record never saw. …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Incident Postmortem@git:20260804.5567c51mdr add wyre-ai/msp-claude-plugins/Incident Postmortem@sha256:a2948ab3c6c19dd9Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_qieph3ougi3uhris)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.5567c51 latest | 2026-08-04 | 5567c51 | 9,449 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 8,991 B | A | view · diff |
| git:20260714.8a673c4 | 2026-07-14 | 8a673c4 | 9,732 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 (9449 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
wyre-ai/msp-claude-plugins · 46 stars · license Apache-2.0 · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qieph3ougi3uhris GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Incident Postmortem GET https://markdownregistry.com/api/v1/blob/a2948ab3c6c19dd9b57a49521523b39f403bbba443e3f27c320b1b36a6303d17
Your agent 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.