Saltar al contenido
TakoAPI
Volver a skills

pager-triage

por tkuehnl

Coding Agents & IDEs
—Aún sin valoraciones
Tu valoración

Resumen

AI-powered incident triage for PagerDuty.

Descripción

Qué hace esta skill

Connects to PagerDuty's REST API to list active incidents, view timelines and alert correlations, check on-call schedules, and take actions like acknowledge, resolve, and annotate. Read-only by default; write operations require an explicit --confirm flag.

Handles the full triage loop, from listing incidents to acknowledging and annotating, without leaving the agent, and enforces confirmation gates on all write operations to prevent accidental changes.

Cuándo usarla

  • Checking what incidents are currently firing during an outage
  • Finding who is on call for a specific service right now
  • Acknowledging a triggered incident to stop further escalation
  • Adding a root cause note to an incident's timeline
  • Reviewing recent incident history for a service over the past 7 or 30 days

Flujo de trabajo de ejemplo

ENTRADA

User asks: What's currently firing on PagerDuty?

AGENTE
  1. 1

    Calls pd_incidents to retrieve all triggered and acknowledged incidents

  2. 2

    Sorts results by urgency (high first) and duration (oldest first)

  3. 3

    Calls pd_incident_detail on the highest urgency incident to get timeline and alert correlation

  4. 4

    Returns a summary of all active incidents with detailed context on the most critical one

SALIDA

List of 3 active incidents with the highest-urgency incident's full timeline, trigger source, escalation history, and recommended next steps

Requisitos

  • PAGERDUTY_API_KEY environment variable (PagerDuty REST API v2 token)
  • PAGERDUTY_EMAIL environment variable (required only for write operations: ack, resolve, note)

Instalación

clawhub install tkuehnl/pager-triage

Ejecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.

Enlaces