incident-triage
Skill41 starsChanged 21 days agoApache-2.0View on GitHub
Triage, prioritize, and assign incidents by impact, urgency, category, escalation risk, ownership, and SLA exposure.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- termalinapp/termalin-plugintheir own version, first seen Nov 15, 2026
- superset-sh/supersettheir own version, first seen Nov 2, 2026
- briiirussell/cybersecurity-skillstheir own version, first seen Nov 1, 2026
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
- rpraharaj/ai-engineertheir own version, first seen Nov 1, 2026
- ParadevAI/Paradevtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use write-runbook, threat-hunting and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MaheshAwasareSkillwrite-runbook
Generate an operational runbook for a service from its code, config, and dependencies — what to do when it breaks, where to look, how to roll back, who to escalate to. Use proactively before a service goes to production, after a major incident, or when handing off operational ownership.
Also in 3 projects that use this
allanninalSkillthreat-hunting
Hunt threats using Sigma detection rules and security analysis techniques. Use when investigating security incidents, creating detection rules, or analyzing suspicious activity.
Also in 3 projects that use this
srclightSkillexplore-codebase
This skill should be used when the user asks to "explore this codebase", "understand this project", "give me an overview", "how does this work", "onboard me", "walk me through the architecture", "map the codebase", or any request to understand a codebase's structure, architecture, or design.
Also in 3 projects that use this
thlaureSkillreview-change
Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.
Also in 4 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 projects that use this
MicrosoftSkillapi-design
Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- ParadevAI/Paradev★ 16ksame name
- superset-sh/superset★ 16ksame name
- briiirussell/cybersecurity-skills★ 489same name
- Indium-AI-Labs/indium-agentkit★ 18same name
- Ionate-Technologies/indium-agentkit★ 17same name
- Mozurok/fhorja.dev★ 10same name
- aws-samples/sample-aws-ops-skills-for-agents★ 8same name
- ByronScottJones/Agents★ 7same name
- aprameyak/coding-skills★ 1same name
- natrisc/claude-code-agents★ 1same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository184 other files it gives its agents.
- happy-platform-skillsSkill
- application-scopeSkill
- batch-operationsSkill
- configuration-validationSkill
- deployment-workflowSkill
- generic-crud-operationsSkill
- instance-managementSkill
- schema-discoverySkill
- script-executionSkill
- script-syncSkill
- smart-assessmentSkill
- task-analysisSkill
- task-summarizationSkill
- update-set-managementSkill
- user-provisioningSkill
- workflow-creationSkill
- workspace-insightsSkill
- approval-summarizationSkill
- approval-workflowsSkill
- catalog-builder-aiSkill
- catalog-item-generationSkill
- item-creationSkill
- multi-turn-orderingSkill
- request-fulfillmentSkill
- ui-policiesSkill
- variable-managementSkill
- ci-discoverySkill
- cmdb-search-analysisSkill
- data-qualitySkill
- impact-analysisSkill
- relationship-mappingSkill
- service-graph-diagnosisSkill
- activity-responseSkill
- csm-case-summarizationSkill
- chat-recommendationSkill
- email-recommendationSkill
- csm-kb-generationSkill
- resolution-notesSkill
- csm-sentiment-analysisSkill
- csm-sidebar-summarizationSkill
- csm-suggested-stepsSkill
- trending-topicsSkill
- automated-testingSkill
- business-rulesSkill
- client-scriptsSkill
- code-assistSkill
- code-reviewSkill
- data-importSkill
- debugging-techniquesSkill
- fluent-sdkSkill
- glide-api-referenceSkill
- mcp-server-installationSkill
- mcp-serverSkill
- notificationsSkill
- performance-optimizationSkill
- scheduled-jobsSkill
- scripted-rest-apisSkill
- script-includesSkill
- servicenow-docs-mcpSkill
- test-generationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Use this skill to classify incoming incidents, validate priority, select an assignment group, and document the triage decision.
- Distinctive: line 29
Read and update access to incident records
- Distinctive: line 30
Read access to assignment groups
- Distinctive: line 88
Look up the group sys_id:
- Very specific: line 111
Validation checkpoint: After assignment, query the incident to confirm assignment_group and state were updated.
- Distinctive: line 164
Verify impact and urgency independently before accepting the calculated priority.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Incident Triage
Overview
Use this skill to classify incoming incidents, validate priority, select an assignment group, and document the triage decision.
Prerequisites
- Read and update access to incident records
- Read access to assignment groups
- Knowledge of the organization’s impact, urgency, and escalation rules
Procedure
Step 1: Identify Incidents Requiring Triage
Query for active incidents that are unassigned or in "New" state.
Tool: SN-Query-Table
Parameters:
table_name: incident
query: active=true^priorityIN1,2^assigned_toISEMPTY
fields: number,short_description,description,impact,urgency,category,priority
limit: 20Step 2: Analyze Each Incident
For each incident, determine:
- Category — Match keywords to category:
- Network: "network", "connectivity", "VPN", "wifi", "firewall"
- Hardware: "laptop", "monitor", "keyboard", "printer", "device"
- Software: "application", "crash", "error", "update"
- Email: "email", "outlook", "mailbox", "calendar"
- Security: "password", "access", "locked", "breach", "phishing"
- SAP/ERP: "SAP", "ERP", "finance system", "procurement"
Priority — Apply the Impact/Urgency matrix:
Impact ↓ / Urgency → High (1) Medium (2) Low (3) High (1) P1 P2 P3 Medium (2) P2 P3 P4 Low (3) P3 P4 P5 - Escalation triggers — Bump to P1 if any apply:
- Executive mentioned or revenue impact
- Security breach or phishing confirmed
- Outage affecting multiple users
- SLA at risk of breach
Step 3: Resolve Assignment Group
Map the category to an assignment group:
| Category | Assignment Group |
| Network | Network Operations |
| Hardware | Desktop Support |
| Software | Application Support |
| Messaging Team | |
| Security | Security Operations |
| SAP/ERP | ERP Support |
| Unknown | Service Desk L2 |
Look up the group sys_id:
Tool: SN-Query-Table
Parameters:
table_name: sys_user_group
query: name=Network Operations
fields: sys_id,name
limit: 1Validation checkpoint: Confirm the query returns exactly one result with a valid sys_id. If no group is found, fall back to "Service Desk L2" and note the mismatch in work notes.
Step 4: Assign the Incident
Tool: SN-Assign-Incident
Parameters:
sys_id: [incident_sys_id]
assignment_group: Network Operations
work_notes: "Triage: Assigned to Network Operations based on keyword analysis (VPN connectivity issue). Priority validated as P2 per impact/urgency matrix."Validation checkpoint: After assignment, query the incident to confirm assignment_group and state were updated. If the update failed (permissions, read-only state), log the error in work notes and flag for manual review.
Step 5: Document Triage Decision
Tool: SN-Add-Work-Notes
Parameters:
sys_id: [incident_sys_id]
work_notes: "TRIAGE: Category=Network (VPN, connectivity). Impact=2 Urgency=1 → P2. Assigned Network Operations. Next: investigate VPN tunnel status."Troubleshooting
| Problem | Cause | Fix |
| No incidents found | Query too restrictive | Broaden query; check different states |
| Assignment group not found | Name mismatch | Use LIKE operator: nameLIKENetwork |
| Insufficient permissions | Missing itil role or incident read-only | Verify roles; check incident state |
Examples
Network Issue Triage
Incident INC0012345 — "Cannot connect to VPN from home"
- Keywords: "VPN", "connect" → Network
- Impact: Medium (single user) / Urgency: High (cannot work) → P2
- Assignment: Network Operations
Tool: SN-Assign-Incident
Parameters:
sys_id: abc123
assignment_group: Network Operations
work_notes: "Triage: VPN connectivity issue assigned to Network Ops. P2 priority."Security Escalation
Incident INC0012346 — "Suspicious email with attachment clicked"
- Keywords: "suspicious", "email", "clicked" → Security → Escalate to P1
- Assignment: Security Operations — notify security manager
Tool: SN-Update-Record
Parameters:
sys_id: def456
table_name: incident
fields: { priority: 1, assignment_group: Security Operations, work_notes: "Triage: Escalated to P1. Phishing indicator. Security Ops notified." }Best Practices
- Verify impact and urgency independently before accepting the calculated priority.
- Confirm the assignment group exists before updating the incident.
- Record the evidence and reasoning behind every triage decision.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

