pr-description

Update a GitHub PR description with a summary of changes

2.17x

Quality

55%

Does it follow best practices?

Impact

100%

2.17x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/pr-description/SKILL.md

Quality

Discovery

32%

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 is concise and identifies a specific task (updating a GitHub PR description), but it lacks a 'Use when...' clause, misses common trigger term variations like 'pull request', and doesn't enumerate multiple concrete actions. It would benefit from explicit trigger guidance and more detail about what the summary includes.

Suggestions

Add a 'Use when...' clause with trigger terms like 'pull request description', 'PR summary', 'update PR body', 'summarize PR changes'.

Include the full term 'pull request' alongside 'PR' to capture both natural phrasings users might use.

Expand the 'what' portion to list specific actions, e.g., 'Analyzes commit diffs and generates a structured summary for the PR description, including changes made, files affected, and context.'

Dimension	Reasoning	Score
Specificity	Names a specific domain (GitHub PR) and one action (update description with summary of changes), but doesn't list multiple concrete actions or elaborate on what the summary includes.	2 / 3
Completeness	Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, and per the rubric a missing 'Use when' clause caps completeness at 2 — but the 'what' is also thin, so this lands at 1.	1 / 3
Trigger Term Quality	Includes natural keywords like 'GitHub', 'PR', 'description', and 'summary of changes' which users might say, but misses common variations like 'pull request', 'PR body', 'PR summary', or 'update PR'.	2 / 3
Distinctiveness Conflict Risk	Fairly specific to GitHub PR descriptions, which narrows the domain, but could overlap with other GitHub-related skills (e.g., PR creation, PR review, commit message generation) without clearer trigger boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

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, actionable skill with clear workflow steps and concrete examples. Its main weakness is moderate verbosity — the guidelines, checklist, and some format examples could be tightened since they partially overlap with the instructions and examples already provided. The skill effectively teaches Claude a specific task with enough detail to execute correctly.

Suggestions

Consolidate the checklist into the workflow steps rather than having it as a separate section, since it largely duplicates step 2 and the guidelines

Trim the guidelines section — points like 'be concise' and 'use bullet points' are things Claude already knows and the example output already demonstrates

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some unnecessary verbosity. The markdown format examples within the PR description format section are somewhat redundant since Claude knows markdown. The guidelines section restates things that are implicit from the examples. The checklist at the end largely duplicates step 2 of the instructions.	2 / 3
Actionability	The skill provides concrete, executable commands (git log, git diff), specific argument formats, clear examples of invocation, and detailed output templates with exact markdown formatting. The instructions are specific enough to follow without ambiguity.	3 / 3
Workflow Clarity	The 4-step workflow is clearly sequenced: gather info → check existing description → analyze changes → generate/update. Step 2 includes an important validation checkpoint (checking if the description already exists and is accurate before proceeding). The checklist at the end provides additional verification. For this non-destructive operation (updating a PR description), the workflow is appropriately thorough.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections, but it's somewhat long for a single file with no bundle files to offload detail into. The PR description format section with its multiple sub-sections and markdown examples could potentially be split into a reference file, keeping the main skill leaner. However, the organization within the single file is logical and navigable.	2 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: pipecat-ai/pipecat
Commit: ea296ba

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.