Incident Management
CheckedAutomatically triage, assign, and track IT incidents based on severity and pre-defined workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add bagelhole/devops-security-agent-skills --skill incident-management -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
bagelhole
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bagelhole/devops-security-agent-skills at 0365f57a07.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0365f57a07
- Scanned
- 1 file, 446 lines
About this skill
What it does
This skill enables AI agents to manage and respond to incidents. It can track incident status, assign ownership, and facilitate communication between teams involved in resolution. The agent can also leverage this skill to automatically create incident reports summarizing key details and actions taken.
When to use it
- Responding to alerts: Automatically acknowledge and log alerts from monitoring systems, initiating an incident management workflow.
- Coordinating team responses: Facilitate communication and task assignment between development, operations, and security teams during an outage.
- Generating post-incident reports: Create comprehensive summaries of incidents, including root cause analysis and corrective actions.
- Tracking incident resolution progress: Monitor the status of ongoing incidents and provide updates to stakeholders.
Key capabilities
- Incident tracking
- Ownership assignment
- Team communication facilitation
- Automated report generation
Example prompts
- "Create a new incident for 'Database connection errors' with severity 'High'."
- "Assign John Doe as the owner of incident #1234."
- "Generate a post-incident report for incident #5678, including root cause analysis."
- “What is the current status of incident 9012?”
Tips & gotchas
This skill requires access to your existing incident management system (e.g., Jira Service Management, ServiceNow) to function correctly. Ensure proper API keys and permissions are configured for seamless integration.