Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Connects to PagerDuty's REST API to list active incidents, view timelines and alert correlations, check on-call schedules, and take actions like acknowledge, resolve, and annotate. Read-only by default; write operations require an explicit --confirm flag.
Handles the full triage loop, from listing incidents to acknowledging and annotating, without leaving the agent, and enforces confirmation gates on all write operations to prevent accidental changes.
When to use it
- Checking what incidents are currently firing during an outage
- Finding who is on call for a specific service right now
- Acknowledging a triggered incident to stop further escalation
- Adding a root cause note to an incident's timeline
- Reviewing recent incident history for a service over the past 7 or 30 days
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: What's currently firing on PagerDuty?
- 1Calls pd_incidents to retrieve all triggered and acknowledged incidents
- 2Sorts results by urgency (high first) and duration (oldest first)
- 3Calls pd_incident_detail on the highest urgency incident to get timeline and alert correlation
- 4Returns a summary of all active incidents with detailed context on the most critical one
List of 3 active incidents with the highest-urgency incident's full timeline, trigger source, escalation history, and recommended next steps
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.