Automate your SRE and incident response workflows with AI-powered PagerDuty triage and management.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install pager-triage
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install pager-triage using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
The PagerDuty Incident Triage skill transforms your AI agent into a high-efficiency first-responder for system outages and alerts. By integrating directly with the PagerDuty REST API v2, this addition to your library of Openclaw Skills allows engineers to query active incidents, investigate alert timelines, and monitor service health through natural language commands. It is designed to bridge the gap between receiving a page and taking action by providing a centralized interface for all incident data.
Security is a core pillar of this skill. It operates in a read-only mode by default, ensuring that sensitive write operations—such as acknowledging or resolving incidents—require explicit human confirmation and the presence of a validated user email. This makes it a safe and reliable choice for teams looking to leverage Openclaw Skills within their production environments without compromising operational integrity.
Navigate to PagerDuty → Settings → API Access Keys and create a new key. Read-only access is recommended for initial setup.
Export the required credentials to your environment to enable the skill:
# Required: Your PagerDuty REST API v2 token
export PAGERDUTY_API_KEY="your_key_here"
# Optional: Required only for ack, resolve, and note operations
export PAGERDUTY_EMAIL="[email protected]"
Test the connection by asking the agent: "What is currently firing on PagerDuty?"
The skill returns structured JSON responses that normalize PagerDuty API data for easy consumption by AI agents and humans alike.
| Component | Description |
|---|---|
| Incident Object | Contains ID, status, urgency, service mapping, and assignment details. |
| Timeline | A chronological list of log entries, including triggers, escalations, and user actions. |
| On-Call | Details regarding the user, schedule name, and escalation level currently active. |
| Stats | Summary metrics including total incident counts and Mean Time to Resolve (MTTR) for specific windows. |
Loading
An operational AI skill that converts meeting transcripts into structured outputs including action items, decisions, and ready-to-send email drafts.

A unified log search engine that translates natural language queries into LogQL, ES DSL, or CloudWatch filter patterns across multiple backends.

A powerful Kubernetes diagnostic toolkit for instant AI-driven cluster triage and incident response using standard kubectl commands.

Analyze and optimize your Hacker News and RSS consumption with AI-generated reports and personalized digests.

A comprehensive bridge between natural language and Prometheus-compatible metrics servers for real-time monitoring and incident triage.

An automated on-chain security auditor for Solana tokens that detects rug-pull risks without requiring API keys or wallet connections.








































