{"id":"0843fc87-a106-498d-b9d4-ee2568e506f9","entityType":"agent","slug":"clawhub-hith3sh-pagerduty-incidents","name":"PagerDuty Incidents","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-pagerduty-incidents","canonicalPath":"/agent/clawhub-hith3sh-pagerduty-incidents","generatedAt":"2026-10-10T02:46:01.842Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T13:54:22.962Z","emptyReason":null},"description":"Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to c... Skill: PagerDuty Incidents Owner: hith3sh Summary: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to c... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:14:55.413Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct t","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.5K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:pagerduty-incidents","sourceUrl":"https://clawhub.ai/hith3sh/pagerduty-incidents","homepage":"https://clawhub.ai/hith3sh/skills/pagerduty-incidents","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/pagerduty-incidents","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/pagerduty-incidents","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":68,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to c..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:54:22.962Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:54:22.962Z","emptyReason":null},"stars":null,"forks":null,"downloads":2533,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"2.5K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T13:54:22.962Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T13:54:22.962Z","lastCrawledAt":"2026-10-09T13:54:22.962Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T13:54:22.962Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-06-09T07:14:55.413Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":5274},{"version":"1.0.5","createdAt":"2026-06-09T06:10:31.888Z","changelog":"- Updated the PagerDuty logo image URL to add a cache-busting query parameter (`?v=2`). - No functional or workflow changes; documentation and usage details remain the same.","fileCount":3,"zipByteSize":5252},{"version":"1.0.4","createdAt":"2026-06-09T05:02:03.597Z","changelog":"- Removed the sample file skill-card.md. - No functional or behavior changes. Documentation and usage remain the same.","fileCount":3,"zipByteSize":5229},{"version":"1.0.1","createdAt":"2026-06-08T16:40:31.355Z","changelog":"- Added PagerDuty brand logo at the top of SKILL.md for improved visual clarity. - Removed redundant skill-card.md file. - No functional or usage changes to skill behavior.","fileCount":3,"zipByteSize":5361},{"version":"0.1.1","createdAt":"2026-06-07T13:34:09.324Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":5268},{"version":"0.1.0","createdAt":"2026-05-17T06:06:14.686Z","changelog":"- Initial release of the PagerDuty-Incidents skill. - Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via ClawLink integration. - Guided setup: install ClawLink plugin, pair account, and connect PagerDuty through a hosted dashboard. - All interactions use ClawLink tools—no direct PagerDuty API credential handling required. - Supports listing, inspecting, creating, updating, and resolving incidents (based on user permissions and available tools). - Emphasizes safe operations with required confirmations for writes or destructive actions.","fileCount":3,"zipByteSize":3456}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:pagerduty-incidents","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T02:46:01.841Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-pagerduty-incidents/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T13:54:22.962Z","emptyReason":null},"readme":"Skill: PagerDuty Incidents\n\nOwner: hith3sh\n\nSummary: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to c...\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-06-09T07:14:55.413Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.5 | 2026-06-09T06:10:31.888Z | auto\n\n- Updated the PagerDuty logo image URL to add a cache-busting query parameter (`?v=2`).\n- No functional or workflow changes; documentation and usage details remain the same.\n\nv1.0.4 | 2026-06-09T05:02:03.597Z | auto\n\n- Removed the sample file skill-card.md.\n- No functional or behavior changes. Documentation and usage remain the same.\n\nv1.0.1 | 2026-06-08T16:40:31.355Z | auto\n\n- Added PagerDuty brand logo at the top of SKILL.md for improved visual clarity.\n- Removed redundant skill-card.md file.\n- No functional or usage changes to skill behavior.\n\nv0.1.1 | 2026-06-07T13:34:09.324Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.0 | 2026-05-17T06:06:14.686Z | auto\n\n- Initial release of the PagerDuty-Incidents skill.\n- Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via ClawLink integration.\n- Guided setup: install ClawLink plugin, pair account, and connect PagerDuty through a hosted dashboard.\n- All interactions use ClawLink tools—no direct PagerDuty API credential handling required.\n- Supports listing, inspecting, creating, updating, and resolving incidents (based on user permissions and available tools).\n- Emphasizes safe operations with required confirmations for writes or destructive actions.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 5274 bytes\n\nFiles: skill-card.md (2338b), SKILL.md (11795b), _meta.json (138b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: pagerduty-incidents\ndescription: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to create, acknowledge, or resolve incidents, manage on-call schedules, and review service health via PagerDuty.\n---\n\n# PagerDuty Incidents\n\n\n\nAccess PagerDuty's incident management platform via the PagerDuty REST API. Manage incidents, services, schedules, escalation policies, users, and on-call data.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=pagerduty-incidents) for hosted connection flows and credentials so you do not need to configure PagerDuty API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect PagerDuty |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect PagerDuty |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ PagerDuty REST │\n│ (User Chat) │ │ (API Key) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect PagerDuty│ │\n │ │ 4. Secure Proxy │\n │ │ 5. API Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ PagerDuty│\n │ File │ │ Auth │ │ Platform │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for PagerDuty again.\"\n\n## Quick Start\n\n```bash\n# List recent incidents\nclawlink_call_tool --tool \"pagerduty_list_incidents\" --params '{\"status\": \"triggered\", \"limit\": 25}'\n\n# Get incident details\nclawlink_call_tool --tool \"pagerduty_get_incident\" --params '{\"incident_id\": \"INCIDENT_ID\"}'\n\n# List services\nclawlink_call_tool --tool \"pagerduty_list_services\" --params '{}'\n```\n\n## Authentication\n\nAll PagerDuty tool calls are authenticated automatically by ClawLink using the user's PagerDuty account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every PagerDuty API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=pagerduty and connect PagerDuty.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `pagerduty` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration pagerduty\n```\n\n**Response:** Returns the live tool catalog for PagerDuty.\n\n### Reconnect\n\nIf PagerDuty tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=pagerduty\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration pagerduty`\n\n## Security& Permissions\n\n- Access is scoped to incidents, services, schedules, and data within the connected PagerDuty account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete service, remove user) must be confirmed.\n- Incident reassignment, escalation changes, and schedule modifications affect real on-call workflows — confirm carefully.\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm PagerDuty is connected.\n2. Call `clawlink_list_tools --integration pagerduty` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `pagerduty`.\n5. If no PagerDuty tools appear, direct the user to https://claw-link.dev/dashboard?add=pagerduty.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List incidents → Get details → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Code Examples\n\n### List incidents\n\n```bash\nclawlink_call_tool --tool \"pagerduty_list_incidents\" \\\n --params '{\n \"statuses\": [\"triggered\", \"acknowledged\"],\n \"limit\": 50,\n \"sort_by\": \"created_at\",\n \"order\": \"desc\"\n }'\n```\n\n### Create an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_create_incident\" \\\n --params '{\n \"title\": \"High CPU usage on prod-server-01\",\n \"service_id\": \"SERVICE_ID\",\n \" urgency\": \"high\",\n \"incident_key\": \"cpu-prod-server-01\",\n \"body\": {\n \"type\": \"incident_body\",\n \"details\": \"CPU usage exceeded 90% for 5 minutes\"\n }\n }'\n```\n\n### Acknowledge an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_acknowledge_incident\" \\\n --params '{\n \"incident_id\": \"INCIDENT_ID\"\n }'\n```\n\n### Get on-call schedule\n\n```bash\nclawlink_call_tool --tool \"pagerduty_get_on_call\" \\\n --params '{\n \"escalation_policy_ids\": [\"ESCALATION_POLICY_ID\"]\n }'\n```\n\n## Notes\n\n- PagerDuty API has rate limits. Use exponential backoff when encountering 429 errors.\n- Incident IDs and service IDs are strings — verify IDs before passing to write operations.\n- Status transitions (triggered → acknowledged → resolved) follow strict rules — not all transitions are valid from all states.\n- On-call queries require escalation policy IDs — list escalation policies first if needed.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration pagerduty`. |\n| Missing connection | PagerDuty is not connected. Direct the user to https://claw-link.dev/dashboard?add=pagerduty. |\n| `not_found` | Incident, service, or user does not exist. Check the ID. |\n| `invalid_state_transition` | Status transition is not allowed from current state. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `pagerduty`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)\n- [Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)\n- [Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=pagerduty-incidents\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [PagerDuty](https://clawhub.ai/hith3sh/pagerduty-incidents) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=pagerduty-incidents)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"pagerduty-incidents\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1780989295413\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nManage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, site reliability engineers, and incident responders use this skill to inspect PagerDuty state and manage incident workflows from an agent chat. It supports listing and updating incidents, services, schedules, escalation policies, users, and on-call data through the connected PagerDuty account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill asks users to install and allow an unpinned third-party plugin that can mediate PagerDuty credentials and operational changes.\n\nMitigation: Use least-privilege PagerDuty access, review the plugin before installing, and prefer a pinned or verified ClawLink plugin release when available.\n\nRisk: PagerDuty write operations can affect production incident response, escalation, schedules, services, or users.\n\nMitigation: Confirm every create, update, delete, reassignment, escalation, and schedule change with the user before execution.\n\n## Reference(s):\n\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)\n- [PagerDuty Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)\n- [PagerDuty Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, API Calls, Configuration]\n\n**Output Format:** [Markdown with inline shell commands and JSON parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses the live ClawLink PagerDuty tool catalog; write operations should be previewed and confirmed before execution.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 3 files, 5252 bytes\n\nFiles: skill-card.md (2523b), SKILL.md (11579b), _meta.json (138b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: pagerduty-incidents\ndescription: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to create, acknowledge, or resolve incidents, manage on-call schedules, and review service health via PagerDuty.\n---\n\n# PagerDuty Incidents\n\n\n\nAccess PagerDuty's incident management platform via the PagerDuty REST API. Manage incidents, services, schedules, escalation policies, users, and on-call data.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure PagerDuty API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect PagerDuty |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect PagerDuty |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ PagerDuty REST │\n│ (User Chat) │ │ (API Key) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect PagerDuty│ │\n │ │ 4. Secure Proxy │\n │ │ 5. API Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ PagerDuty│\n │ File │ │ Auth │ │ Platform │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for PagerDuty again.\"\n\n## Quick Start\n\n```bash\n# List recent incidents\nclawlink_call_tool --tool \"pagerduty_list_incidents\" --params '{\"status\": \"triggered\", \"limit\": 25}'\n\n# Get incident details\nclawlink_call_tool --tool \"pagerduty_get_incident\" --params '{\"incident_id\": \"INCIDENT_ID\"}'\n\n# List services\nclawlink_call_tool --tool \"pagerduty_list_services\" --params '{}'\n```\n\n## Authentication\n\nAll PagerDuty tool calls are authenticated automatically by ClawLink using the user's PagerDuty account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every PagerDuty API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=pagerduty and connect PagerDuty.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `pagerduty` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration pagerduty\n```\n\n**Response:** Returns the live tool catalog for PagerDuty.\n\n### Reconnect\n\nIf PagerDuty tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=pagerduty\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration pagerduty`\n\n## Security& Permissions\n\n- Access is scoped to incidents, services, schedules, and data within the connected PagerDuty account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete service, remove user) must be confirmed.\n- Incident reassignment, escalation changes, and schedule modifications affect real on-call workflows — confirm carefully.\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm PagerDuty is connected.\n2. Call `clawlink_list_tools --integration pagerduty` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `pagerduty`.\n5. If no PagerDuty tools appear, direct the user to https://claw-link.dev/dashboard?add=pagerduty.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List incidents → Get details → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Code Examples\n\n### List incidents\n\n```bash\nclawlink_call_tool --tool \"pagerduty_list_incidents\" \\\n --params '{\n \"statuses\": [\"triggered\", \"acknowledged\"],\n \"limit\": 50,\n \"sort_by\": \"created_at\",\n \"order\": \"desc\"\n }'\n```\n\n### Create an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_create_incident\" \\\n --params '{\n \"title\": \"High CPU usage on prod-server-01\",\n \"service_id\": \"SERVICE_ID\",\n \" urgency\": \"high\",\n \"incident_key\": \"cpu-prod-server-01\",\n \"body\": {\n \"type\": \"incident_body\",\n \"details\": \"CPU usage exceeded 90% for 5 minutes\"\n }\n }'\n```\n\n### Acknowledge an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_acknowledge_incident\" \\\n --params '{\n \"incident_id\": \"INCIDENT_ID\"\n }'\n```\n\n### Get on-call schedule\n\n```bash\nclawlink_call_tool --tool \"pagerduty_get_on_call\" \\\n --params '{\n \"escalation_policy_ids\": [\"ESCALATION_POLICY_ID\"]\n }'\n```\n\n## Notes\n\n- PagerDuty API has rate limits. Use exponential backoff when encountering 429 errors.\n- Incident IDs and service IDs are strings — verify IDs before passing to write operations.\n- Status transitions (triggered → acknowledged → resolved) follow strict rules — not all transitions are valid from all states.\n- On-call queries require escalation policy IDs — list escalation policies first if needed.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration pagerduty`. |\n| Missing connection | PagerDuty is not connected. Direct the user to https://claw-link.dev/dashboard?add=pagerduty. |\n| `not_found` | Incident, service, or user does not exist. Check the ID. |\n| `invalid_state_transition` | Status transition is not allowed from current state. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `pagerduty`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)\n- [Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)\n- [Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [PagerDuty](https://clawhub.ai/hith3sh/pagerduty-incidents) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"pagerduty-incidents\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780985431888\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:
\nManage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, incident responders, and operations teams use this skill to inspect PagerDuty incidents and service health, manage on-call workflows, and perform confirmed changes through ClawLink-backed PagerDuty tools.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can operate on PagerDuty incidents, schedules, escalation policies, services, and users through a connected account.
\nMitigation: Review the PagerDuty permissions granted during connection and require clear preview plus explicit confirmation before any incident, schedule, escalation, service, or user-changing action.
\nRisk: Credential-backed access depends on ClawLink and its OpenClaw plugin being trusted with PagerDuty access.
\nMitigation: Install only when ClawLink is trusted for the PagerDuty account and verify the active PagerDuty integration before making tool calls.
\n\n\n## Reference(s):
\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)
\n- [PagerDuty Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)
\n- [PagerDuty Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)
\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/pagerduty-incidents)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline bash commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires a connected PagerDuty account through ClawLink; write operations require explicit user confirmation.]
\n\n## Skill Version(s):
\n1.0.5 (source: server-resolved release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.4: 3 files, 5229 bytes\n\nFiles: skill-card.md (2362b), SKILL.md (11575b), _meta.json (138b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: pagerduty-incidents\ndescription: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to create, acknowledge, or resolve incidents, manage on-call schedules, and review service health via PagerDuty.\n---\n\n# PagerDuty Incidents\n\n\n\nAccess PagerDuty's incident management platform via the PagerDuty REST API. Manage incidents, services, schedules, escalation policies, users, and on-call data.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure PagerDuty API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect PagerDuty |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect PagerDuty |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ PagerDuty REST │\n│ (User Chat) │ │ (API Key) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect PagerDuty│ │\n │ │ 4. Secure Proxy │\n │ │ 5. API Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ PagerDuty│\n │ File │ │ Auth │ │ Platform │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for PagerDuty again.\"\n\n## Quick Start\n\n```bash\n# List recent incidents\nclawlink_call_tool --tool \"pagerduty_list_incidents\" --params '{\"status\": \"triggered\", \"limit\": 25}'\n\n# Get incident details\nclawlink_call_tool --tool \"pagerduty_get_incident\" --params '{\"incident_id\": \"INCIDENT_ID\"}'\n\n# List services\nclawlink_call_tool --tool \"pagerduty_list_services\" --params '{}'\n```\n\n## Authentication\n\nAll PagerDuty tool calls are authenticated automatically by ClawLink using the user's PagerDuty account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every PagerDuty API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=pagerduty and connect PagerDuty.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `pagerduty` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration pagerduty\n```\n\n**Response:** Returns the live tool catalog for PagerDuty.\n\n### Reconnect\n\nIf PagerDuty tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=pagerduty\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration pagerduty`\n\n## Security& Permissions\n\n- Access is scoped to incidents, services, schedules, and data within the connected PagerDuty account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete service, remove user) must be confirmed.\n- Incident reassignment, escalation changes, and schedule modifications affect real on-call workflows — confirm carefully.\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm PagerDuty is connected.\n2. Call `clawlink_list_tools --integration pagerduty` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `pagerduty`.\n5. If no PagerDuty tools appear, direct the user to https://claw-link.dev/dashboard?add=pagerduty.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List incidents → Get details → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Code Examples\n\n### List incidents\n\n```bash\nclawlink_call_tool --tool \"pagerduty_list_incidents\" \\\n --params '{\n \"statuses\": [\"triggered\", \"acknowledged\"],\n \"limit\": 50,\n \"sort_by\": \"created_at\",\n \"order\": \"desc\"\n }'\n```\n\n### Create an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_create_incident\" \\\n --params '{\n \"title\": \"High CPU usage on prod-server-01\",\n \"service_id\": \"SERVICE_ID\",\n \" urgency\": \"high\",\n \"incident_key\": \"cpu-prod-server-01\",\n \"body\": {\n \"type\": \"incident_body\",\n \"details\": \"CPU usage exceeded 90% for 5 minutes\"\n }\n }'\n```\n\n### Acknowledge an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_acknowledge_incident\" \\\n --params '{\n \"incident_id\": \"INCIDENT_ID\"\n }'\n```\n\n### Get on-call schedule\n\n```bash\nclawlink_call_tool --tool \"pagerduty_get_on_call\" \\\n --params '{\n \"escalation_policy_ids\": [\"ESCALATION_POLICY_ID\"]\n }'\n```\n\n## Notes\n\n- PagerDuty API has rate limits. Use exponential backoff when encountering 429 errors.\n- Incident IDs and service IDs are strings — verify IDs before passing to write operations.\n- Status transitions (triggered → acknowledged → resolved) follow strict rules — not all transitions are valid from all states.\n- On-call queries require escalation policy IDs — list escalation policies first if needed.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration pagerduty`. |\n| Missing connection | PagerDuty is not connected. Direct the user to https://claw-link.dev/dashboard?add=pagerduty. |\n| `not_found` | Incident, service, or user does not exist. Check the ID. |\n| `invalid_state_transition` | Status transition is not allowed from current state. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `pagerduty`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)\n- [Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)\n- [Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [PagerDuty](https://clawhub.ai/hith3sh/pagerduty-incidents) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"pagerduty-incidents\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1780981323597\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nManage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and operations teams use this skill to inspect PagerDuty incidents and on-call data, then create, acknowledge, resolve, or update PagerDuty resources through ClawLink-mediated tool calls.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill connects ClawLink to a PagerDuty account and can access sensitive incident and on-call data.
\nMitigation: Install only when ClawLink is trusted, review the PagerDuty permissions granted during connection, and avoid exposing PagerDuty credentials in chat.
\nRisk: Incident, schedule, escalation, service, or user changes can affect real on-call workflows.
\nMitigation: Require explicit user confirmation before write or destructive actions, preview changes when available, and verify target resource identifiers before execution.
\n\n\n## Reference(s):
\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)
\n- [PagerDuty Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)
\n- [PagerDuty Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/pagerduty-incidents)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, configuration, API calls, text]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses the live ClawLink PagerDuty tool catalog as the source of truth before making tool calls.]
\n\n## Skill Version(s):
\n1.0.4 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 5361 bytes\n\nFiles: skill-card.md (2844b), SKILL.md (11575b), _meta.json (138b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: pagerduty-incidents\ndescription: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to create, acknowledge, or resolve incidents, manage on-call schedules, and review service health via PagerDuty.\n---\n\n# PagerDuty Incidents\n\n\n\nAccess PagerDuty's incident management platform via the PagerDuty REST API. Manage incidents, services, schedules, escalation policies, users, and on-call data.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure PagerDuty API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect PagerDuty |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect PagerDuty |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ PagerDuty REST │\n│ (User Chat) │ │ (API Key) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect PagerDuty│ │\n │ │ 4. Secure Proxy │\n │ │ 5. API Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ PagerDuty│\n │ File │ │ Auth │ │ Platform │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for PagerDuty again.\"\n\n## Quick Start\n\n```bash\n# List recent incidents\nclawlink_call_tool --tool \"pagerduty_list_incidents\" --params '{\"status\": \"triggered\", \"limit\": 25}'\n\n# Get incident details\nclawlink_call_tool --tool \"pagerduty_get_incident\" --params '{\"incident_id\": \"INCIDENT_ID\"}'\n\n# List services\nclawlink_call_tool --tool \"pagerduty_list_services\" --params '{}'\n```\n\n## Authentication\n\nAll PagerDuty tool calls are authenticated automatically by ClawLink using the user's PagerDuty account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every PagerDuty API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=pagerduty and connect PagerDuty.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `pagerduty` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration pagerduty\n```\n\n**Response:** Returns the live tool catalog for PagerDuty.\n\n### Reconnect\n\nIf PagerDuty tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=pagerduty\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration pagerduty`\n\n## Security& Permissions\n\n- Access is scoped to incidents, services, schedules, and data within the connected PagerDuty account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete service, remove user) must be confirmed.\n- Incident reassignment, escalation changes, and schedule modifications affect real on-call workflows — confirm carefully.\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm PagerDuty is connected.\n2. Call `clawlink_list_tools --integration pagerduty` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `pagerduty`.\n5. If no PagerDuty tools appear, direct the user to https://claw-link.dev/dashboard?add=pagerduty.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List incidents → Get details → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Code Examples\n\n### List incidents\n\n```bash\nclawlink_call_tool --tool \"pagerduty_list_incidents\" \\\n --params '{\n \"statuses\": [\"triggered\", \"acknowledged\"],\n \"limit\": 50,\n \"sort_by\": \"created_at\",\n \"order\": \"desc\"\n }'\n```\n\n### Create an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_create_incident\" \\\n --params '{\n \"title\": \"High CPU usage on prod-server-01\",\n \"service_id\": \"SERVICE_ID\",\n \" urgency\": \"high\",\n \"incident_key\": \"cpu-prod-server-01\",\n \"body\": {\n \"type\": \"incident_body\",\n \"details\": \"CPU usage exceeded 90% for 5 minutes\"\n }\n }'\n```\n\n### Acknowledge an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_acknowledge_incident\" \\\n --params '{\n \"incident_id\": \"INCIDENT_ID\"\n }'\n```\n\n### Get on-call schedule\n\n```bash\nclawlink_call_tool --tool \"pagerduty_get_on_call\" \\\n --params '{\n \"escalation_policy_ids\": [\"ESCALATION_POLICY_ID\"]\n }'\n```\n\n## Notes\n\n- PagerDuty API has rate limits. Use exponential backoff when encountering 429 errors.\n- Incident IDs and service IDs are strings — verify IDs before passing to write operations.\n- Status transitions (triggered → acknowledged → resolved) follow strict rules — not all transitions are valid from all states.\n- On-call queries require escalation policy IDs — list escalation policies first if needed.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration pagerduty`. |\n| Missing connection | PagerDuty is not connected. Direct the user to https://claw-link.dev/dashboard?add=pagerduty. |\n| `not_found` | Incident, service, or user does not exist. Check the ID. |\n| `invalid_state_transition` | Status transition is not allowed from current state. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `pagerduty`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)\n- [Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)\n- [Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [PagerDuty](https://clawhub.ai/hith3sh/pagerduty-incidents) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"pagerduty-incidents\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780936831355\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nManage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nOperations engineers, SREs, incident commanders, and on-call responders use this skill to inspect and manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data from an agent workflow.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires ClawLink access to a connected PagerDuty account, which may expose sensitive incident, schedule, escalation, service, and user data.
\nMitigation: Install only if the user trusts ClawLink with PagerDuty access, and review the connected PagerDuty permissions before use.
\nRisk: Write actions can change real incident response state, on-call schedules, escalation policies, services, or users.
\nMitigation: Require explicit user confirmation for create, update, delete, reassignment, escalation, and schedule-modification actions before execution.
\nRisk: Incorrect resource IDs or invalid incident status transitions can cause failed or unintended PagerDuty operations.
\nMitigation: List or retrieve target resources first, describe unfamiliar tools, preview write calls where available, and report PagerDuty errors without inventing results.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/pagerduty-incidents)
\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)
\n- [PagerDuty Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)
\n- [PagerDuty Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include PagerDuty tool-call parameters, setup steps, connection checks, previews for write actions, and error-handling guidance.]
\n\n## Skill Version(s):
\n1.0.1 (source: release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.1: 3 files, 5268 bytes\n\nFiles: skill-card.md (2627b), SKILL.md (11450b), _meta.json (138b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: pagerduty-incidents\ndescription: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to create, acknowledge, or resolve incidents, manage on-call schedules, and review service health via PagerDuty.\n---\n\n# PagerDuty Incidents\n\nAccess PagerDuty's incident management platform via the PagerDuty REST API. Manage incidents, services, schedules, escalation policies, users, and on-call data.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure PagerDuty API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect PagerDuty |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect PagerDuty |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ PagerDuty REST │\n│ (User Chat) │ │ (API Key) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect PagerDuty│ │\n │ │ 4. Secure Proxy │\n │ │ 5. API Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ PagerDuty│\n │ File │ │ Auth │ │ Platform │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for PagerDuty again.\"\n\n## Quick Start\n\n```bash\n# List recent incidents\nclawlink_call_tool --tool \"pagerduty_list_incidents\" --params '{\"status\": \"triggered\", \"limit\": 25}'\n\n# Get incident details\nclawlink_call_tool --tool \"pagerduty_get_incident\" --params '{\"incident_id\": \"INCIDENT_ID\"}'\n\n# List services\nclawlink_call_tool --tool \"pagerduty_list_services\" --params '{}'\n```\n\n## Authentication\n\nAll PagerDuty tool calls are authenticated automatically by ClawLink using the user's PagerDuty account.\n\n**No API key is required in chat.** ClawLink stores the API key securely and injects it into every PagerDuty API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=pagerduty and connect PagerDuty.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `pagerduty` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration pagerduty\n```\n\n**Response:** Returns the live tool catalog for PagerDuty.\n\n### Reconnect\n\nIf PagerDuty tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=pagerduty\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration pagerduty`\n\n## Security& Permissions\n\n- Access is scoped to incidents, services, schedules, and data within the connected PagerDuty account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete service, remove user) must be confirmed.\n- Incident reassignment, escalation changes, and schedule modifications affect real on-call workflows — confirm carefully.\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm PagerDuty is connected.\n2. Call `clawlink_list_tools --integration pagerduty` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `pagerduty`.\n5. If no PagerDuty tools appear, direct the user to https://claw-link.dev/dashboard?add=pagerduty.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List incidents → Get details → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Code Examples\n\n### List incidents\n\n```bash\nclawlink_call_tool --tool \"pagerduty_list_incidents\" \\\n --params '{\n \"statuses\": [\"triggered\", \"acknowledged\"],\n \"limit\": 50,\n \"sort_by\": \"created_at\",\n \"order\": \"desc\"\n }'\n```\n\n### Create an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_create_incident\" \\\n --params '{\n \"title\": \"High CPU usage on prod-server-01\",\n \"service_id\": \"SERVICE_ID\",\n \" urgency\": \"high\",\n \"incident_key\": \"cpu-prod-server-01\",\n \"body\": {\n \"type\": \"incident_body\",\n \"details\": \"CPU usage exceeded 90% for 5 minutes\"\n }\n }'\n```\n\n### Acknowledge an incident\n\n```bash\nclawlink_call_tool --tool \"pagerduty_acknowledge_incident\" \\\n --params '{\n \"incident_id\": \"INCIDENT_ID\"\n }'\n```\n\n### Get on-call schedule\n\n```bash\nclawlink_call_tool --tool \"pagerduty_get_on_call\" \\\n --params '{\n \"escalation_policy_ids\": [\"ESCALATION_POLICY_ID\"]\n }'\n```\n\n## Notes\n\n- PagerDuty API has rate limits. Use exponential backoff when encountering 429 errors.\n- Incident IDs and service IDs are strings — verify IDs before passing to write operations.\n- Status transitions (triggered → acknowledged → resolved) follow strict rules — not all transitions are valid from all states.\n- On-call queries require escalation policy IDs — list escalation policies first if needed.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration pagerduty`. |\n| Missing connection | PagerDuty is not connected. Direct the user to https://claw-link.dev/dashboard?add=pagerduty. |\n| `not_found` | Incident, service, or user does not exist. Check the ID. |\n| `invalid_state_transition` | Status transition is not allowed from current state. |\n| `validation_error` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Rate limited | Too many requests. Wait and retry with exponential backoff. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `pagerduty`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)\n- [Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)\n- [Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [PagerDuty](https://clawhub.ai/hith3sh/pagerduty-incidents) — For this skill's native documentation\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.1.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"pagerduty-incidents\",\n \"version\": \"0.1.1\",\n \"publishedAt\": 1780839249324\n}\n\nFile v0.1.1:skill-card.md\n\n## Description:
\nManage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, operators, and incident response teams use this skill to inspect PagerDuty state and perform incident, service, schedule, escalation policy, user, and on-call workflows through ClawLink-mediated PagerDuty API tools.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires ClawLink to hold and proxy access to a PagerDuty account.
\nMitigation: Install only when the user trusts ClawLink with PagerDuty access, and verify that the PagerDuty connection is active before using live tools.
\nRisk: The skill can create, acknowledge, resolve, and modify PagerDuty resources that affect real incident response workflows.
\nMitigation: Preview and confirm write actions only after checking the target incident, service, schedule, escalation policy, or user.
\nRisk: Destructive or workflow-changing actions can remove services or users, reassign incidents, change escalations, or alter schedules.
\nMitigation: Require explicit confirmation for destructive actions and prefer read, list, search, and describe operations before executing changes.
\n\n\n## Reference(s):
\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)
\n- [PagerDuty Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)
\n- [PagerDuty Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/pagerduty-incidents)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses ClawLink-hosted PagerDuty tools; write actions require explicit user confirmation.]
\n\n## Skill Version(s):
\n0.1.1 (source: release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.0: 3 files, 3456 bytes\n\nFiles: skill-card.md (2361b), SKILL.md (5029b), _meta.json (138b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: pagerduty-incidents\ndescription: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data - powered by ClawLink.\n---\n\n# PagerDuty\n\nWork with PagerDuty from chat - manage incidents, services, schedules, escalation policies, users, and on-call data.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure PagerDuty API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect PagerDuty at [claw-link.dev/dashboard?add=pagerduty](https://claw-link.dev/dashboard?add=pagerduty)\n7. When the user confirms PagerDuty is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `pagerduty` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting PagerDuty\n\nTell the user to open https://claw-link.dev/dashboard?add=pagerduty and connect PagerDuty there. The page opens the add-connection panel filtered to PagerDuty. ClawLink's hosted page runs the provider connection flow. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `pagerduty`.\n\n## Using PagerDuty tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm PagerDuty is connected.\n2. Call `clawlink_list_tools` with integration `pagerduty`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `pagerduty`.\n5. If no PagerDuty tools appear, direct the user to https://claw-link.dev/dashboard?add=pagerduty.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer read, list, search, and get operations before writes.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical PagerDuty tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- List incidents, services, users, and schedules\n- Inspect on-call and escalation policy data\n- Create or update incidents after confirmation\n- Acknowledge, resolve, or reassign incidents after confirmation\n- Review service health and response workflows\n\n## Rules\n\n- Always use ClawLink tools for PagerDuty. Do not ask the user for separate PagerDuty credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before destructive, external-facing, or bulk write actions.\n- If PagerDuty is not connected, direct the user to https://claw-link.dev/dashboard?add=pagerduty.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- PagerDuty API: https://developer.pagerduty.com/api-reference/\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"pagerduty-incidents\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1778997974686\n}\n\nFile v0.1.0:skill-card.md\n\n## Description:
\nManage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data - powered by ClawLink.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and incident responders use this skill to work with PagerDuty incidents, services, schedules, escalation policies, users, and on-call data through ClawLink. It guides setup, discovers the live PagerDuty tool catalog, and requires preview or confirmation for write actions.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can guide actions that create, update, acknowledge, resolve, reassign, or bulk-modify PagerDuty data.
\nMitigation: Review the ClawLink plugin and service before pairing, grant only needed PagerDuty access, and carefully confirm any write or bulk action.
\nRisk: Tool availability depends on the user's connected PagerDuty account, permissions, scopes, and the current ClawLink catalog.
\nMitigation: Discover integrations and tools in the current turn, describe unfamiliar tools before use, and report live tool errors directly.
\n\n\n## Reference(s):
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [PagerDuty API Reference](https://developer.pagerduty.com/api-reference/)
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/pagerduty-incidents)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, API calls, configuration]
\n**Output Format:** [Markdown with inline shell commands and tool-call guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses the live ClawLink PagerDuty catalog as the source of truth and gates writes with preview or user confirmation.]
\n\n## Skill Version(s):
\n0.1.0 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: PagerDuty Incidents Owner: hith3sh Summary: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to c... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:14:55.413Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct t","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ PagerDuty REST │\n│ (User Chat) │ │ (API Key) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect PagerDuty│ │\n │ │ 4. Secure Proxy │\n │ │ 5. API Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ PagerDuty│\n │ File │ │ Auth │ │ Platform │\n └──────────┘ └──────────┘ └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# List recent incidents\nclawlink_call_tool --tool \"pagerduty_list_incidents\" --params '{\"status\": \"triggered\", \"limit\": 25}'\n\n# Get incident details\nclawlink_call_tool --tool \"pagerduty_get_incident\" --params '{\"incident_id\": \"INCIDENT_ID\"}'\n\n# List services\nclawlink_call_tool --tool \"pagerduty_list_services\" --params '{}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration pagerduty"},{"language":"text","snippet":"┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List incidents → Get details → Show status │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: pagerduty-incidents\ndescription: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to create, acknowledge, or resolve incidents, manage on-call schedules, and review service health via PagerDuty.\n---\n\n# PagerDuty Incidents\n\n\n\nAccess PagerDuty's incident management platform via the PagerDuty REST API. Manage incidents, services, schedules, escalation policies, users, and on-call data.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=pagerduty-incidents) for hosted connection flows and credentials so you do not need to configure PagerDuty API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect PagerDuty |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect PagerDuty |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ PagerDuty REST │\n│ (User Chat) │ │ (API Key) │ │ API │\n└─────────────────┘ └──────────────┘ └──────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect PagerDuty│ │\n │ │ 4. Secure Proxy │\n │ │ 5. API Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ PagerDuty│\n │ File │ │ Auth │ │ Platform │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for PagerDuty again.\"\n\n## Quick Start\n\n```bash\n# List recent incidents\nclawlink_call_tool --tool \"pagerduty_list_incidents\" --params '{\"status\": \"triggered\", \"limit\": 25}'\n\n# Get incide"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"pagerduty-incidents\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1780989295413\n}"},{"path":"skill-card.md","content":"## Description:\n\nManage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, site reliability engineers, and incident responders use this skill to inspect PagerDuty state and manage incident workflows from an agent chat. It supports listing and updating incidents, services, schedules, escalation policies, users, and on-call data through the connected PagerDuty account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill asks users to install and allow an unpinned third-party plugin that can mediate PagerDuty credentials and operational changes.\n\nMitigation: Use least-privilege PagerDuty access, review the plugin before installing, and prefer a pinned or verified ClawLink plugin release when available.\n\nRisk: PagerDuty write operations can affect production incident response, escalation, schedules, services, or users.\n\nMitigation: Confirm every create, update, delete, reassignment, escalation, and schedule change with the user before execution.\n\n## Reference(s):\n\n- [PagerDuty REST API Reference](https://developer.pagerduty.com/api-reference/)\n- [PagerDuty Incidents API](https://developer.pagerduty.com/api-reference/rZMyfN/incidents/)\n- [PagerDuty Services API](https://developer.pagerduty.com/api-reference/R4FyWD/services/)\n- [ClawLink OpenClaw Documentation](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, API Calls, Configuration]\n\n**Output Format:** [Markdown with inline shell commands and JSON parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses the live ClawLink PagerDuty tool catalog; write operations should be previewed and confirmed before execution.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to c... Skill: PagerDuty Incidents Owner: hith3sh Summary: Manage PagerDuty incidents, services, schedules, escalation policies, users, and on-call data via the PagerDuty REST API. Use this skill when users want to c... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:14:55.413Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct t","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1046,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T13:54:22.962Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T13:54:22.962Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T02:46:01.842Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}