skills/pagerduty/SKILL.md
PagerDuty REST API for incidents, on-call schedules, and escalation policies
npx skillsauth add athal7/dotfiles pagerdutyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Base URL: https://api.pagerduty.com
Write actions need: From: <email> — fetch from /users/me first.
Spec: https://raw.githubusercontent.com/PagerDuty/api-schema/main/REST/openapi.yaml
| Action | Works at user role? |
|---|---|
| Read endpoints (oncalls, incidents, services) | ✅ |
| POST /incidents (ack, resolve, snooze, note) | ✅ requires From: header |
| PUT /services/{id} name/description | ✅ if manager on service team |
| PUT /services/{id} other fields | ❌ silent — field echoes but is dropped |
| POST /addons | ❌ 403 admin-only |
| POST /incident_workflows write | ❌ admin-only |
incident_number (integer) vs long ID (e.g. P12ABCD). Write endpoints use the long ID./oncalls with no filter returns the entire account roster — filter by escalation_policy_ids[] or schedule_ids[] for large orgs.&limit=100&offset=0 for more.development
Zoom meeting captions — file locations and format
tools
macOS dictation custom vocabulary — sync knowledge base names and terms to the system spelling dictionary
testing
Look up people, projects, products, and decisions locally first: contact info (email, Slack ID, GitHub handle), titles and teams, project/product status, who works on what, and past decisions. Check before searching Slack, email, calendar, or GitHub — this is the first stop for any contact detail, project context, or decision-history question.
testing
Communication style, audience awareness, and AI-authorship markers for human-facing prose — load when composing chat messages, review comments, merge request descriptions, emails, doc bodies, or ticket descriptions