Alerting Oncall
CheckedThis skill automatically alerts on-call personnel based on defined triggers, streamlining incident response and reducing downtime.
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 alerting-oncall -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, 471 lines
About this skill
What it does
The alerting-oncall skill allows AI agents to manage on-call schedules and escalate alerts appropriately. It can determine who is currently on-call based on a defined schedule, and then forward incident notifications to the correct individuals. This ensures timely responses to critical issues by routing them to the right people at the right time.
When to use it
- Incident Response: Automatically notify the on-call engineer when an alert triggers in your monitoring system.
- Escalation Management: Route alerts to secondary or tertiary contacts if the primary on-call person doesn't acknowledge within a specified timeframe.
- Schedule Adherence: Verify that notifications are sent according to the defined on-call schedule, ensuring coverage and accountability.
- Rotation Awareness: Determine who is responsible for handling an incident based on rotation schedules.
Key capabilities
- On-call schedule integration
- Incident notification routing
- Escalation logic
- Rotation awareness
Example prompts
- "Who is the on-call engineer for database alerts?"
- "Forward this PagerDuty alert to the current primary on-call."
- "What's the escalation policy if the on-call doesn’t acknowledge within 15 minutes?"
Tips & gotchas
The skill requires access to your on-call schedule data, which might be stored in a calendar or other system. Ensure that the AI agent has appropriate permissions and credentials to retrieve this information for accurate routing.