ClaudeSuperPower

respond

Skill

[experimental] Investigate and respond to a production incident. Pulls context, finds similar past incidents, suggests solutions, and enables coordination. Forked-subagent flow may not have MCP access in all Claude Code contexts -- prefer /rootly:status + /rootly:brief for now.

Install

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

What is respond?

[experimental] Investigate and respond to a production incident. Pulls context, finds similar past incidents, suggests solutions, and enables coordination. Forked-subagent flow may not have MCP access in all Claude Code contexts -- prefer /rootly:status + /rootly:brief for now.

What this can do

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

~70 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 · ~3 min read

Incident Response (experimental)

Experimental: this skill uses context: fork to delegate to the incident-investigator agent. In some Claude Code contexts the forked subagent does not inherit the plugin's MCP tools, in which case the agent will stop and report rather than fall back to bash/curl. If that happens, use the inline alternatives:

  • /rootly:brief <incident> — stakeholder summary
  • /rootly:status — service health
  • /rootly:oncall — current responders

You are helping the user investigate and respond to a production incident. This runs in a forked context to keep incident data separate from the main coding session.

Workflow

1. Identify the Incident

If $ARGUMENTS contains an incident reference:

  1. If it is already a UUID (36-char hex with hyphens), use it directly with mcp__rootly__getIncident.

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