pagerduty-oncall
PagerDuty On-Call Incident Investigator
Authenticate, list escalation policies, fetch all incidents and their details, then analyse relevance across on-call teams.
Inputs
Raw arguments: $ARGUMENTS
Infer from the arguments:
- QUERY: what to investigate. Defaults to "incidents today". Interpret the time range to derive --since and --until dates (YYYY-MM-DD) in UTC (not local timezone). See the date derivation table in Step 5.
- MODE: Inferred from QUERY.
- If QUERY starts with "incident " or contains a PagerDuty URL (matching
pagerduty\.com/incidents/([A-Z0-9]+)) → SINGLE-INCIDENT mode - Otherwise → LIST mode (existing behaviour)
- If QUERY starts with "incident " or contains a PagerDuty URL (matching
- SINCE: (optional) UTC ISO8601 start of analysis window. Takes precedence over QUERY-derived dates in LIST mode.
- UNTIL: (optional) UTC ISO8601 end of analysis window. Takes precedence over QUERY-derived dates in LIST mode.
- TZ_DISPLAY: (optional) Timezone abbreviation for report display (e.g. the output of
date +"%Z"on the calling machine). When provided, use this for all report timestamps instead of detecting via system clock.
Target Escalation Policies
More from delexw/claude-code-misc
oxlint
Run and configure oxlint — the high-performance JavaScript/TypeScript linter built on the Oxc compiler stack. Use this skill whenever working in a project that has oxlint installed (check for `oxlint` in package.json devDependencies or an `.oxlintrc.json` / `oxlint.config.ts` config file). This includes when you need to lint code after making changes, fix linting errors, configure oxlint rules/plugins, set up or modify `.oxlintrc.json`, or migrate from ESLint.
282pir
Create Post Incident Records (PIRs) by discovering issues from PagerDuty, Datadog, Cloudflare, and Rollbar concurrently. Orchestrates pagerduty-oncall, datadog-analyser, cloudflare-traffic-investigator, and rollbar-reader skills, auto-determines severity, and outputs completed PIR forms. Use when asked to "create a PIR", "write a post incident record", "fill out PIR form", "incident report", "analyse incidents", or after on-call shifts need documentation.
63figma-reader
Read Figma designs via Figma MCP server. Auto-detects MCP availability and prompts user only if setup is needed. Use when Figma links or UI design images are found in task context.
62forge
Forge implementation from JIRA tickets using dynamic skill generation. Gathers context into a lazy-loaded skill, then invokes it for execution. Use when given a JIRA ticket URL to process end-to-end.
60jira-ticket-viewer
View Jira ticket details using the jira CLI (jira-cli). Use when given a Jira issue key to fetch and display ticket information.
55confluence-page-viewer
Read Confluence page content using the confluence CLI. Use when given a Confluence page URL to fetch and display page information.
54