[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSNY222AZHTSRH4JTG91AT":3,"skill-same:01M6FSNY222AZHTSRH4JTG91AT":72},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6FSNY222AZHTSRH4JTG91AT","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.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\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],"automation","pagerduty","pagerduty automation","incidents","MCP","via","composio","call","community","manage","automate","first","Tools","escalation","services","search","tasks","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.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\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":46,"source":32,"requires":47,"description":7},"unknown",{"mcp":48},[49],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fpagerduty-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add reikiplanet\u002Fdaoskills --skill pagerduty-automation",{"tool":64,"command":65},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill pagerduty-automation",{"tool":67,"command":68},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill pagerduty-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fpagerduty-automation\u002FSKILL.md",true,[],[73,99,111,126,146,169],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":41},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[80,81,82,83,84,85,32,86,87,88,89,90,91,92,93,94,95,96,97,98],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":41},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[106,107,97,108,109,32,87,88,89,83,110,84],"ar","vr ar","interaction","requirements","performance",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":41},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[113,118,119,120,121,122,32,123,89,124,125,83],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":41},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[133,134,135,136,137,32,138,139,140,141,123,142,143,144,145],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":41},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[153,154,155,156,157,158,159,160,32,89,83,161,84,162,163,164,165,166,167,168],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":41},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[176,177,178,179,180,181,182,183,166,123,184,185,186,32,187,188,189,163,190,191],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]