pagerduty-automation
Automate PagerDuty Incident Operations
PagerDuty operations often require careful tool selection and repeated ID lookups. This skill guides Claude, Codex, and Claude Code through Rube MCP workflows for incidents, services, schedules, and escalation policies.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "pagerduty-automation" from https://skillstore.io/skills/sickn33-pagerduty-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-pagerduty-automation/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "pagerduty-automation". Show current high urgency incidents for the payments service.
Expected outcome:
A concise incident list with status, urgency, service, assigned responder, and recommended next action.
Using "pagerduty-automation". Create a schedule override for Alex tomorrow.
Expected outcome:
A confirmation summary with schedule, time window, user, affected rotation, and a request for approval before creating the override.
Using "pagerduty-automation". Review the checkout escalation policy.
Expected outcome:
A plain-language summary of escalation levels, delays, loops, targets, and services that depend on the policy.
Security Audit
High RiskMost static command-execution findings are false positives caused by Markdown backticks around PagerDuty tool names and parameters. The hardcoded Rube MCP URL is a low network trust-boundary finding, and semantic review found meaningful risks from third-party authorization and high-impact PagerDuty state changes.
Confirmed security concerns (2)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (78)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-pagerduty-automation/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-pagerduty-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-pagerduty-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-pagerduty-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-pagerduty-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). pagerduty-automation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-pagerduty-automation/audits/4BibTeX citation
@techreport{sickn33-sickn33-pagerduty-automation-2026,
author = {sickn33},
title = {pagerduty-automation security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-pagerduty-automation/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "pagerduty-automation security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-pagerduty-automation/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-pagerduty-automation:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Coordinate Incident Response
Review open incidents, add notes, acknowledge or resolve incidents, and inspect alert details during response.
Maintain Service Configuration
Create or update services, integrations, and escalation policies after confirming account IDs.
Manage On-Call Coverage
Audit schedules, on-call coverage, overrides, and escalation rules before changing rotations.
Try These Prompts
Use this PagerDuty skill to find active incidents for {service_name}. Search tools first, then show status, urgency, owner, and next action.Look up incident {incident_id}. Summarize related alerts, current status, notes, and analytics that affect response priority.Check schedule {schedule_name} for {date_range}. Preview a temporary override for {user_name}, then ask before applying it.Inspect escalation policy {policy_name}, identify affected services, draft the change, preview risks, and require confirmation before updating PagerDuty.Best Practices
- Search Rube tools first so parameters match current PagerDuty schemas.
- Confirm every state-changing action with the requester before updating PagerDuty.
- Use least-privilege PagerDuty access and keep audit notes for operational changes.
Avoid
- Do not resolve, snooze, or reassign incidents without explicit human approval.
- Do not create schedules, services, or policies from incomplete names without resolving IDs.
- Do not run broad bulk changes during active incidents without rollback planning.
Frequently Asked Questions
Does this skill require PagerDuty credentials?
Can Claude, Codex, or Claude Code use this skill?
Does the skill run local scripts?
Can it change production PagerDuty data?
Why does it search tools first?
What should teams review before using it?
Developer Details
Author
sickn33License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/pagerduty-automationRef
816c62b2546ddb1c6a0453e7c781b5e095117819
Maintenance freshness
7/18/2026
Usage
8 downloads · 95 views
File structure
📄 SKILL.md