alert
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.
Install
With your agent
Install OMGSkills skill "rootly-ai-labs/rootly-claude-plugin:skills/alert" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Rootly-AI-Labs/rootly-claude-plugin /tmp/rootly-claude-plugin && ln -s /tmp/rootly-claude-plugin/skills/alert ~/.claude/skills/alert
From README
Alert Triage You are helping the user triage a Rootly alert. Alerts are the upstream signal that may or may not become incidents. The goal is to give the user enough context in one place that they can decide: ignore, acknowledge, escalate, or open an incident. Workflow Resolve the alert $ARGUMENTS should contain a short alert ID (e.g. A-1234 or 1234). If $ARGUMENTS is empty: report "No alert ID provided. Pass a short ID like A-1234 or 1234." and stop. Otherwise call mcprootlygetalertbyshortid with the value as given. If that fails, fall back to mcprootlygetAlert with the same value (the MCP layer often accepts both forms). If both fail, surface the error and stop. Gather context Once you have the alert UUID: Call mcprootlylistAlertEvents (or filter by alert) to get the event timeline. If the alert response includes an alertgroupid or group reference, call mcprootlygetAlertGroup for sibling alerts. If the alert is attached to an incident, the response usually carries an incidentid.
