[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7147XEBNEAA6H7RBF71W9KY":3,"skill-same:01M7147XEBNEAA6H7RBF71W9KY":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M7147XEBNEAA6H7RBF71W9KY","pagerduty-automation",null,"Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fpagerduty-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"automation","pagerduty","pagerduty automation","composio","search tools","2026","via","services","first","tasks","unknown","schedules","MCP","call","incidents","search","manage","for","escalation","community","2026-11-10 10:12:30",false,"---\nname: pagerduty-automation\ndescription: \"Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# PagerDuty Automation via Rube MCP\n\nAutomate PagerDuty incident management and operations through Composio's PagerDuty toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active PagerDuty connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pagerduty`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pagerduty`\n3. If connection is not ACTIVE, follow the returned auth link to complete PagerDuty authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Incidents\n\n**When to use**: User wants to create, update, acknowledge, or resolve incidents\n\n**Tool sequence**:\n1. `PAGERDUTY_FETCH_INCIDENT_LIST` - List incidents with filters [Required]\n2. `PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID` - Get specific incident details [Optional]\n3. `PAGERDUTY_CREATE_INCIDENT_RECORD` - Create a new incident [Optional]\n4. `PAGERDUTY_UPDATE_INCIDENT_BY_ID` - Update incident status or assignment [Optional]\n5. `PAGERDUTY_POST_INCIDENT_NOTE_USING_ID` - Add a note to an incident [Optional]\n6. `PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION` - Snooze an incident for a period [Optional]\n\n**Key parameters**:\n- `statuses[]`: Filter by status ('triggered', 'acknowledged', 'resolved')\n- `service_ids[]`: Filter by service IDs\n- `urgencies[]`: Filter by urgency ('high', 'low')\n- `title`: Incident title (for creation)\n- `service`: Service object with `id` and `type` (for creation)\n- `status`: New status for update operations\n\n**Pitfalls**:\n- Incident creation requires a `service` object with both `id` and `type: 'service_reference'`\n- Status transitions follow: triggered -> acknowledged -> resolved\n- Cannot transition from resolved back to triggered directly\n- `PAGERDUTY_UPDATE_INCIDENT_BY_ID` requires the incident ID as a path parameter\n- Snooze duration is in seconds; the incident re-triggers after the snooze period\n\n### 2. Inspect Incident Alerts and Analytics\n\n**When to use**: User wants to review alerts within an incident or analyze incident metrics\n\n**Tool sequence**:\n1. `PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID` - List alerts for an incident [Required]\n2. `PAGERDUTY_GET_INCIDENT_ALERT_DETAILS` - Get details of a specific alert [Optional]\n3. `PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID` - Get incident analytics\u002Fmetrics [Optional]\n\n**Key parameters**:\n- `incident_id`: The incident ID\n- `alert_id`: Specific alert ID within the incident\n- `statuses[]`: Filter alerts by status\n\n**Pitfalls**:\n- An incident can have multiple alerts; each alert has its own status\n- Alert IDs are scoped to the incident\n- Analytics data includes response times, engagement metrics, and resolution times\n\n### 3. Manage Services\n\n**When to use**: User wants to create, update, or list services\n\n**Tool sequence**:\n1. `PAGERDUTY_RETRIEVE_LIST_OF_SERVICES` - List all services [Required]\n2. `PAGERDUTY_RETRIEVE_SERVICE_BY_ID` - Get service details [Optional]\n3. `PAGERDUTY_CREATE_NEW_SERVICE` - Create a new technical service [Optional]\n4. `PAGERDUTY_UPDATE_SERVICE_BY_ID` - Update service configuration [Optional]\n5. `PAGERDUTY_CREATE_INTEGRATION_FOR_SERVICE` - Add an integration to a service [Optional]\n6. `PAGERDUTY_CREATE_BUSINESS_SERVICE` - Create a business service [Optional]\n7. `PAGERDUTY_UPDATE_BUSINESS_SERVICE_BY_ID` - Update a business service [Optional]\n\n**Key parameters**:\n- `name`: Service name\n- `escalation_policy`: Escalation policy object with `id` and `type`\n- `alert_creation`: Alert creation mode ('create_alerts_and_incidents' or 'create_incidents')\n- `status`: Service status ('active', 'warning', 'critical', 'maintenance', 'disabled')\n\n**Pitfalls**:\n- Creating a service requires an existing escalation policy\n- Business services are different from technical services; they represent business-level groupings\n- Service integrations define how alerts are created (email, API, events)\n- Disabling a service stops all incident creation for that service\n\n### 4. Manage Schedules and On-Call\n\n**When to use**: User wants to view or manage on-call schedules and rotations\n\n**Tool sequence**:\n1. `PAGERDUTY_GET_SCHEDULES` - List all schedules [Required]\n2. `PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID` - Get specific schedule details [Optional]\n3. `PAGERDUTY_CREATE_NEW_SCHEDULE_LAYER` - Create a new schedule [Optional]\n4. `PAGERDUTY_UPDATE_SCHEDULE_BY_ID` - Update an existing schedule [Optional]\n5. `PAGERDUTY_RETRIEVE_ONCALL_LIST` - View who is currently on-call [Optional]\n6. `PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION` - Create temporary overrides [Optional]\n7. `PAGERDUTY_DELETE_SCHEDULE_OVERRIDE_BY_ID` - Remove an override [Optional]\n8. `PAGERDUTY_RETRIEVE_USERS_BY_SCHEDULE_ID` - List users in a schedule [Optional]\n9. `PAGERDUTY_PREVIEW_SCHEDULE_OBJECT` - Preview schedule changes before saving [Optional]\n\n**Key parameters**:\n- `schedule_id`: Schedule identifier\n- `time_zone`: Schedule timezone (e.g., 'America\u002FNew_York')\n- `schedule_layers`: Array of rotation layer configurations\n- `since`\u002F`until`: Date range for on-call queries (ISO 8601)\n- `override`: Override object with user, start, and end times\n\n**Pitfalls**:\n- Schedule layers define rotation order; multiple layers can overlap\n- Overrides are temporary and take precedence over the normal schedule\n- `since` and `until` are required for on-call queries to scope the time range\n- Time zones must be valid IANA timezone strings\n- Preview before saving complex schedule changes to verify correctness\n\n### 5. Manage Escalation Policies\n\n**When to use**: User wants to create or modify escalation policies\n\n**Tool sequence**:\n1. `PAGERDUTY_FETCH_ESCALATION_POLICES_LIST` - List all escalation policies [Required]\n2. `PAGERDUTY_GET_ESCALATION_POLICY_BY_ID` - Get policy details [Optional]\n3. `PAGERDUTY_CREATE_ESCALATION_POLICY` - Create a new policy [Optional]\n4. `PAGERDUTY_UPDATE_ESCALATION_POLICY_BY_ID` - Update an existing policy [Optional]\n5. `PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDS` - View audit trail for a policy [Optional]\n\n**Key parameters**:\n- `name`: Policy name\n- `escalation_rules`: Array of escalation rule objects\n- `num_loops`: Number of times to loop through rules before stopping (0 = no loop)\n- `escalation_delay_in_minutes`: Delay between escalation levels\n\n**Pitfalls**:\n- Each escalation rule requires at least one target (user, schedule, or team)\n- `escalation_delay_in_minutes` defines how long before escalating to the next level\n- Setting `num_loops` to 0 means the policy runs once and stops\n- Deleting a policy fails if services still reference it\n\n### 6. Manage Teams\n\n**When to use**: User wants to create or manage PagerDuty teams\n\n**Tool sequence**:\n1. `PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS` - Create a new team [Required]\n\n**Key parameters**:\n- `name`: Team name\n- `description`: Team description\n\n**Pitfalls**:\n- Team names must be unique within the account\n- Teams are used to scope services, escalation policies, and schedules\n\n## Common Patterns\n\n### ID Resolution\n\n**Service name -> Service ID**:\n```\n1. Call PAGERDUTY_RETRIEVE_LIST_OF_SERVICES\n2. Find service by name in response\n3. Extract id field\n```\n\n**Schedule name -> Schedule ID**:\n```\n1. Call PAGERDUTY_GET_SCHEDULES\n2. Find schedule by name in response\n3. Extract id field\n```\n\n### Incident Lifecycle\n\n```\n1. Incident triggered (via API, integration, or manual creation)\n2. On-call user notified per escalation policy\n3. User acknowledges -> status: 'acknowledged'\n4. User resolves -> status: 'resolved'\n```\n\n### Pagination\n\n- PagerDuty uses offset-based pagination\n- Check response for `more` boolean field\n- Use `offset` and `limit` parameters\n- Continue until `more` is false\n\n## Known Pitfalls\n\n**ID Formats**:\n- All PagerDuty IDs are alphanumeric strings (e.g., 'P1234AB')\n- Service references require `type: 'service_reference'`\n- User references require `type: 'user_reference'`\n\n**Status Transitions**:\n- Incidents: triggered -> acknowledged -> resolved (forward only)\n- Services: active, warning, critical, maintenance, disabled\n\n**Rate Limits**:\n- PagerDuty API enforces rate limits per account\n- Implement exponential backoff on 429 responses\n- Bulk operations should be spaced out\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Pagination uses `offset`\u002F`limit`\u002F`more` pattern\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List incidents | PAGERDUTY_FETCH_INCIDENT_LIST | statuses[], service_ids[] |\n| Get incident | PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID | incident_id |\n| Create incident | PAGERDUTY_CREATE_INCIDENT_RECORD | title, service |\n| Update incident | PAGERDUTY_UPDATE_INCIDENT_BY_ID | incident_id, status |\n| Add incident note | PAGERDUTY_POST_INCIDENT_NOTE_USING_ID | incident_id, content |\n| Snooze incident | PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION | incident_id, duration |\n| Get incident alerts | PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID | incident_id |\n| Incident analytics | PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID | incident_id |\n| List services | PAGERDUTY_RETRIEVE_LIST_OF_SERVICES | (none) |\n| Get service | PAGERDUTY_RETRIEVE_SERVICE_BY_ID | service_id |\n| Create service | PAGERDUTY_CREATE_NEW_SERVICE | name, escalation_policy |\n| Update service | PAGERDUTY_UPDATE_SERVICE_BY_ID | service_id |\n| List schedules | PAGERDUTY_GET_SCHEDULES | (none) |\n| Get schedule | PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID | schedule_id |\n| Get on-call | PAGERDUTY_RETRIEVE_ONCALL_LIST | since, until |\n| Create schedule override | PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION | schedule_id |\n| List escalation policies | PAGERDUTY_FETCH_ESCALATION_POLICES_LIST | (none) |\n| Create escalation policy | PAGERDUTY_CREATE_ESCALATION_POLICY | name, escalation_rules |\n| Create team | PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS | name, description |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# PagerDuty Automation via Rube MCP\n\nAutomate PagerDuty incident management and operations through Composio's PagerDuty toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active PagerDuty connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pagerduty`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pagerduty`\n3. If connection is not ACTIVE, follow the returned auth link to complete PagerDuty authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Incidents\n\n**When to use**: User wants to create, update, acknowledge, or resolve incidents\n\n**Tool sequence**:\n1. `PAGERDUTY_FETCH_INCIDENT_LIST` - List incidents with filters [Required]\n2. `PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID` - Get specific incident details [Optional]\n3. `PAGERDUTY_CREATE_INCIDENT_RECORD` - Create a new incident [Optional]\n4. `PAGERDUTY_UPDATE_INCIDENT_BY_ID` - Update incident status or assignment [Optional]\n5. `PAGERDUTY_POST_INCIDENT_NOTE_USING_ID` - Add a note to an incident [Optional]\n6. `PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION` - Snooze an incident for a period [Optional]\n\n**Key parameters**:\n- `statuses[]`: Filter by status ('triggered', 'acknowledged', 'resolved')\n- `service_ids[]`: Filter by service IDs\n- `urgencies[]`: Filter by urgency ('high', 'low')\n- `title`: Incident title (for creation)\n- `service`: Service object with `id` and `type` (for creation)\n- `status`: New status for update operations\n\n**Pitfalls**:\n- Incident creation requires a `service` object with both `id` and `type: 'service_reference'`\n- Status transitions follow: triggered -> acknowledged -> resolved\n- Cannot transition from resolved back to triggered directly\n- `PAGERDUTY_UPDATE_INCIDENT_BY_ID` requires the incident ID as a path parameter\n- Snooze duration is in seconds; the incident re-triggers after the snooze period\n\n### 2. Inspect Incident Alerts and Analytics\n\n**When to use**: User wants to review alerts within an incident or analyze incident metrics\n\n**Tool sequence**:\n1. `PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID` - List alerts for an incident [Required]\n2. `PAGERDUTY_GET_INCIDENT_ALERT_DETAILS` - Get details of a specific alert [Optional]\n3. `PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID` - Get incident analytics\u002Fmetrics [Optional]\n\n**Key parameters**:\n- `incident_id`: The incident ID\n- `alert_id`: Specific alert ID within the incident\n- `statuses[]`: Filter alerts by status\n\n**Pitfalls**:\n- An incident can have multiple alerts; each alert has its own status\n- Alert IDs are scoped to the incident\n- Analytics data includes response times, engagement metrics, and resolution times\n\n### 3. Manage Services\n\n**When to use**: User wants to create, update, or list services\n\n**Tool sequence**:\n1. `PAGERDUTY_RETRIEVE_LIST_OF_SERVICES` - List all services [Required]\n2. `PAGERDUTY_RETRIEVE_SERVICE_BY_ID` - Get service details [Optional]\n3. `PAGERDUTY_CREATE_NEW_SERVICE` - Create a new technical service [Optional]\n4. `PAGERDUTY_UPDATE_SERVICE_BY_ID` - Update service configuration [Optional]\n5. `PAGERDUTY_CREATE_INTEGRATION_FOR_SERVICE` - Add an integration to a service [Optional]\n6. `PAGERDUTY_CREATE_BUSINESS_SERVICE` - Create a business service [Optional]\n7. `PAGERDUTY_UPDATE_BUSINESS_SERVICE_BY_ID` - Update a business service [Optional]\n\n**Key parameters**:\n- `name`: Service name\n- `escalation_policy`: Escalation policy object with `id` and `type`\n- `alert_creation`: Alert creation mode ('create_alerts_and_incidents' or 'create_incidents')\n- `status`: Service status ('active', 'warning', 'critical', 'maintenance', 'disabled')\n\n**Pitfalls**:\n- Creating a service requires an existing escalation policy\n- Business services are different from technical services; they represent business-level groupings\n- Service integrations define how alerts are created (email, API, events)\n- Disabling a service stops all incident creation for that service\n\n### 4. Manage Schedules and On-Call\n\n**When to use**: User wants to view or manage on-call schedules and rotations\n\n**Tool sequence**:\n1. `PAGERDUTY_GET_SCHEDULES` - List all schedules [Required]\n2. `PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID` - Get specific schedule details [Optional]\n3. `PAGERDUTY_CREATE_NEW_SCHEDULE_LAYER` - Create a new schedule [Optional]\n4. `PAGERDUTY_UPDATE_SCHEDULE_BY_ID` - Update an existing schedule [Optional]\n5. `PAGERDUTY_RETRIEVE_ONCALL_LIST` - View who is currently on-call [Optional]\n6. `PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION` - Create temporary overrides [Optional]\n7. `PAGERDUTY_DELETE_SCHEDULE_OVERRIDE_BY_ID` - Remove an override [Optional]\n8. `PAGERDUTY_RETRIEVE_USERS_BY_SCHEDULE_ID` - List users in a schedule [Optional]\n9. `PAGERDUTY_PREVIEW_SCHEDULE_OBJECT` - Preview schedule changes before saving [Optional]\n\n**Key parameters**:\n- `schedule_id`: Schedule identifier\n- `time_zone`: Schedule timezone (e.g., 'America\u002FNew_York')\n- `schedule_layers`: Array of rotation layer configurations\n- `since`\u002F`until`: Date range for on-call queries (ISO 8601)\n- `override`: Override object with user, start, and end times\n\n**Pitfalls**:\n- Schedule layers define rotation order; multiple layers can overlap\n- Overrides are temporary and take precedence over the normal schedule\n- `since` and `until` are required for on-call queries to scope the time range\n- Time zones must be valid IANA timezone strings\n- Preview before saving complex schedule changes to verify correctness\n\n### 5. Manage Escalation Policies\n\n**When to use**: User wants to create or modify escalation policies\n\n**Tool sequence**:\n1. `PAGERDUTY_FETCH_ESCALATION_POLICES_LIST` - List all escalation policies [Required]\n2. `PAGERDUTY_GET_ESCALATION_POLICY_BY_ID` - Get policy details [Optional]\n3. `PAGERDUTY_CREATE_ESCALATION_POLICY` - Create a new policy [Optional]\n4. `PAGERDUTY_UPDATE_ESCALATION_POLICY_BY_ID` - Update an existing policy [Optional]\n5. `PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDS` - View audit trail for a policy [Optional]\n\n**Key parameters**:\n- `name`: Policy name\n- `escalation_rules`: Array of escalation rule objects\n- `num_loops`: Number of times to loop through rules before stopping (0 = no loop)\n- `escalation_delay_in_minutes`: Delay between escalation levels\n\n**Pitfalls**:\n- Each escalation rule requires at least one target (user, schedule, or team)\n- `escalation_delay_in_minutes` defines how long before escalating to the next level\n- Setting `num_loops` to 0 means the policy runs once and stops\n- Deleting a policy fails if services still reference it\n\n### 6. Manage Teams\n\n**When to use**: User wants to create or manage PagerDuty teams\n\n**Tool sequence**:\n1. `PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS` - Create a new team [Required]\n\n**Key parameters**:\n- `name`: Team name\n- `description`: Team description\n\n**Pitfalls**:\n- Team names must be unique within the account\n- Teams are used to scope services, escalation policies, and schedules\n\n## Common Patterns\n\n### ID Resolution\n\n**Service name -> Service ID**:\n```\n1. Call PAGERDUTY_RETRIEVE_LIST_OF_SERVICES\n2. Find service by name in response\n3. Extract id field\n```\n\n**Schedule name -> Schedule ID**:\n```\n1. Call PAGERDUTY_GET_SCHEDULES\n2. Find schedule by name in response\n3. Extract id field\n```\n\n### Incident Lifecycle\n\n```\n1. Incident triggered (via API, integration, or manual creation)\n2. On-call user notified per escalation policy\n3. User acknowledges -> status: 'acknowledged'\n4. User resolves -> status: 'resolved'\n```\n\n### Pagination\n\n- PagerDuty uses offset-based pagination\n- Check response for `more` boolean field\n- Use `offset` and `limit` parameters\n- Continue until `more` is false\n\n## Known Pitfalls\n\n**ID Formats**:\n- All PagerDuty IDs are alphanumeric strings (e.g., 'P1234AB')\n- Service references require `type: 'service_reference'`\n- User references require `type: 'user_reference'`\n\n**Status Transitions**:\n- Incidents: triggered -> acknowledged -> resolved (forward only)\n- Services: active, warning, critical, maintenance, disabled\n\n**Rate Limits**:\n- PagerDuty API enforces rate limits per account\n- Implement exponential backoff on 429 responses\n- Bulk operations should be spaced out\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Pagination uses `offset`\u002F`limit`\u002F`more` pattern\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List incidents | PAGERDUTY_FETCH_INCIDENT_LIST | statuses[], service_ids[] |\n| Get incident | PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID | incident_id |\n| Create incident | PAGERDUTY_CREATE_INCIDENT_RECORD | title, service |\n| Update incident | PAGERDUTY_UPDATE_INCIDENT_BY_ID | incident_id, status |\n| Add incident note | PAGERDUTY_POST_INCIDENT_NOTE_USING_ID | incident_id, content |\n| Snooze incident | PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION | incident_id, duration |\n| Get incident alerts | PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID | incident_id |\n| Incident analytics | PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID | incident_id |\n| List services | PAGERDUTY_RETRIEVE_LIST_OF_SERVICES | (none) |\n| Get service | PAGERDUTY_RETRIEVE_SERVICE_BY_ID | service_id |\n| Create service | PAGERDUTY_CREATE_NEW_SERVICE | name, escalation_policy |\n| Update service | PAGERDUTY_UPDATE_SERVICE_BY_ID | service_id |\n| List schedules | PAGERDUTY_GET_SCHEDULES | (none) |\n| Get schedule | PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID | schedule_id |\n| Get on-call | PAGERDUTY_RETRIEVE_ONCALL_LIST | since, until |\n| Create schedule override | PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION | schedule_id |\n| List escalation policies | PAGERDUTY_FETCH_ESCALATION_POLICES_LIST | (none) |\n| Create escalation policy | PAGERDUTY_CREATE_ESCALATION_POLICY | name, escalation_rules |\n| Create team | PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS | name, description |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":34,"source":43,"date_added":49,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fpagerduty-automation","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill pagerduty-automation",{"tool":62,"command":63},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill pagerduty-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill pagerduty-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fpagerduty-automation\u002FSKILL.md",true,[],[71,94,120,130,143,160],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":44},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[83,84,39,85,86,87,88,89,90,91,92,93],"wechat search","wechat","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":44},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[101,102,103,104,105,106,39,107,108,109,110,111,112,113,114,115,116,117,118,119],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":44},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[127,128,101,112,113,114,115,105,39,117,129,118,119,111,109,108,107,116,106,104],"trend radar","radar","pulse",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":44},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[137,138,139,140,141,142],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":44},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[145,90,153,154,155,93,112,156,157,158,103,159,116],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":44},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[162,167,168,169,116,170,157,171,172,173,174,175],"status","play","go","latest","github","discover","control","cmd","volume"]