New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Incident Retrospective

by OpenHands in OpenHands/extensions

Create an automation that drafts incident retrospectives. An agent skill from OpenHands/extensions.

MITAuto-check passedProduct & Project Management

Install Incident Retrospective

skills CLI
$ npx skills add OpenHands/extensions --skill incident-retrospective -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install OpenHands/extensions incident-retrospective --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/incident-retrospective .claude/skills/incident-retrospective && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
incident-retrospective
GitHub stars
158
Token cost
~922 tokens
SKILL.md length
356 words
Files
6
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Create an automation that drafts incident retrospectives. An agent skill from OpenHands/extensions.

  • Works in 5 steps: Verify MCP access → Determine trigger type → Build the retro prompt → …
  • Tasks that involve Runbooks and postmortems
  • SKILL.md covers Prerequisites and Setup Workflow
  • Calls curl; needs OPENHANDS_API_KEY and OPENHANDS_AUTOMATION_API_KEY

What it does

Incident Retrospective is an agent 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.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `.plugin/plugin.json`, `README.md` and `commands/incident-retro-setup.md`).

It sits in Product & Project Management, covering Runbooks and postmortems, Retrospectives and Root cause analysis. It works with Notion, Slack and Model Context Protocol. The repository describes itself as: Public registry for OpenHands extensions. The licence is MIT.

When your agent uses it

  • Tasks that involve Runbooks and postmortems
  • Tasks that involve Retrospectives
  • Tasks that involve Root cause analysis

Example prompts

  • “/incident-retrospective”

Requirements

  • A credential in OPENHANDS_API_KEY
  • A credential in OPENHANDS_AUTOMATION_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Verify MCP access
  2. Determine trigger type
  3. Build the retro prompt
  4. Create the automation
  5. Confirm

What it can do on your machine

Read from SKILL.md and the folder at commit d008b81. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENHANDS_API_KEY
    • OPENHANDS_AUTOMATION_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Incident Retrospective loads about 922 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 356 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~922

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OpenHands/extensions at commit d008b81, republished under its MIT licence (© OpenHands). 356 words, ~922 tokens.

Download SKILL.mdSave it as .claude/skills/incident-retrospective/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
incident-retrospective
description
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.
triggers
/incident-retro:setup

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

Test each integration:

Use the Slack MCP to list recent messages in an incident channel.
Use the Linear MCP to list recent issues for the target team.
Use the Notion MCP to search for the destination database.

If any fail, tell the user which integration needs to be installed first.

Step 2 — Determine trigger type

Ask the user how retros should be triggered:

  • Manual — dispatch from the automations page when an incident wraps up
  • Cron — run daily/weekly to check for recent incidents
  • Event — triggered by a Linear label change or Slack message
Show full SKILL.md (142 more words)Show less
Step 3 — Build the retro prompt

Construct a prompt that includes:

  • How to identify the incident (channel pattern, label, etc.)
  • Which Slack channels and Linear teams to query
  • The retrospective template/sections
  • Where to publish in Notion
Step 4 — Create the automation

Set OPENHANDS_HOST and AUTH_HEADER for the request below:

  • OpenHands Cloud or Enterprise - a <HOST> value is in your system prompt: use it as OPENHANDS_HOST, with AUTH_HEADER="Authorization: Bearer $OPENHANDS_API_KEY"
  • Local Agent Canvas - an Automation backend is listed in <RUNTIME_SERVICES>: use its url_from_agent as OPENHANDS_HOST, with AUTH_HEADER="X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY"

Use the prompt preset endpoint:

bash
curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \
  -H "$AUTH_HEADER" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Incident Retrospective Drafter",
    "prompt": "<constructed retro prompt>",
    "trigger": <trigger config from step 2>
  }'

PowerShell note: use curl.exe for this exact flag syntax, and replace ${OPENHANDS_HOST} / $AUTH_HEADER with $env:OPENHANDS_HOST / $env:AUTH_HEADER if running it natively.

Step 5 — Confirm

Tell the user:

✅ Incident Retrospective Drafter is running!

  • Automation ID: {id}
  • Incident source: {identification method}
  • Slack channels: {channels}
  • Linear teams: {teams}
  • Notion destination: {destination}
  • Trigger: {trigger description}

© OpenHands, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files in skills/incident-retrospective of OpenHands/extensions.

  • SKILL.md
  • .claude-plugin
  • .codex-plugin
  • .plugin/plugin.json
  • README.md
  • commands/incident-retro-setup.md

Open the folder on GitHubat commit d008b81

Compare with similar skills

