원클릭으로
pagerduty
PagerDuty REST API for incidents, on-call schedules, and escalation policies
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
PagerDuty REST API for incidents, on-call schedules, and escalation policies
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | pagerduty |
| description | PagerDuty REST API for incidents, on-call schedules, and escalation policies |
| license | MIT |
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.OpenCode agent runtime — manage sessions, dispatch tasks, repair DB issues, and reset diffs
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.
Load when reviewing a diff, naming a code smell or anti-pattern, deciding refactoring direction, or grading review-comment severity. Required reading when a named pattern is cited — load explicitly rather than paraphrasing from memory.
Load before creating, restacking, or landing a branch in a git-spice–managed stack — branch naming, stack navigation, and conflict/restack recovery. Use instead of raw git commands whenever the repo has a git-spice stack.
Load when investigating production errors, latency, or trace data that requires querying Elasticsearch/APM directly — index patterns, field names, auth setup, and time-range syntax. Use before hand-rolling a query DSL call or guessing field names.
Manage dotfiles via chezmoi — apply safely, destroy files, manage LaunchAgents and externals, config and template gotchas