Skill Detail

Incident Response Checklist Engine

Generates and tracks incident response checklists using PagerDuty Incident Workflows API and Statuspage.io API. Automates severity classification, stakeholder notification, and post-incident review scheduling with Jira Service Management integration.

Runbooks & DiagnosticsClaude Agents
Runbooks & Diagnostics Claude Agents Published
Tool match: pagerduty
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill incident-response-checklist-engine Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Author
PagerDuty
Last updated
Mar 20, 2026
Quick brief

The Incident Response Checklist Engine skill provides structured incident management workflows that guide teams through detection, triage, mitigation, and resolution phases. It integrates with PagerDuty Incident Workflows API to automate response procedures based on incident severity and affected services.

How it works

What this skill actually does

The skill classifies incident severity (SEV1-SEV4) based on configurable criteria including affected user count, service criticality, and blast radius. Each severity level triggers a corresponding checklist with phase-appropriate tasks: initial assessment, communication setup, investigation, mitigation, resolution, and post-incident review.

Statuspage.io API integration enables automatic incident creation and status updates. The skill manages component status transitions (operational โ†’ degraded_performance โ†’ partial_outage โ†’ major_outage) and posts real-time updates visible to end users. Template-based update messages ensure consistent communication.

Stakeholder notification chains are managed through PagerDuty escalation policies with automatic escalation timers. The skill integrates with Jira Service Management to create post-incident review tickets with pre-populated timelines, assign action items to responsible parties, and schedule retrospective meetings via calendar API integration.