Pagerduty
npx -y skills add athal7/dotfiles --skill pagerdutyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
PagerDuty REST API for incidents, on-call schedules, and escalation policies
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.1 KB, as published. Nobody here has run it
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
Role permissions table
| 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 |
Notes
- Incident IDs: short
incident_number(integer) vs long ID (e.g.P12ABCD). Write endpoints use the long ID. /oncallswith no filter returns the entire account roster — filter byescalation_policy_ids[]orschedule_ids[]for large orgs.- Pagination: list endpoints default to 25 items. Add
&limit=100&offset=0for more.