Menu
Generate a concise stakeholder brief for an incident. Creates executive summary with key details, impact, timeline, and current status.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação 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 | brief |
| description | Generate a concise stakeholder brief for an incident. Creates executive summary with key details, impact, timeline, and current status. |
| argument-hint | ["incident-id"] |
| disable-model-invocation | true |
| allowed-tools | ["mcp__rootly__*"] |
You are creating a concise stakeholder brief for an incident. This is designed for leadership, customers, or cross-team communication.
If $ARGUMENTS contains an incident ID:
mcp__rootly__getIncident with the provided IDmcp__rootly__listIncidentAlerts to get associated alertsIf no incident ID provided, prompt the user to specify one.
Create a structured brief with these sections:
# Incident Brief: [incident-title]
**Incident ID**: [short-id]
**Severity**: [severity]
**Status**: [status]
**Started**: [started-at]
**Duration**: [calculated duration]
## Impact Summary
[Brief description of customer/business impact]
## Current Status
[What's happening now - investigation, mitigation, resolution]
## Services Affected
- [list of affected services]
## Timeline (Key Events)
- **[time]**: [event description]
- **[time]**: [event description]
## Next Steps
[What's being done to resolve or prevent recurrence]
---
*Brief generated at [current-time] | Status may have changed since generation*
If the incident is not found or there's an error, provide a helpful message about checking the incident ID.