rootly

Plugin rootly from marketplace msp-claude-plugins in WYRE-AI/msp-claude-plugins. Commands read from the repo's manifest — yesterday.

Skills (7)

• Rootly Alerts

  Rootly's alerting layer between monitoring tools and incident management: alert sources (`alerts_source`) and their webhook/email intake, alert routing rules, alert groups (deduplication/noise reduction), alert urgencies, escalation policies, and the acknowledge/resolve actions on an individual aler

• Rootly API Patterns

  The Rootly hosted MCP server and the JSON:API REST surface behind it: Global vs. Team token types and how the gateway injects credentials, the catalog of roughly 253 dynamically generated tools by category, page-number pagination and relationship includes, filter syntax, rate limits, and error handl

• Rootly Incidents

  Incidents, Rootly's primary resource: the incident lifecycle and status transitions, severity levels, the incident field reference, AI-assisted analysis via find_related_incidents and suggest_solutions, action items, alert attachment, and cross-vendor PSA ticket correlation. When declaring, searchin

• Rootly On-Call

  Rootly on-call visibility built on the get_oncall_handoff_summary, get_oncall_shift_metrics, get_shift_incidents, get_oncall_schedule_summary and check_responder_availability tools: schedule and rotation coverage, structured shift handoffs, per-shift incident scoping, shift metric fields, and the bu

• Rootly Postmortems

  Rootly postmortems as structured post-incident retrospectives: Rootly's retrospective process/step model (there is no standalone "postmortem" object), per-step status tracking through to completion, action item creation and tracking, and the blameless review practices Rootly's model assumes. When wr

• Rootly Services

  The Rootly service catalog: the real service record (ownership via owner teams/users, Slack channels, dependency modeling via linked service IDs, and third-party links to PagerDuty/Opsgenie/Cortex/Backstage/GitHub/GitLab), service CRUD, incident/uptime charts per service, and how services link back

• Rootly Workflows

  Rootly's incident-response automation model: workflow tasks (each with a concrete `task_type` like `create_slack_channel` or `page_rootly_on_call_responders`), the trigger-type/`triggers`-event structure (incident, post_mortem, action_item, alert, pulse, simple), the ID-list based condition/matching

Slash commands (5)

• /rootly:action-items

  List outstanding action items from Rootly postmortems and incidents

• /rootly:create-incident

  Create a new incident in Rootly with title, severity, and affected services

• /rootly:incident-triage

  Triage active Rootly incidents by severity and status

• /rootly:postmortem-summary

  Generate a postmortem summary for a resolved Rootly incident

• /rootly:service-status

  Check service health and dependency status across the Rootly service catalog

Subagents (2)

• incident-commander

  Use this agent when an MSP engineer, SRE, or incident manager needs to command an active Rootly incident or review open incidents. Trigger for: rootly incident, rootly outage, incident command rootly, rootly response, rootly severity, rootly on-call, rootly postmortem, active incident rootly. Exampl

• post-mortem-writer

  Use this agent when an MSP engineer, SRE, or incident manager needs to generate a structured post-incident review (PIR) for a resolved Rootly incident — not live incident command, but a thorough retrospective document covering what happened, why it happened, the full impact timeline, contributing fa

Similar plugins