pagerduty-api

Queries and manages PagerDuty on-call assignments, incidents, schedules, escalations and routing via REST API and Events API v2.

37|13|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/anthropics/claude-tag-plugins --skill pagerduty-api-anthropics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pagerduty-api
Source: https://github.com/anthropics/claude-tag-plugins/tree/main/pagerduty/skills/pagerduty-api
Command: npx skills add https://github.com/anthropics/claude-tag-plugins --skill pagerduty-api-anthropics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the friction of working across PagerDuty's alerting, on-call, and incident workflows, so you can answer paging questions, investigate incidents, and take action without manually stitching together API calls.

Core Features & Use Cases

  • On-call lookups: Find who is currently on call, who will be paged next, and how service ownership maps to escalation policies and schedules.
  • Incident operations: List, inspect, acknowledge, resolve, snooze, escalate, merge, and annotate incidents while preserving audit context.
  • Routing investigation: Trace how an alert moved from service to escalation policy to schedule, and inspect log entries to see who was notified and why.
  • Use Case: When an incident fires at night, you can quickly confirm the responsible responder, understand the paging path, and take the correct follow-up action in one place.

Quick Start

Ask this skill who is on call for a PagerDuty service or incident, then use it to trace paging history or update the incident status.

Frequently Asked Questions about pagerduty-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find who is currently on call for a PagerDuty service or escalation policy?

You can find who is on call by querying PagerDuty on-call assignments and schedules via the REST API. This Skill maps service ownership to escalation policies, identifying the active responder and who is paged next.

Can I acknowledge or resolve PagerDuty incidents automatically using the API?

Yes, you can acknowledge, resolve, snooze, and escalate PagerDuty incidents via the REST API. Incident mutations require token-based authentication and a From header to preserve audit context during status updates.

How do I trace the routing path of a PagerDuty alert from service to schedule?

You trace alert routing by inspecting PagerDuty log entries to see who was notified and why. This Skill follows the alert path from service to escalation policy to schedule, revealing the exact notification sequence.

What do I need to manage PagerDuty incidents and on-call schedules from the command line?

You need curl and jq to manage PagerDuty incidents and schedules from the command line. These dependencies handle REST API pagination, token-based authentication, From headers, and bracketed array query parameters for JSON processing.

Does the PagerDuty Events API v2 support updating existing incident statuses?

The PagerDuty Events API v2 handles alert lifecycle operations, while incident status updates like acknowledging and resolving require the REST API. This Skill manages both APIs to cover event ingestion and incident mutations.