incident-retrospective SKILL.md skillA
incident-retrospective from openhands/extensions is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add openhands/extensions/incident-retrospective@git:20261002.6ffd7e1Pins git:20261002.6ffd7e1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- openhands/extensions
- Path
skills/incident-retrospective/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261002.6ffd7e1, committed Oct 2, 2026
- First version recorded
- Jun 4, 2026
- Size
- 3,724 bytes
- Repository stars
- 179
- License
- MIT
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.
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 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@sha256:aaf8c7ca51604e86The line at the top of this page pins the label git:20261002.6ffd7e1, 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_yct6twsti3kgb5ow)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 4, 2026 and Oct 2, 2026, about one every 60 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261002.6ffd7e1 latest | 2026-10-02 | 6ffd7e1 | 3,724 B | A | view · diff |
| git:20260701.599cc4d | 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 (3724 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 · 179 stars · license MIT · pushed 2026-11-08 · 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/aaf8c7ca51604e86f7c6f18324504a500e4d4456774977acb53d019ec77900c5
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.