Habilidades pagerduty-automation
📦

pagerduty-automation

Seguro ⚙️ Comandos externos🌐 Acceso a red

Automate PagerDuty Incident Management

Manage PagerDuty incidents, services, schedules, and on-call rotations directly from Claude. Streamline incident response workflows without leaving your AI assistant.

Soporta: Claude Codex Code(CC)
🥉 74 Bronce
1

Descargar el ZIP de la skill

2

Subir en Claude

Ve a Configuración → Capacidades → Skills → Subir skill

3

Activa y empieza a usar

Pruébalo

Usando "pagerduty-automation". Who is on-call for the platform team this week?

Resultado esperado:

  • Schedule: Platform Team On-Call
  • Current on-call: John Smith (john.smith@company.com)
  • Rotation: Weekly
  • Next handoff: Monday 9:00 AM UTC

Usando "pagerduty-automation". Create a high-urgency incident titled 'Payment Gateway Timeout' for the checkout service

Resultado esperado:

  • Incident created successfully
  • ID: P123XYZ
  • Status: triggered
  • Service: Checkout API
  • Urgency: high
  • Escalated to: Platform On-Call

Auditoría de seguridad

Seguro
v1 • 2/24/2026

All 112 static findings are FALSE POSITIVES. The SKILL.md file is pure documentation describing PagerDuty automation via Rube MCP server. Static analyzer incorrectly flagged tool names (e.g., PAGERDUTY_FETCH_INCIDENT_LIST) as shell commands, but these are MCP tool identifiers in documentation text only. The hardcoded URL is the legitimate Rube MCP endpoint. No executable code, command injection vectors, or malicious patterns exist.

1
Archivos escaneados
251
Líneas analizadas
2
hallazgos
1
Auditorías totales

Factores de riesgo

⚙️ Comandos externos
No se registraron ubicaciones específicas
🌐 Acceso a red (1)
Auditado por: claude

Puntuación de calidad

38
Arquitectura
100
Mantenibilidad
87
Contenido
50
Comunidad
100
Seguridad
91
Cumplimiento de la especificación

Lo que puedes crear

Incident Responder

Quickly acknowledge or resolve incidents during on-call shifts by running natural language commands like 'Acknowledge incident P123ABC'

DevOps Automation Engineer

Programmatically create incidents, manage service configurations, and set up on-call schedules through Claude Code

Team Lead

View who is currently on-call across all schedules and create or modify escalation policies without logging into PagerDuty

Prueba estos prompts

Check Current On-Call
Who is currently on-call for the production support schedule?
Acknowledge Incident
Acknowledge incident P123ABC with note: 'Working on database connection issue'
Create New Service
Create a new PagerDuty service named 'Checkout API' using escalation policy 'Default' with alert creation set to 'create_incidents'
List Unacknowledged Incidents
List all unacknowledged incidents from the last 2 hours, grouped by service

Mejores prácticas

  • Always call RUBE_SEARCH_TOOLS first to get current available tool schemas before running commands
  • Verify connection status shows ACTIVE before executing workflows
  • Use the preview tool before saving complex schedule changes

Evitar

  • Attempting to create incidents without verifying the PagerDuty connection is active
  • Trying to create a service without an existing escalation policy
  • Attempting to transition incidents backward (resolved -> triggered)

Preguntas frecuentes

Do I need a PagerDuty API key?
No API key needed. The skill uses Rube MCP which handles authentication through OAuth when you connect your PagerDuty account.
Can I create incidents without a service?
No. Incident creation requires a service with both id and type: 'service_reference'. You must create or reference an existing service first.
How do I check if my PagerDuty connection is working?
Run RUBE_MANAGE_CONNECTIONS with toolkit 'pagerduty' and verify the status shows ACTIVE before running any workflows.
Can I transition an incident from resolved back to triggered?
No. PagerDuty incident status transitions are one-way: triggered -> acknowledged -> resolved. You cannot go backward.
What happens if I hit rate limits?
PagerDuty enforces rate limits per account. Implement exponential backoff when receiving 429 responses and space out bulk operations.
Can this skill manage business services and technical services?
Yes. The skill supports both technical services (via PAGERDUTY_CREATE_NEW_SERVICE) and business services (via PAGERDUTY_CREATE_BUSINESS_SERVICE).

Detalles del desarrollador

Estructura de archivos

📄 SKILL.md