incident-retrospective skillA
incident-retrospective is agent-read markdown (skill) from openhands/extensions: Create an automation that drafts incident retrospectives. Gathers incident-channel messages from Slack, collects linked tickets and follow-ups from Linear, and publishes a retrospective draft to Notion with a timeline, impact summary, root-cause hypotheses, and action items..
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 Retrospective Drafter Automation Set up an automation that drafts incident retrospectives by pulling data from Slack, Linear, and Notion. --- ## Prerequisites ### Required integrations All three MCP integrations must be installed in Settings → MCP: - **Slack MCP** — to gather incident-channel messages - **Linear MCP** — to collect linked tickets and follow-ups - **Notion MCP** — to publish the retrospective draft ### Information to collect Ask the user for: 1. **Incident identification** — how are incidents identified? (e.g. Slack channel naming convention like `#inc-*`, a Linear label, or manual trigger) 2. **Slack channels** — which channels contain incident chatter (e.g. `#incidents`, `#inc-*` pattern) 3. **Linear teams** — which Linear teams/projects to inspect for follow-up tickets 4. **Retrospective template** — what sections should the retro include? Default: Timeline, Impact, Root Cause, Action Items, Lessons Learned 5. **Notion destination** — which Notion database or page should receive the draft 6. **Trigger type** — manual dispatch, cron schedule, or triggered by an incident label being added --- ## Setup Workflow ### Step 1 — Verify MCP access …
Read the whole file at its exact version.
How to install
mdr add openhands/extensions/incident-retrospective@git:20260701.599cc4dmdr add openhands/extensions/incident-retrospective@sha256:bf99ca3938e3245bPin 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_yct6twsti3kgb5ow)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260701.599cc4d latest | 2026-07-01 | 599cc4d | 3,554 B | A | view · diff |
| git:20260604.d916b35 | 2026-06-04 | d916b35 | 3,338 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 (3554 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
openhands/extensions · 150 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yct6twsti3kgb5ow GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/incident-retrospective GET https://markdownregistry.com/api/v1/blob/bf99ca3938e3245be78cbb4638cbdea9d38f1f42ad051750a3a52bba92e953dc
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.