Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill pagerduty-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Incident pagination and status transitions
Pagination loop
100%
100%
Pagination termination check
100%
100%
Status transition guard
100%
100%
No reverse transition
100%
100%
Service reference type
100%
100%
Defensive data parsing
70%
70%
Rate limit on 429 only
100%
100%
Exponential backoff pattern
100%
100%
Incident ID in note call
100%
100%
Incident ID path param for update
100%
100%
Status filter passed
100%
100%
Without context: $0.3175 · 1m 16s · 16 turns · 20 in / 5,158 out tokens
With context: $0.5587 · 2m 20s · 21 turns · 58 in / 9,289 out tokens
On-call schedule querying and overrides
since parameter present
100%
100%
until parameter present
100%
100%
ISO 8601 date format
100%
100%
IANA timezone string
50%
100%
Preview before commit
0%
50%
Override structure complete
100%
100%
Pagination loop
100%
100%
Pagination termination check
100%
100%
Defensive response parsing
50%
50%
Rate limit on 429
0%
0%
Bulk ops spacing
0%
0%
Without context: $0.6335 · 2m 28s · 25 turns · 32 in / 10,392 out tokens
With context: $0.9555 · 3m 55s · 24 turns · 389 in / 18,196 out tokens
Service onboarding with escalation policy setup
Escalation policy before service
100%
100%
Escalation rule has target
100%
100%
escalation_delay_in_minutes used
100%
100%
num_loops set to 0
0%
100%
Service reference type
100%
100%
User reference type
100%
100%
Escalation policy ID in service call
100%
100%
Technical not business service
100%
100%
Rate limit backoff on 429
0%
0%
Defensive response parsing
0%
0%
ID from prior response
100%
100%
Without context: $0.3293 · 1m 21s · 18 turns · 25 in / 5,237 out tokens
With context: $0.5387 · 2m 7s · 21 turns · 280 in / 7,900 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.