Help us improve
Share bugs, ideas, or general feedback.
From rootly
Manages Rootly postmortems: creates retrospectives from incidents, lists by status/incident, retrieves details, tracks action items, applies templates for blameless reviews.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin rootlyHow this skill is triggered — by the user, by Claude, or both
Slash command
/rootly:postmortemsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Postmortems in Rootly are structured retrospectives created after incidents are resolved. They document what happened, why it happened, and what will be done to prevent recurrence. Rootly supports templates, automatic timeline import, action item tracking, and integration with project management tools for follow-through.
Activate for: incident, outage, system failure, post-mortem, incident post-mortem, root cause analysis, RCA, five whys, corrective action, lessons learned, incident log, incident report, P1, P2, major incident, incident review, incident timeline, what went wrong, service outage, payment failure, data breach incident, incident response, MTTD, MTTR, incident management, on-call, escalation, incident retrospective, corrective action tracker, lessons learned brief. NOT for: change impact assessment (use official /change-request), risk register building (use official risk-assessment auto-skill), compliance obligation mapping (use official compliance-tracking auto-skill).
Manages Rootly incidents: create, search, triage, update, resolve using MCP tools. Covers lifecycle, severity/status, AI analysis (find_related_incidents, suggest_solutions), alerts, action items.
Guides structured incident response from detection through post-mortem, including severity classification and RCA templates.
Share bugs, ideas, or general feedback.
Postmortems in Rootly are structured retrospectives created after incidents are resolved. They document what happened, why it happened, and what will be done to prevent recurrence. Rootly supports templates, automatic timeline import, action item tracking, and integration with project management tools for follow-through.
A typical Rootly postmortem includes:
Action items are the most important output of a postmortem:
rootly_list_postmortems
Parameters:
incident_id -- Filter by incidentstatus -- Filter by status (draft, in_review, published, completed)Example response:
{
"data": [
{
"id": "pm-101",
"type": "postmortems",
"attributes": {
"title": "Payment Processing Outage - 2026-03-25",
"status": "in_review",
"incident_id": "inc-456",
"created_at": "2026-03-26T10:00:00Z",
"summary": "Payment webhooks timed out due to database connection pool exhaustion",
"action_items_count": 4,
"action_items_completed": 1
}
}
]
}
rootly_get_postmortem
Parameters:
postmortem_id -- The postmortem IDrootly_create_postmortem
Parameters:
incident_id -- The incident to create a postmortem fortitle -- Postmortem titletemplate_id -- Optional template to userootly_update_postmortem
Parameters:
postmortem_id -- The postmortem IDsummary -- Updated summaryroot_cause -- Root cause analysisimpact -- Impact descriptionstatus -- Updated statusrootly_list_action_items
Parameters:
incident_id -- Filter by incidentstatus -- Filter by status (open, in_progress, completed)assignee -- Filter by assigneerootly_create_action_item
Parameters:
incident_id -- The incident IDtitle -- Action item titledescription -- Detailed descriptionpriority -- Priority levelassignee_id -- Assigned userdue_date -- Target completion daterootly_update_action_item
Parameters:
action_item_id -- The action item IDstatus -- Updated statusassignee_id -- Updated assigneerootly_get_incidentrootly_create_postmortem (timeline auto-imports)rootly_get_postmortemrootly_list_action_items with status=openCause: Invalid postmortem ID or postmortem deleted Solution: List postmortems for the incident to verify the ID
Cause: Attempting to create a postmortem for an active incident Solution: Resolve the incident first, then create the postmortem
Cause: Postmortem already exists for this incident Solution: Get the existing postmortem instead of creating a new one