Name: pagerduty
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

pagerduty

PagerDuty integration. Manage Users, Teams, Services, Events. Use when the user wants to interact with PagerDuty data.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/pagerduty/SKILL.md

Quality

Content

71%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 highly actionable body with executable Membrane CLI commands and a well-validated connection workflow. It loses points on conciseness (concept preamble and duplicated action listings) and progressive disclosure (everything inlined with no reference files).

Suggestions

Remove the "PagerDuty Overview" paragraph and bulleted entity/action list since they duplicate the "Popular actions" table, cutting padding Claude does not need.

Move the 20-row "Popular actions" table and the detailed connection-state documentation into a references/ file (e.g. ACTIONS.md) and link to it from SKILL.md to improve progressive disclosure.

Fix the dangling "Skip to Step 2" / "#### 1b" numbering and add an explicit validation/verification step before running destructive actions such as delete-service.

Dimension	Reasoning	Score
Conciseness	The opening "PagerDuty is an incident management platform that helps teams respond to critical issues quickly" explains a concept Claude already knows, and the bulleted "PagerDuty Overview" action list largely duplicates the "Popular actions" table, adding padding that could be tightened.	3 / 5
Actionability	Copy-paste-ready commands are given throughout ("membrane login --tenant --clientName=<agentType>", "membrane connection ensure", "membrane action run <actionId> --connectionId=CONNECTION_ID --json") with concrete flag tables covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit state-based checkpoints and a feedback loop (poll again after CLIENT_ACTION_REQUIRED), but it references a "Step 2" that is never labeled and gives no validation guidance for destructive actions like "Delete Service" or batch incident updates.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in one ~195-line SKILL.md; the large 20-row action table and lengthy connection-state documentation are candidates for a separate reference file but are kept inline, so structure is present but not split.	3 / 5
	Total	15 / 20 Passed

Description

73%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 concise, third-person description that clearly states both capability and trigger condition with a distinct PagerDuty niche. It is slightly held back by the generic "Manage" verb and trigger terms that could enumerate more natural user phrases.

Suggestions

Replace the generic "Manage" with 2-3 distinct concrete verbs (e.g., "Create, update, and list Users, Teams, Services, and Incidents") to raise specificity.

Expand the "Use when" clause with natural trigger phrases users actually say, e.g., "Use when the user wants to manage PagerDuty incidents, on-call schedules, or escalation policies."

Dimension	Reasoning	Score
Specificity	"Manage Users, Teams, Services, Events" names the domain and several concrete entities, but "Manage" is a single generic verb rather than distinct actions, so it stops at 1-2 concrete actions rather than comprehensive coverage.	3 / 5
Completeness	Both "what" ("PagerDuty integration. Manage Users, Teams, Services, Events") and "when" ("Use when the user wants to interact with PagerDuty data") are present and explicit, but the "when" could be more specific about concrete triggers.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with PagerDuty data" supplies the natural term "PagerDuty" in a user-like phrase; coverage is good though a few natural variations ("on-call", "incidents", "alerts") are missing.	4 / 5
Distinctiveness Conflict Risk	"PagerDuty integration" targets a named product niche with distinct proper-noun triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/pagerduty/SKILL.md
Commit: f484c82

Reviewed: 5 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.