What problem does it solve? During incident response, engineers waste time manually checking PagerDuty to find who is on-call, whether an alert is a recurring issue, and how long similar incidents typically take to resolve. This Skill pulls that alerting context directly into the investigation workflow. ## Core Features & Use Cases - Incident Lookup: Fetch full details of any PagerDuty incident by ID, including status, urgency, assignments, acknowledgements, and an optional timeline of events. - Incident Listing & Filtering: List incidents filtered by status (triggered, acknowledged, resolved), service, and time range to spot recurring alerts or correlated incidents. - MTTR Calculation: Compute mean, median, p95, min, and max resolution times for a service over a configurable number of days. - Use Case: When a new alert fires, run the incident lookup to see who acknowledged it, list the last 30 days of incidents to check if it is a known recurring issue, and compare its duration against the service's historical MTTR to decide whether to escalate. ## Quick Start Ask the agent to pull the PagerDuty context for incident P123ABC, including its timeline and any similar incidents from the last 30 days.
