pr-description

Update a GitHub PR description with a summary of changes

Quality

65%

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 ./.claude/skills/pr-description/SKILL.md

Quality

Content

82%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.

The content is actionable, concise, and well-structured with concrete commands and templates. The main gap is an explicit validation/feedback loop for the outward-facing PR-description write.

Dimension	Reasoning	Score
Conciseness	The body is efficient: concrete git commands, bullet points, and template snippets without explaining concepts Claude already knows; only minor wording could be trimmed.	4 / 5
Actionability	It gives executable commands (`git log main..HEAD --oneline`, `git diff main..HEAD`), copy-ready PR-description templates, and worked examples covering the common cases.	5 / 5
Workflow Clarity	Steps 1-4 are clearly sequenced with a validation checkpoint (step 2 checks whether an update is needed and a final checklist), but the error-recovery feedback loop is only implicit rather than fully spelled out.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections within a single self-contained file, which is appropriate for this skill's size; no nested or buried references exist.	4 / 5
	Total	17 / 20 Passed

Description

48%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.

The description is clear and distinct but minimal: it states a single action and omits any trigger guidance. Adding a "Use when..." clause and more specific actions would lift specificity and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to update or summarize a pull request description."

List more concrete actions to raise specificity, e.g. "summarizes commits, documents breaking changes, and links fixed issues".

Include natural synonyms users say, such as "summarize my PR" or "update pull request".

Dimension	Reasoning	Score
Specificity	"Update a GitHub PR description with a summary of changes" names the domain (PR descriptions) but offers only a single generic action (update); it lacks multiple concrete, specific actions.	2 / 5
Completeness	It clearly states the "what" but provides no "Use when..." or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Keywords like "GitHub PR description" and "summary of changes" are relevant, but natural user phrases and synonyms (e.g., "summarize my PR", "update pull request") are missing.	3 / 5
Distinctiveness Conflict Risk	The PR-description niche is fairly distinct with minimal overlap against unrelated skills, though it could overlap slightly with general commit/PR tooling.	4 / 5
	Total	12 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: pipecat-ai/pipecat
Path: .claude/skills/pr-description/SKILL.md
Commit: 6659b78

Reviewed: 1 day 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.