pagerduty

What This Skill Does

The PagerDuty skill for OpenClaw is a powerful integration that enables your AI agent to act as an on-call operations engineer. By leveraging the PagerDuty REST API, this skill allows the agent to interact directly with your incident response lifecycle. It provides capabilities to query active incidents, manage service statuses, inspect escalation policies, and view on-call schedules. Essentially, it transforms your agent into a centralized control plane for your PagerDuty account, allowing it to perform routine administrative tasks, fetch critical operational data, and provide status updates on infrastructure health without requiring manual intervention.

Installation

To install this skill, use the OpenClaw command-line interface as follows:

clawhub install openclaw/skills/skills/aiwithabidi/pagerduty

Once installed, you must configure your environment to include the required authentication token. Obtain your API key from your PagerDuty account settings and set it as an environment variable:

export PAGERDUTY_API_KEY="your_api_key_here"

Ensure that the environment where OpenClaw is running has network access to the PagerDuty API endpoints.

Use Cases

This skill is ideal for DevOps and Site Reliability Engineering (SRE) teams. Common use cases include:

1. Automated Incident Triage: Asking the agent to fetch all open incidents for a specific service to provide a high-level summary during a standup meeting.
2. On-Call Management: Quickly identifying who is currently on-call for a particular rotation or checking upcoming schedule changes without logging into the PagerDuty dashboard.
3. Operational Contextualization: Adding notes to an incident as soon as a fix is deployed, ensuring that incident logs are always up-to-date for post-mortem reviews.

Example Prompts

• "List all triggered incidents for the Database service from the last 24 hours."
• "Who is currently on-call for the Backend Engineering team and what is their contact info?"
• "Add a note to incident #12345 stating that the patch has been applied and we are monitoring logs."

Tips & Limitations

• Output Formatting: For automated workflows, use the default JSON output. When working interactively, append --human to commands to receive a table-formatted response that is easier to parse visually.
• Security: Ensure that the PAGERDUTY_API_KEY is kept secure and not hardcoded in scripts or exposed in logs. Use a secrets manager if possible.
• Rate Limiting: Keep in mind that heavy polling of the PagerDuty API may hit rate limits. Design your agent's task loops to be considerate of API throughput.