incident-management
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Create, read, update, assign, acknowledge, hold, resolve, reopen, and close an incident record on a supported ITSM or incident-response platform — currently ServiceNow (standard state model), PagerDuty, Opsgenie, Jira Service Management, and ManageEngine ServiceDesk Plus. The break/fix counterpart to change-management, it covers records for unplanned disruptions and their lifecycle, not planned changes. Assumes an authenticated client for the target platform's API is already available; this skill does not provision or authenticate it. Check references/INDEX.md for which platforms and operations are covered; paging an on-call responder and problem or major-incident handling are not covered.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- mawero83/google-sre-skillstheir own version, first seen Nov 1, 2026
- Abdox-menara/guard-skillstheir own version, first seen Aug 24, 2026
- mmondora/claude-skillstheir own version, first seen Feb 14, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- mawero83/google-sre-skills★ 18same name
- mmondora/claude-skills★ 1same name
- Abdox-menara/guard-skills★ 0same name
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 repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alert-monitor-managementSkill
- automation-job-executionSkill
- casb-policy-managementSkill
- casb-posture-assessmentSkill
- certificate-managementSkill
- change-managementSkill
- cloud-security-group-auditSkill
- cmdb-asset-managementSkill
- compute-instance-provisioningSkill
- config-backup-managementSkill
- connector-tunnel-managementSkill
- container-workload-deploymentSkill
- crm-contact-managementSkill
- dcim-asset-managementSkill
- dhcp-scope-managementSkill
- dns-record-managementSkill
- dns-zone-managementSkill
- firewall-managementSkill
- infrastructure-plan-executionSkill
- interface-link-troubleshootingSkill
- ipam-allocationSkill
- load-balancingSkill
- log-querySkill
- metric-querySkill
- network-access-control-managementSkill
- network-health-verificationSkill
- network-state-collectionSkill
- notificationsSkill
- repository-pull-request-managementSkill
- routing-troubleshootingSkill
- sdwan-policy-managementSkill
- sdwan-site-onboardingSkill
- secret-retrievalSkill
- software-upgrade-lifecycleSkill
- vpn-tunnel-managementSkill
- vulnerability-lookupSkill
- waf-managementSkill
- wireless-network-managementSkill
- zero-trust-access-policy-managementSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Not for planned changes — see change-management.
- Very specific: line 20
Not for delivering a message to a channel or person — see notifications.
- Very specific: line 21
Not for monitor, threshold, or alert-rule definitions, or for acknowledging or resolving an alert raised by an observability platform — see …
- Distinctive: line 24
Not for problem records, major-incident handling, or paging an on-call responder.
- Very specific: line 60
Does not cover planned changes (see change-management), configuration-item records (see cmdb-asset-management), notification delivery (see …
- Distinctive: line 63
Does not cover problem records, major-incident management, or on-call paging.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Incident Management
Runs an incident record lifecycle — create, update, assign, acknowledge, hold, resolve, reopen, close — on whichever platform the caller is targeting, following that platform's own documented state model and required fields.
When to use this skill
- Creating, reading, updating, assigning, acknowledging, placing on hold, resolving, reopening, or closing
an incident record on a supported ITSM or incident-response platform. Which of those actions a platform supports is
platform-dependent; see
references/INDEX.md. - Not for planned changes — see
change-management. Linking an incident to an existing change is part of the platform's own procedure; creating or advancing the change is not. - Not for delivering a message to a channel or person — see
notifications. - Not for monitor, threshold, or alert-rule definitions, or for acknowledging or resolving an alert
raised by an observability platform — see
alert-monitor-management. This skill covers incident records on an ITSM platform. - Not for problem records, major-incident handling, or paging an on-call responder; no procedure here covers them yet.
Universal concepts (shared incident-handling vocabulary, not a wire standard)
Several platforms are documented today, so these are claims expected to hold for any listed platform, and
do not extend automatically to a platform not listed in references/INDEX.md. Where a platform
differs, its own procedure wins.
- An incident moves through named states from open to resolved. Some platforms add states before that (acknowledged, on hold) or after it (closed). The state names and the transitions allowed between them are the platform's own, and some platforms let each site or workflow define them; do not assume one platform's names or end state on another.
- Resolving and closing are different steps, where the platform separates them. Resolving declares the service restored and can usually be undone by reopening; closing is final where documented. Treat both as confirmation points and report which one happened.
- Internal notes and caller-visible comments are separate channels, where the platform separates them. Check which one a platform's note field reaches before writing sensitive content.
- Where a platform computes priority from impact and urgency, set the inputs rather than the result.
- A platform may change a record in response to a write (clearing a hold reason, adjusting an assignment, refusing a transition). Some platforms apply writes asynchronously, so wait for the request to complete before reading the record back to confirm the state you asked for.
Procedure
- Identify the target platform — from the caller's request or the
platformargument. Checkreferences/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet. - Open
references/<platform>/procedure.mdand follow it exactly — it contains that platform's full operational procedure, error handling, patterns, known limitations, tools, and verification checklist. - Report the outcome using that platform procedure's own status vocabulary — don't normalize it away.
Known limitations
- Platform coverage is in
references/INDEX.md; a platform not listed there needs a new reference file before this skill can be used for it. - Does not cover planned changes (see
change-management), configuration-item records (seecmdb-asset-management), notification delivery (seenotifications), or alert handling on observability platforms (seealert-monitor-management). - Does not cover problem records, major-incident management, or on-call paging.
Contributing to this skill
SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific procedure changes — a new error
code, a corrected field, a changed API path — belong in that platform's own
references/<platform>/procedure.md, never here.
Tools
Each platform assumes its own authenticated client — see references/INDEX.md for which, and that
platform's procedure.md for the specific operations.
Verification checklist
- Target platform confirmed against
references/INDEX.mdbefore proceeding - That platform's own
procedure.mdwas followed, including its own confirmation gates on resolving and closing an incident - Outcome reported using the platform procedure's own status vocabulary
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.

