Skip to content
TrustedSkillsbeta
Back to all skills

Pagerduty Automation

Checked
davepoon·vlatest·devops·MIT

Automatically create, update, and resolve PagerDuty incidents based on external event data and triggers.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add davepoon/buildwithclaude --skill pagerduty-automation -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

davepoon

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned davepoon/buildwithclaude at fc03a95b41.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
fc03a95b41
Manifest
plugins/all-skills/skills/pagerduty-automation/SKILL.md
Scanned
1 file, 246 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to interact with PagerDuty, enabling actions like creating incidents, acknowledging incidents, and retrieving incident details. It provides a way to automate responses to alerts and manage on-call workflows directly from within an AI agent's capabilities. The skill is designed for integrations requiring real-time incident management.

When to use it

  • Automated Incident Response: Automatically create PagerDuty incidents based on events detected by monitoring systems.
  • On-Call Escalation: Escalate incidents to the appropriate on-call personnel through automated notifications and acknowledgements.
  • Incident Status Updates: Retrieve current incident status and details for reporting or integration with other tools.
  • Post-Mortem Automation: Automatically create summaries of resolved incidents, including timelines and actions taken.

Key capabilities

  • Create Incidents
  • Acknowledge Incidents
  • Retrieve Incident Details

Example prompts

  • "Create a PagerDuty incident for server 'webserver01' with the description 'High CPU utilization'."
  • "Acknowledge incident number 12345 in PagerDuty."
  • "What is the status of incident 67890?"

Tips & gotchas

Requires appropriate API keys and permissions within your PagerDuty account to function correctly. Ensure the AI agent has access to these credentials securely.