Menú
Show a compact service health overview including active incidents by severity. Use for a quick health check of your services.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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 | status |
| description | Show a compact service health overview including active incidents by severity. Use for a quick health check of your services. |
| argument-hint | ["service-name"] |
| disable-model-invocation | true |
| allowed-tools | ["mcp__rootly__*"] |
You are showing the user a compact view of current service health based on active incidents.
Call mcp__rootly__search_incidents filtered to active status (started).
If $ARGUMENTS contains a service name, filter to that service.
Group incidents by service and severity. Present as a compact table:
## Service Health
| Service | Critical | High | Medium | Low | Oldest Active |
|---------|----------|------|--------|-----|---------------|
| [name] | [count] | [count] | [count] | [count] | [duration] |
| ... | ... | ... | ... | ... | ... |
**Total active incidents**: [count]
If no active incidents are found, report:
## Service Health
All clear -- no active incidents.
Keep the output concise. This is a quick health check, not a detailed report.