Menu
Prepare an incident or on-call handoff document. Creates structured summary for shift changes or incident commander transitions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Set up the Rootly plugin. Verifies MCP server connection via OAuth2 or API token and guides through configuration. Run this after installing the plugin.
Manage 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.
Draft 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.
Offer 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.
Request 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.
Triage 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.
| name | handoff |
| description | Prepare an incident or on-call handoff document. Creates structured summary for shift changes or incident commander transitions. |
| argument-hint | ["incident-id"] |
| disable-model-invocation | true |
| allowed-tools | ["mcp__rootly__*"] |
You are preparing a handoff document for either incident response or on-call shift transitions.
If $ARGUMENTS contains an incident ID:
mcp__rootly__getIncident with the provided IDmcp__rootly__listIncidentAlerts for associated alertsIf no incident ID provided:
mcp__rootly__get_oncall_handoff_summary or relevant on-call endpointsmcp__rootly__search_incidents filtered to recent active incidentsFor incident-specific handoffs:
# Incident Handoff: [incident-title]
**Handoff Time**: [current-time]
**Incident ID**: [short-id]
**Severity**: [severity]
**Current Status**: [status]
**Started**: [started-at] ([duration] ago)
## Current Situation
[Brief summary of what's happening now]
## What's Been Done
- [action 1]
- [action 2]
- [action 3]
## Immediate Next Steps
1. [priority action]
2. [next action]
3. [monitoring action]
## Key Contacts
- **Incident Commander**: [if assigned]
- **On-Call**: [current on-call person]
- **Escalation Path**: [relevant escalation details]
## Important Notes
[Any critical context, gotchas, or special considerations]
## Monitoring
- [key dashboards/alerts to watch]
- [specific metrics to monitor]
For general on-call handoffs:
# On-Call Handoff
**Handoff Time**: [current-time]
**Previous On-Call**: [if determinable]
**Incoming On-Call**: [current/next on-call]
## Active Incidents
[List current active incidents with brief status]
## Recent Activity (Last 24h)
- [incident summaries]
- [any resolved issues]
## Ongoing Concerns
- [items requiring monitoring]
- [scheduled maintenance]
- [known issues]
## Escalation Paths
[Current escalation contacts and procedures]
## Key Dashboards
[Important monitoring dashboards to check]
## Upcoming Events
[Deployments, maintenance, or other scheduled activities]