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.

1.09x

Quality

58%

Does it follow best practices?

Impact

84%

1.09x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/pagerduty-automation/SKILL.md

Quality

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 skill provides comprehensive coverage of PagerDuty operations via Rube MCP with good structural organization (numbered workflows, parameter lists, pitfalls). However, it suffers from verbosity with repeated information across sections, lacks concrete executable examples showing actual tool invocations with sample parameters, and misses validation/verification steps in its workflows. The content would benefit from being split across multiple files with SKILL.md as a lean overview.

Suggestions

Add concrete tool invocation examples with sample parameters (e.g., show an actual RUBE_SEARCH_TOOLS call and a PAGERDUTY_CREATE_INCIDENT_RECORD call with realistic parameter values) to improve actionability.

Add explicit validation steps to workflows, such as 'Verify creation by calling PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID with the returned ID' after create operations.

Deduplicate pitfalls — consolidate ID format rules, status transitions, and rate limit guidance into the 'Known Pitfalls' section only, removing duplicates from individual workflow sections.

Consider splitting detailed workflow sections into separate reference files (e.g., incidents.md, services.md, schedules.md) and keeping SKILL.md as a concise overview with the quick reference table and setup instructions.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably organized but quite verbose for what it conveys. There's significant repetition across workflows (e.g., pitfalls about ID formats and references appear multiple times), and the 'Known Pitfalls' section repeats information already stated in individual workflow sections. The quick reference table is useful but duplicates the tool sequences above. Some trimming would improve token efficiency.	2 / 3
Actionability	The skill provides tool names, parameter lists, and sequencing, which is helpful. However, it lacks executable code examples or concrete tool invocation examples with actual parameter values. The 'Common Patterns' section uses pseudocode-style numbered lists rather than showing actual tool calls with sample payloads. The instruction to 'always call RUBE_SEARCH_TOOLS first' is good but the skill never shows what that call looks like.	2 / 3
Workflow Clarity	Workflows are clearly sequenced with numbered steps and labeled as Required/Optional, which is good. However, there are no explicit validation checkpoints or error recovery steps. For operations like creating incidents or modifying escalation policies, there's no 'verify the result' step or feedback loop for handling failures (e.g., what to do if creation fails, how to verify the incident was actually created).	2 / 3
Progressive Disclosure	The content is a monolithic document with no bundle files to reference. At ~200+ lines, the detailed workflow sections for each PagerDuty entity type could be split into separate reference files, with SKILL.md serving as a concise overview pointing to them. The quick reference table at the end partially serves as an overview, but the body contains too much inline detail for a single file.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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: d065ead

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.