skills.rest
jimweller
jimwellerCOMMUNITY
Explore all skills by this author →
GitHub

pagerduty-incident-reader

Retrieve and summarize PagerDuty incident details by incident ID and research context.

2|Updated Feb 14, 2026
Search Tags:#api#alerting#reader#on-call#incident#pagerduty
One-click install
npx skills add https://github.com/jimweller/davit-dataops-dotfiles --skill pagerduty-incident-reader
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pagerduty-incident-reader
Source: https://github.com/jimweller/davit-dataops-dotfiles/tree/main/dataops-plugin/skills/pagerduty-incident-reader
Command: npx skills add https://github.com/jimweller/davit-dataops-dotfiles --skill pagerduty-incident-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you quickly find and extract specific information from PagerDuty incidents relevant to your research context, avoiding the need to sift through lengthy incident reports.

Core Features & Use Cases

  • Targeted Information Extraction: Focuses on details pertinent to a given research question, rather than a full summary.
  • Incident ID Handling: Accurately identifies and processes PagerDuty incident IDs.
  • Use Case: If you are investigating a specific service outage, you can provide the incident ID and a research context like "investigating root cause of checkout failure" to get a concise summary of relevant findings and timeline events.

Quick Start

Use the pagerduty-incident-reader skill to read incident Q0RIJJZL24RC6W for the research context of investigating root cause of checkout failure.

Frequently Asked Questions about pagerduty-incident-reader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract specific details from a PagerDuty incident for root cause analysis?▼

Yes, you can retrieve assignees, service, status, and key timeline events for a PagerDuty incident. By supplying the incident ID and research context, the skill focuses on extracting only the pertinent information rather than a full report.

How do I pull targeted information from PagerDuty incidents without reading the full report?▼

No external dependencies are required to use this skill. It operates independently using a built-in bash script to interact with the PagerDuty API, requiring only your incident ID and research context to function.

How does providing research context help summarize a PagerDuty incident?▼

Providing research context guides the extraction process to focus on specific details relevant to your query. Instead of a generic summary, the skill filters the PagerDuty incident data, notes, and timeline events to match your stated research goals.

What do I need to provide to query a PagerDuty incident using this approach?▼

You need to provide a valid PagerDuty incident ID and a description of your research context. The skill uses these inputs to call the PagerDuty API and extract focused details like incident status, assignees, and timeline events.

Related Skills

Explore More Software Engineering Skills→
incidentfoxincidentfox
654

alerting-context

Fetch on-call rosters, incident history, and MTTR metrics from PagerDuty.

Official
Intermediate
ulises-jeremiasulises-jeremias
2

dots-workstation-incident

Draft and review incident reports and RCA notes for IT operations.

Community
Intermediate
Shakudo-ioShakudo-io

pagerduty-ops

Trigger, acknowledge, and resolve PagerDuty incidents via REST and Events APIs.

Official
Intermediate
sjinkssjinks

pd-incident-alerts

Fetch all alerts for a specific PagerDuty incident via the REST API.

Community
Intermediate