From rootly
Manages Rootly on-call schedules: generates handoff summaries, retrieves shift metrics and incidents, detects health risks like burnout, checks coverage.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin rootlyThis skill uses the workspace's default tool permissions.
Rootly's on-call management provides visibility into who is currently on-call, what incidents occurred during a shift, and whether responders are at risk of burnout. For MSPs and SRE teams, the on-call tools help with:
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Rootly's on-call management provides visibility into who is currently on-call, what incidents occurred during a shift, and whether responders are at risk of burnout. For MSPs and SRE teams, the on-call tools help with:
| Tool | Description | Key Parameters |
|---|---|---|
get_oncall_handoff_summary | Current/next on-call status plus incidents from the current shift | Schedule or team context |
get_oncall_shift_metrics | Shift metrics grouped by user, team, or schedule | group_by, time range |
get_shift_incidents | Incidents filtered to a specific shift timeframe | severity, status, tags, time range |
check_oncall_health_risk | Detects workload health risk in scheduled responders | Schedule/team context |
A shift is a period assigned to one or more responders in a schedule. Rootly supports:
check_oncall_health_risk analyses patterns that correlate with burnout:
| Indicator | Description |
|---|---|
| High incident volume | Significantly more incidents than the rolling average for this shift |
| Late-night pages | High proportion of pages during sleep hours |
| Long time-to-resolve | Incidents taking significantly longer than the team average |
| Repeat pages | Same alert firing multiple times (suggests a systemic issue, not a one-off) |
| Short time between pages | Responder has not had recovery time between incidents |
When a page is not acknowledged within the configured timeout:
Before handing off to the incoming responder:
get_oncall_handoff_summary to get a structured overview:
in_triage incidents — add a handoff note as an action item on each open incidentget_shift_incidents to list all incidents during the shift (for the outgoing responder's records)check_oncall_health_risk for the current schedule or teamget_oncall_shift_metrics grouped by user to identify individual responder load imbalancesget_oncall_shift_metrics with group_by=schedule for the past 7 daysBefore a major deployment or planned maintenance window:
check_oncall_health_risk to confirm responders are not already overloadedget_oncall_handoff_summary to confirm the on-call team is available during the deployment windowAfter a shift ends, review its full incident history:
get_shift_incidents scoped to the shift time rangeseverity=critical or severity=high to focus on the most impactful eventsfind_related_incidents to check if it is part of a pattern| Field | Description |
|---|---|
current_oncall | Name and contact of the current on-call responder |
next_oncall | Name, contact, and handoff time of the next responder |
shift_start | When the current shift started |
shift_end | When the current shift ends |
open_incidents | List of in-progress incidents: ID, title, severity, status |
resolved_incidents | Incidents resolved during this shift |
| Field | Description |
|---|---|
group | User, team, or schedule name |
incident_count | Total incidents during the period |
mttr | Mean time to resolve (seconds) |
mtta | Mean time to acknowledge (seconds) |
escalations | Number of incidents that escalated beyond Tier 1 |
severity_breakdown | Incident count by severity level |
| Error | Cause | Resolution |
|---|---|---|
| No schedule found | Team or schedule not configured | Verify schedule exists in Rootly Settings > On-Call |
| Empty handoff summary | No incidents in current shift | This is expected for quiet shifts — healthy outcome |
| Health risk unavailable | Insufficient historical data | Need at least 2-3 past shifts to baseline |
| 401 Unauthorized | Invalid API token | Regenerate at Account > Manage API Keys |
deployment-related or third-party make shift analysis more usefulfind_related_incidents for recurring alerts