Incident Retrospective next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Incident Retrospective compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Incident Retrospective this skillOpenHands/extensions158—~922Automated safety check: PassMIT
After Action Reportrampstackco/claude-skills9401 repos~2.5kAutomated safety check: PassMIT
Launch Retro Analyzeraaron-he-zhu/aaron-marketing-skills2.9k—~3kAutomated safety check: PassApache-2.0
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
66 Crisis Playbook Globalminhnv0807/ai-business-skills608—~2.8kAutomated safety check: PassMIT
ComposioComposioHQ/composio30k1 repos~1.7kAutomated safety check: PassMIT

Similar skills

  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    940 GitHub starsUsed in 1 repo~2.5k tokens
    Product & Project ManagementAuto-check passed

  • Launch Retro Analyzer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "run a launch retro / post-mortem", "compare launch results vs targets by channel", or "decide what to keep or kill for the next launch"; produces a…

    2.9k GitHub stars~3k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • 66 Crisis Playbook Global

    minhnv0807/ai-business-skills

    A skill your agent uses when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an…

    608 GitHub stars~2.8k tokensUpdated 26 days ago
    Product & Project ManagementAuto-check passed

  • Composio

    ComposioHQ/composio

    Route and complete Composio work across Composio For You and Composio Platform.

    30k GitHub starsUsed in 1 repo~1.7k tokens
    Productivity & AutomationAuto-check passed

  • Claap Weekly Recap

    Othmane-Khadri/YALC-the-GTM-operating-system

    Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.

    317 GitHub stars~5.4k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

More from OpenHands/extensions

All 78 skills in this repo

  • GitHub

    OpenHands/extensions

    Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUBTOKEN environment variable and GitHub CLI.

    158 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • Agent Readiness Report

    OpenHands/extensions

    Evaluate how well a codebase supports autonomous AI-assisted development.

    158 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Discord

    OpenHands/extensions

    Build and automate Discord integrations (bots, webhooks, slash commands, and REST API workflows).

    158 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • GitHub Issue To PR

    OpenHands/extensions

    Create an automation that implements GitHub issues when a configurable trigger label is applied.

    158 GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • GitHub Repo Monitor

    OpenHands/extensions

    This skill should be used when the user asks to "monitor a GitHub repository", "watch GitHub for issues or PRs", "respond to @OpenHands mentions on GitHub", "set up an OpenHands GitHub integration"…

    158 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • GitLab Issue To Mr

    OpenHands/extensions

    Create an automation that implements GitLab issues when a configurable trigger label is applied.

    158 GitHub stars~4.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Incident Retrospective

What does Incident Retrospective do?

Create an automation that drafts incident retrospectives. An agent skill from OpenHands/extensions. Incident Retrospective is an agent skill from OpenHands/extensions. Create an automation that drafts incident retrospectives.

When should I use Incident Retrospective?

Incident Retrospective fits situations like: tasks that involve Runbooks and postmortems; tasks that involve Retrospectives; tasks that involve Root cause analysis.

How do I install Incident Retrospective in Claude Code?

Run `npx skills add OpenHands/extensions --skill incident-retrospective -a claude-code`. Or copy the skill folder (skills/incident-retrospective in OpenHands/extensions) into .claude/skills/incident-retrospective in your project. Claude Code loads it when a task matches its description.

How do I install Incident Retrospective in Codex?

Run `npx skills add OpenHands/extensions --skill incident-retrospective -a codex`. Or copy the skill folder (skills/incident-retrospective in OpenHands/extensions) into .agents/skills/incident-retrospective in your project. Codex loads it when a task matches its description.

Can I use Incident Retrospective in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenHands/extensions --skill incident-retrospective -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/incident-retrospective, .gemini/skills/incident-retrospective, .github/skills/incident-retrospective and .opencode/skills/incident-retrospective in your project.

What does Incident Retrospective need to run?

Going by SKILL.md and its folder, Incident Retrospective needs the command-line tools its instructions call (curl) and credentials named OPENHANDS_API_KEY and OPENHANDS_AUTOMATION_API_KEY. Our summary lists: A credential in OPENHANDS_API_KEY; A credential in OPENHANDS_AUTOMATION_API_KEY.

Does Incident Retrospective access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Incident Retrospective safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Incident Retrospective use?

Incident Retrospective is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Incident Retrospective use?

About 922 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Incident Retrospective?

Skills that share tags, products or a category with Incident Retrospective: After Action Report (rampstackco/claude-skills, 940 stars), Launch Retro Analyzer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars) and 66 Crisis Playbook Global (minhnv0807/ai-business-skills, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Incident Retrospective?

OpenHands (a GitHub organization) maintains it in OpenHands/extensions, which has 158 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 7, 2026.

Source: OpenHands/extensions on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.