Menu
Show 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.
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
| name | oncall |
| description | Show 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. |
| argument-hint | ["team-name"] |
| disable-model-invocation | true |
| allowed-tools | ["mcp__rootly__*"] |
You are showing the user a compact on-call dashboard. Gather data and present it concisely.
Make these calls (in parallel if possible):
mcp__rootly__get_oncall_handoff_summary -- Current and next on-call, shift contextmcp__rootly__get_oncall_shift_metrics -- Workload data (hours, incident count)mcp__rootly__check_oncall_health_risk -- Fatigue and health risk indicatorsIf $ARGUMENTS contains a team name, pass it to scope the queries.
## On-Call Dashboard
### Current On-Call
- **Who**: [name]
- **Since**: [start time] ([hours] hours into shift)
- **Incidents this shift**: [count]
### Next On-Call
- **Who**: [name]
- **Handoff**: [time] ([hours] from now)
### Shift Health
- **Hours worked**: [current hours] / [shift length]
- **Fatigue risk**: [LOW / MEDIUM / HIGH]
- **Workload**: [incidents handled] incidents, [pages received] pages
### Recent Incidents This Shift
[List of incidents handled during current shift, if any]
| Severity | Title | Duration | Status |
|----------|-------|----------|--------|
| ... | ... | ... | ... |
Keep the output compact. If any data source returns an error or empty result, omit that section rather than showing empty tables.
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.