Stats
Actions
Tags
From servicenow
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
How this command is triggered — by the user, by Claude, or both
Slash command
/servicenow:triage [INC number, priority filter, or description]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /servicenow:triage Route based on `$ARGUMENTS`: ## No arguments or general request If `$ARGUMENTS` is empty, contains "what's on fire", "open", "recent", or "list": - Run the **List Recent Incidents** workflow from the `triaging-incidents` skill. - Show open incidents sorted by priority, highlight any P1/P2. ## Specific INC number If `$ARGUMENTS` contains an INC number (e.g., "INC0010001"): 1. Find the incident: `list_records(table_name="incident", query="number=$ARGUMENTS", limit=1)` 2. Run the **Investigate an Incident** workflow — get full details, check CI dependencies, find simila...
Route based on $ARGUMENTS:
If $ARGUMENTS is empty, contains "what's on fire", "open", "recent", or "list":
triaging-incidents skill.If $ARGUMENTS contains an INC number (e.g., "INC0010001"):
list_records(table_name="incident", query="number=$ARGUMENTS", limit=1)If $ARGUMENTS contains "P1", "P2", "critical", or "high priority":
If $ARGUMENTS contains "triage", "assess", or "new":
If $ARGUMENTS contains "trends", "analysis", "bulk", or "SLA":
For any other input, treat $ARGUMENTS as a search term:
list_records(table_name="incident", query="short_descriptionLIKE$ARGUMENTS^active=true", limit=10)npx claudepluginhub kylburns89/servicenow-claude-plugins --plugin plugin/incident-triageTriages open PagerDuty incidents by urgency and priority, listing triggered/acknowledged ones with counts, summary table, critical highlights, similar past incidents, and recommendations.
/incident-triageLists active Rootly incidents filtered by severity and status, sorted by severity with counts, triage table, affected services, and AI analysis for critical ones.
/incident-triageTriages current Better Stack incidents: fetches active ones, categorizes by status, highlights unacknowledged grouped by monitor, and suggests next steps.
/incidentOrchestrates incident response for specified <incident> using SRE best practices, supporting optional [phase] like triage or postmortem.
/incident-triageTriages open Huntress incidents by severity: lists sorted incidents with counts by level, summary table, critical highlights, and next-step recommendations. Supports --severity, --organization_id, --limit filters.
/incidentManages incident response: classifies SEV1-4 severity, builds timelines with evidence, performs 5 Whys root cause analysis, generates blameless post-mortems with action items and metrics. Outputs Markdown docs and git commits.