Automate PagerDuty incident retrieval, creation, acknowledgment, and resolution via REST API.
npx skills add https://github.com/kubiyabot/skill --skill pagerduty
Please help me install this Agent Skill. Skill: pagerduty Source: https://github.com/kubiyabot/skill/tree/main/examples/wasm-skills/pagerduty-skill Command: npx skills add https://github.com/kubiyabot/skill --skill pagerduty
PagerDuty is widely used for incident response and on-call management. This Skill provides an automated bridge to PagerDuty's API, enabling teams to query, create, update, and annotate incidents directly from the AI agent, reducing manual steps and response times.
Install the Skill, configure API key, and run common operations:
High-intent search queries and answers about installing and using this skill.
You can automate PagerDuty incident management by using a Skill API to retrieve, create, acknowledge, and resolve incidents directly through REST-based endpoints, reducing manual response steps. It supports filtering by status, urgency, and service.
Yes, you can retrieve and filter PagerDuty incidents via API using specific parameters. The Skill allows you to list incidents by status, urgency, service, and time range, returning targeted incident data for automated monitoring and response.
To programmatically acknowledge and resolve PagerDuty incidents, you configure your API key and use the Skill's acknowledge and resolve tools. You can also add notes to incident timelines to track the resolution progress.
Yes, this PagerDuty automation Skill supports on-call schedule retrieval. You can use the list-oncalls and list-services tools to retrieve current on-call schedules and service information, supporting automated alert routing and incident assignment.
Before using a PagerDuty API automation tool, you need to install the Skill and configure your PagerDuty API key. This authentication key enables the WASM-based runtime to securely interact with your PagerDuty REST endpoints.
The Skill's add-note tool allows you to append notes to incident timelines via the API, but it operates within the constraints of standard PagerDuty REST endpoints. It does not modify existing incident notes, only adds new entries to the timeline.
tuanductranManage NextDNS profiles, security settings, analytics, and logs via RESTful API.
allthingslinuxRoute alerts and coordinate incidents across PagerDuty, Alertmanager, and Slack.
ChegginCapture, deduplicate, and alert on frontend and backend errors with deploy-version tagging.
Shakudo-ioTrigger, acknowledge, and resolve PagerDuty incidents via REST and Events APIs.
