ClaudeSuperPower
SubmitLog in

retro

Skill

[experimental] Generate a structured post-incident retrospective from incident data. Forked-subagent flow may not have MCP access in all Claude Code contexts.

1Monitoring

Install

git clone https://github.com/Rootly-AI-Labs/rootly-claude-plugin.git ~/.claude/skills/retro

What is retro?

[experimental] Generate a structured post-incident retrospective from incident data. Forked-subagent flow may not have MCP access in all Claude Code contexts.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

~40 tokens of context used while enabled, before you invoke anything

All declared tools (1)
mcp__rootly__*

Trust

74/100 · Good

3 factors scored below maximum

Documentation

README · ~2 min read

Retrospective Generator (experimental)

Experimental: this skill uses context: fork to delegate to the retro-analyst agent. In some Claude Code contexts the forked subagent does not inherit the plugin's MCP tools. If the agent reports MCP tools unavailable, use /rootly:brief <incident> for a basic incident summary instead.

You are generating a structured post-incident retrospective. The output should be copy-pasteable markdown.

Workflow

1. Get Incident Data

The incident ID should be provided in $ARGUMENTS. If not provided, ask the user for it.

  1. Call mcp__rootly__getIncident for the full incident record
  2. Check the incident status:
    • If status is started (still active), warn the user: "This incident is still active. Retrospectives are typically done after resolution. Continue anyway?" Wait for confirmation before proceeding.

2. Gather Context

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

cardputer-buddy

Iterate on the Cardputer-Adv MicroPython app bundle (Claude Buddy, Snake, Hello) after the device is already provisioned via m5-onboard. Use when the user wants to add a new app, push a single changed .py without re-flashing, watch device serial logs, or run a one-shot REPL command. Trigger on "add

32.8K stars

planning-with-files

Persistent file-based planning for AI coding agents and long-running tasks. Crash-proof markdown plans, session recovery after /clear and compaction, per-turn re-injection against context rot, deterministic completion gate. Manus-style. Claude Code, Codex, Cursor, Kiro, OpenCode and 60+ agents via the Agent Skills standard.

25.8K stars

troubleshoot

Diagnose and fix a failing or misbehaving Atomic Agents app — import errors, schema validation failures, empty or malformed LLM output, provider role/mode errors, history and context problems, MCP transport errors. Use when the user reports an error, traceback, or wrong behavior in atomic-agents cod

6.1K stars