pagerduty-automation
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
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively communicates specific PagerDuty automation capabilities and is highly distinctive due to the product-specific focus. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords like 'alerts' or 'who's on call' to improve discoverability.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks about PagerDuty, incident management, on-call schedules, or who is currently on call.'
Include common user variations and synonyms such as 'alerts', 'oncall', 'pager duty', 'incident response', or 'who's on call tonight'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'manage incidents, services, schedules, escalation policies, and on-call rotations' plus the meta-action of searching tools for schemas. | 3 / 3 |
Completeness | Clearly answers 'what' (automate PagerDuty tasks with specific capabilities), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good domain terms like 'PagerDuty', 'incidents', 'on-call rotations', 'escalation policies', but missing common user variations like 'pager', 'alerts', 'who's on call', 'incident response', or 'oncall'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche with 'PagerDuty' as a distinct product name and 'Rube MCP (Composio)' as the specific integration method; unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with clear workflow sequences and comprehensive coverage of PagerDuty operations. Its main weaknesses are the lack of executable code examples (only pseudocode patterns) and some redundancy between the detailed workflows and the quick reference table. The pitfalls sections add genuine value for avoiding common mistakes.
Suggestions
Add executable code examples showing actual tool calls with concrete JSON payloads, especially for common operations like creating an incident or acknowledging one
Consider splitting detailed workflow sections into separate files (e.g., INCIDENTS.md, SCHEDULES.md) and keeping SKILL.md as a concise overview with the Quick Reference table
Remove the Quick Reference table or consolidate it with the workflow sections to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the Quick Reference table duplicates information already covered in the workflows, and some workflow descriptions could be tighter. The pitfalls sections add value but occasionally state obvious constraints. | 2 / 3 |
Actionability | Provides clear tool sequences and parameter lists, but lacks executable code examples. The ID Resolution and Incident Lifecycle patterns use pseudocode-style descriptions rather than actual API call examples with concrete payloads. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps, explicit tool names, and [Required]/[Optional] markers. Each workflow includes pitfalls that serve as validation guidance, and the Incident Lifecycle pattern shows the state machine clearly. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document with no references to external files. The Quick Reference table at the end is helpful, but detailed workflows could be split into separate files for better navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
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.