[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SY3DJR6Q37F917GKP07AT":3,"skill-same:01M71SY3DJR6Q37F917GKP07AT":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71SY3DJR6Q37F917GKP07AT","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.","javiertarazon\u002Fide-agente-free-jt7-","javiertarazon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153141207?v=4","01M71R52TB3S9HXKH6WSNT8A7V","01M71R52VG5KS2DKDDH4GDQ30A",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fpagerduty-automation\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"automation","pagerduty","pagerduty automation","composio","search tools","via","services","first","tasks","unknown","schedules","MCP","call","incidents","schemas","search","manage","for","escalation","community","2026-11-10 13:02:02",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":32,"source":42,"requires":48,"description":7},{"mcp":49},[50],"rube","release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fpagerduty-automation","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-","https:\u002F\u002Fgithub.com\u002Fjaviertarazon","2026-07-12 07:10:45",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill pagerduty-automation",{"tool":63,"command":64},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill pagerduty-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill pagerduty-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fpagerduty-automation\u002FSKILL.md",true,[],[72,100,116,134,149,171],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":81,"publishedAt":43},"01M71TQ7Q6Z10VWF3C2H5X1KW9","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[82,83,84,42,85,86,87,88,89,32,90,91,92,93,94,95,96,97,98,99],"zustand","store","zustand store ts","middleware","implementing","use","react state management","when","react","with","state","create","state management","typescript","action","management","separation","global",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":43},"01M71TQ5EAR40G6W0MV5ZDVEZT","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[106],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[108,109,23,42,110,40,38,37,34,32,30,28,111,27,112,113,26,114,97,115],"zoom automation","zoom","creation","meeting","tracking","webinars","recordings","Tools",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":43},"01M71TQ29B1EYBCEAP1ZBGXQ1A","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[122],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[124,125,23,126,127,128,42,129,130,40,39,38,37,131,34,32,132,31,133,93],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","records","convert","contacts",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":43},"01M71TPZPMN60DH0XV58KVHY23","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[140],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[142,23,143,42,40,38,37,34,144,32,31,145,146,30,28,147,27,26,115,148],"zendesk automation","zendesk","organizations","replies","users","tickets","automate",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":43},"01M71TPXDWKHKG4N6TVEPXWD0N","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[156,157,158,159,160,161,162,163,164,23,165,32,166,167,168,169,170,148],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":180,"publishedAt":43},"01M71TPT5T10WXNKW9G7ZXZ27W","youtube-summarizer","Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fyoutube-summarizer\u002FSKILL.md",[177],{"categoryNo":178,"categoryName":179,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[181,182,183,184,42,185,186,187,188,189,190,191,166,192,193,194,195,196,197,198],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]