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.
69
58%
Does it follow best practices?
Impact
84%
1.09xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/pagerduty-automation/SKILL.mdQuality
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 does a good job of specifying the concrete PagerDuty capabilities and is highly distinctive due to the specific product domain. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from more natural user-facing trigger terms beyond the technical entity names.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about PagerDuty incidents, on-call schedules, escalation policies, or needs to manage alerting and incident response workflows.'
Include more natural trigger terms users might say, such as 'who is on call', 'incident response', 'pager alerts', 'duty rotation', or 'acknowledge/resolve incident'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: manage incidents, services, schedules, escalation policies, and on-call rotations. Also specifies the mechanism (Rube MCP via Composio) and includes a behavioral instruction about searching tools first. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate PagerDuty tasks including incidents, services, schedules, etc.), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the domain terms rather than explicitly stated. | 2 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'PagerDuty', 'incidents', 'services', 'schedules', 'escalation policies', 'on-call rotations', but lacks common user variations like 'paging', 'alerts', 'who is on call', 'incident response', or 'duty schedule'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests. | 2 / 3 |
Distinctiveness Conflict Risk | PagerDuty is a very specific product/service, and the description clearly scopes to PagerDuty automation via a specific toolchain (Rube MCP/Composio). This is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference skill for PagerDuty automation that covers the major workflows comprehensively with clear tool sequences and parameter documentation. Its main weaknesses are the lack of concrete executable examples (actual tool call payloads), missing validation/verification steps in workflows, and some redundancy between sections. The content would benefit from being more concise and including at least one fully worked example with real parameter values.
Suggestions
Add at least one fully concrete tool call example per major workflow showing actual parameter values (e.g., a complete PAGERDUTY_CREATE_INCIDENT_RECORD call with realistic payload), rather than just listing parameter names.
Add explicit validation steps to core workflows, e.g., after creating an incident, verify it exists by fetching it; after updating a schedule, preview or retrieve it to confirm changes.
Reduce redundancy by consolidating pitfalls into the Known Pitfalls section and removing duplicates from individual workflow sections, or vice versa—pick one location for each pitfall.
Consider splitting the detailed per-workflow tool sequences and parameters into a separate reference file, keeping SKILL.md as a concise overview with the quick reference table and setup instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy—pitfalls are repeated across sections (e.g., service_reference type mentioned in both Manage Incidents and Known Pitfalls), and the quick reference table largely duplicates information already covered in the workflow sections. The ID resolution and incident lifecycle patterns are somewhat obvious for Claude. However, most content is domain-specific and not general knowledge Claude would already have. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and sequences, which is good. However, it lacks executable code examples—the ID resolution and incident lifecycle sections use pseudocode-style numbered lists rather than actual tool call examples with concrete parameter values. No copy-paste-ready tool invocations with example payloads are provided. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and labeled as Required/Optional, which is helpful. However, there are no explicit validation checkpoints or error recovery feedback loops. For operations like creating incidents or modifying schedules, there's no 'verify the result' step. The setup section has a good validation flow (check connection is ACTIVE before proceeding), but core workflows lack similar verification steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table. However, at ~200+ lines, some sections (like the full tool listings for each workflow) could be split into separate reference files. There are no bundle files to offload detailed content to, and the single external link is to Composio docs rather than local reference files. The content is somewhat monolithic for its length. | 2 / 3 |
Total | 8 / 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- 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.