CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/pagerduty-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, information-dense reference for PagerDuty automation with concrete tool slugs, parameters, and useful pitfalls, but weak on validation feedback loops and file organization. The single-file layout inlines significant API-reference material, and destructive operations lack post-action verification steps.

Suggestions

Add explicit validation checkpoints after destructive or state-changing operations (e.g., "After updating an incident, retrieve it to confirm the new status before proceeding") to lift workflow clarity.

Move the per-workflow tool catalogs and Quick Reference table into a references/ file (e.g. TOOL_REFERENCE.md) and keep SKILL.md as a concise overview with clearly signaled links.

State the "call RUBE_SEARCH_TOOLS first" instruction once in Setup and remove the duplicate mentions in Prerequisites to tighten token usage.

DimensionReasoningScore

Conciseness

The body is largely lean — tool sequences, key parameters, and pitfalls with no explanation of concepts Claude already knows (e.g., it never explains what PagerDuty or MCP is). Minor trim opportunities exist: "Always call RUBE_SEARCH_TOOLS first" is stated three times (Prerequisites, Setup, and the description), and the Quick Reference table re-lists tool slugs already enumerated in each workflow. This fits anchor 4 (efficient with minor instances that could be trimmed) rather than anchor 3, since the padding is repetition of a genuine instruction, not unnecessary explanation.

4 / 5

Actionability

Concrete, executable guidance dominates: exact tool slugs ("PAGERDUTY_CREATE_INCIDENT_RECORD"), specific parameter shapes ("service object with id and type: 'service_reference'", "status transitions: triggered -> acknowledged -> resolved"), and ID-resolution patterns. As an MCP-tool skill the guidance is inherently concrete, though it stops short of example tool-call payloads and the [Required]/[Optional] labels on workflow steps are ambiguous. This lands on anchor 4 (mostly executable, concrete, minor gaps) rather than 5.

4 / 5

Workflow Clarity

Sequences are clearly listed (Setup steps 1-4 include an explicit checkpoint: "Confirm connection status shows ACTIVE"), but the core workflows involve destructive and batch operations ("PAGERDUTY_DELETE_SCHEDULE_OVERRIDE_BY_ID", disabling services, bulk pagination) without validation/verification steps or fix-and-retry loops after each operation — e.g., no step to confirm an incident actually reached the requested status after an update. Per the judging guidelines, missing validation in destructive/batch workflows caps this at 3, matching anchor 3 (sequence present but checkpoints missing or implicit).

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), so all ~250 lines live in SKILL.md itself. Section headers and the task-to-tool table provide reasonable navigation, but the per-workflow tool catalogs, parameter reference, and Quick Reference table are exactly the API-reference bulk that belongs in a separate reference file loaded on demand. This matches anchor 3 (some structure, but content that should be separate is inline) rather than anchor 4, which expects most bulk content split out into clearly signaled files.

3 / 5

Total

14

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, domain-specific description that clearly states what the skill does with good keyword coverage and virtually no conflict risk. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness and limits natural invocation.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions PagerDuty, incidents, on-call rotations, escalation policies, or wants to acknowledge/resolve pages."

Replace generic verbs with concrete operations: "create, acknowledge, and resolve incidents; manage services, schedules, and escalation policies" instead of "Automate PagerDuty tasks".

Consider adding common user phrasings like "alerts" and "who is on call" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Phrases like "manage incidents, services, schedules, escalation policies, and on-call rotations" list several specific capability areas within PagerDuty, but the verbs stay generic ("Automate", "manage") rather than naming concrete operations like create/acknowledge/resolve incidents. This matches anchor 4 (several specific actions, minor coverage gaps) better than anchor 5, which requires concrete named actions.

4 / 5

Completeness

The "what" is clear ("Automate PagerDuty tasks via Rube MCP... manage incidents, services...") but there is no "when to use" clause — "Always search tools first for current schemas" is an operating instruction, not a trigger condition, so the missing explicit trigger guidance caps this at 3 per the judging guidelines. It is not a 2 because the "what" is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Natural user terms are present: "PagerDuty", "incidents", "on-call rotations", "escalation policies", "schedules". A few commonly-said terms are missing ("alerts", "runbooks", "paging"), so it fits anchor 4 (good keyword coverage, a few natural terms missing) rather than the comprehensive synonym coverage of anchor 5, and is clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

"Automate PagerDuty tasks via Rube MCP (Composio)" carves out a clear niche — PagerDuty incident management specifically — and its keywords (PagerDuty, on-call, escalation policies) would not naturally trigger any other skill. This matches anchor 5 (clear niche with distinct triggers, minimal conflict risk) rather than anchor 4, which still anticipates overlap with closely related skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

davepoon/buildwithclaude

Path

plugins/all-skills/skills/pagerduty-automation/SKILL.md

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.