Query PagerDuty incidents, services, and on-call schedules
Scanned 9/12/2026
Install to Claude Code
Skills Directorynpx -y skills add fisker086/AIOps --skill pagerduty --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pagerduty?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/fisker086-pagerduty)More formats (shields.io, HTML) on the badges page.
---
name: pagerduty
description: Query PagerDuty incidents, services, and on-call schedules
activation_keywords: [pagerduty, incident, alert, oncall, escalation, service]
execution_mode: server
---
# PagerDuty Skill
Provides read-only PagerDuty operations via REST API:
- List and search incidents
- Get incident details and alerts
- List services with escalation policies
- List on-call schedules and who is on-call
- List escalation policies
Use `builtin_pagerduty` tool with fields:
- `operation`: one of "list_incidents", "get_incident", "list_services", "list_schedules", "on_call", "list_escalation_policies"
- `incident_id`: incident ID (required for get_incident)
- `api_key`: PagerDuty API key (from PAGERDUTY_API_KEY env var if not provided)
- `status`: filter incidents by status (triggered, acknowledged, resolved)
- `service_id`: filter by service ID
- `per_page`: results per page (default: 20)
Note: All operations are read-only.
The API key is used only for this request and never logged.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
