Rootly for Claude Code
Install
npx skills add Rootly-AI-Labs/rootly-claude-plugingh skill install Rootly-AI-Labs/rootly-claude-plugingit clone --depth 1 https://github.com/Rootly-AI-Labs/rootly-claude-pluginSkills in this collection
- ActionRootly AI LabsManage incident action items from the terminal. Subcommands - list (default - your open action items) or add <incident> "<summary>" (create one on an incident). Use to capture follow-ups during or after an incident without opening the Rootly UI.
- AlertRootly AI LabsTriage a Rootly alert by short ID. Pulls the alert record, its event timeline, related alerts in the same group, and any incident the alert is attached to. Use when a page comes in and you want context before opening Rootly.
- AnnounceRootly AI LabsDraft a stakeholder-facing status update for an active incident, then post it after explicit confirmation. Useful for incident commanders pushing public-status-page or internal updates without opening the Rootly UI. Write action - never posts without confirming.
- AskRootly AI LabsAsk natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured answers.
- BriefRootly AI LabsGenerate a concise stakeholder brief for an incident. Creates executive summary with key details, impact, timeline, and current status.
- CoverRootly AI LabsOffer to cover someone else's on-call shift. Lists upcoming shifts on a team or schedule and creates an override placing you on the chosen one after explicit confirmation. Write action - never executes without confirming.
- Deploy CheckRootly AI Labs[experimental] Evaluate deployment risk by analyzing code changes against incident history, active incidents, and on-call readiness. Forked-subagent flow may not have MCP access in all Claude Code contexts.
- HandoffRootly AI LabsPrepare an incident or on-call handoff document. Creates structured summary for shift changes or incident commander transitions.
- LookupRootly AI LabsLook up a service, team, or catalog entity in Rootly. Returns owner, on-call, recent reliability, dependencies, and any active incidents. Use when something breaks and the first question is who owns this.
- MyRootly AI LabsPersonal Rootly dashboard. Shows your open action items, your active incidents (where you're a responder), and your upcoming on-call shifts. Use to start the day or to context-switch back into incident work.
- OncallRootly AI LabsShow current on-call status, shift metrics, and health indicators for your team. Use to check who's on-call, handoff context, or on-call workload.
- RespondRootly AI Labs[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.
- RetroRootly AI Labs[experimental] Generate a structured post-incident retrospective from incident data. Forked-subagent flow may not have MCP access in all Claude Code contexts.
- SetupRootly AI LabsSet up the Rootly plugin. Verifies MCP server connection via OAuth2 or API token and guides through configuration. Run this after installing the plugin.
- StatusRootly AI LabsShow a compact service health overview including active incidents by severity. Use for a quick health check of your services.
- SwapRootly AI LabsRequest someone to cover one of your upcoming on-call shifts. Lists your shifts, helps identify a candidate based on availability, and creates an override after explicit confirmation. Write action - never executes without confirming.
- TrendRootly AI LabsReliability trend summary for a service, team, or the whole org. Reports incident volume, severity mix, and MTTR direction over a window (default 30 days). Use for standups, 1-on-1s, or quarterly reviews.