Help us improve
Share bugs, ideas, or general feedback.
From rootly
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.
npx claudepluginhub rootly-ai-labs/rootly-claude-plugin --plugin rootlyHow this skill is triggered — by the user, by Claude, or both
Slash command
/rootly:actionThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the user view or update incident action items in Rootly.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
You are helping the user view or update incident action items in Rootly.
Parse $ARGUMENTS:
list → List mode (default).add <incident-ref> → Add mode. The remainder is the description.argument-hint and stop.Goal: show the user their open action items, sorted by incident severity then age.
mcp__rootly__getCurrentUser to get the user's UUID.mcp__rootly__listAllIncidentActionItems and filter results client-side by assigned_to_user_id matching the current user, plus status not in done/closed/cancelled.incident_id or incident reference. Cluster results by incident.## Your Open Action Items ([N] total across [M] incidents)
### [INC-XXXX] [Incident title] ([severity])
- [ ] [Action item description] — due [date or "no due date"], priority [priority]
- [ ] [Action item description] — due [date], priority [priority]
### [INC-YYYY] [Incident title] ([severity])
- [ ] [Action item description] — due [date], priority [priority]
If there are zero open items, say so plainly: "No open action items assigned to you."
Goal: create a new action item on an incident. Write action — requires explicit confirmation.
$ARGUMENTS (UUID, INC-XXXX, or bare number).mcp__rootly__getIncident with the reference exactly as the user provided it. The MCP server now accepts UUIDs plus sequential forms like 4460, #4460, and INC-4460.**About to create action item:**
- Incident: [INC-XXXX] [title]
- Summary: [summary]
- Assigned to: [you / unassigned per default]
- Priority: medium (default — adjust in Rootly UI if needed)
Confirm to create? (yes / no)
mcp__rootly__createIncidentActionItem until they say yes.mcp__rootly__createIncidentActionItem with:{
"incident_id": "[resolved incident UUID]",
"data": {
"type": "incident_action_items",
"attributes": {
"summary": "[summary]",
"priority": "medium",
"status": "open"
}
}
}
Echo the resulting action item ID and any URL. 7. On rejection, acknowledge and stop without making the call.
mcp__rootly__listAllIncidentActionItems is rate-limited or paginates, take just the first page (50 items). The user can re-run if they need more.