CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-description

Writes pull request descriptions. Use when creating a PR, writing a PR, or when the user asks to summarize changes for a pull request.

65

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/pr-description/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Scale 1-5

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

This is a clean, focused skill that does one thing well. It's concise, provides a concrete command and a clear template format, and doesn't over-explain. The main improvement opportunity would be adding a brief example of a completed PR description to make the output expectations fully concrete.

Suggestions

Add one brief example of a completed PR description to show the expected output quality and level of detail.

DimensionReasoningScore

Conciseness

Every line earns its place. No unnecessary explanations of what PRs are, how git works, or other concepts Claude already knows. The template format is lean and directly usable.

5 / 5

Actionability

Provides a concrete git command and a clear output format template. Minor gap: no example of a completed PR description showing what good output looks like, which would make it fully copy-paste actionable.

4 / 5

Workflow Clarity

Clear two-step sequence (run diff, then write description). This is a simple, non-destructive skill so no validation/feedback loops are needed. Minor gap: doesn't address edge cases like what to do if there's no diff or if the branch is behind main.

4 / 5

Progressive Disclosure

This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized with clear sections and the template format serves as both instruction and structure.

5 / 5

Total

18

/

20

Passed

Description

73%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 has strong completeness with an explicit 'Use when' clause and good trigger terms, making it easy for Claude to know when to select this skill. However, it is weak on specificity—it doesn't describe what goes into a PR description (e.g., summarizing diffs, listing files changed, structuring sections). Adding concrete actions and a few more trigger term synonyms would strengthen it.

Suggestions

Add specific actions describing what the skill does, e.g., 'Analyzes git diffs, summarizes code changes, and generates structured PR descriptions with sections like summary, changes, and testing notes.'

Include additional trigger term synonyms such as 'merge request', 'MR', 'PR summary', 'PR description', or 'describe changes' to improve matching coverage.

DimensionReasoningScore

Specificity

The description names the domain (pull request descriptions) but only describes one generic action: 'writes pull request descriptions.' It doesn't elaborate on what that entails—e.g., summarizing diffs, listing changed files, generating structured sections like 'What changed' or 'Testing notes.'

2 / 5

Completeness

Clearly answers both 'what' (writes pull request descriptions) and 'when' (creating a PR, writing a PR, summarizing changes for a pull request) with explicit trigger phrases using a 'Use when' clause.

5 / 5

Trigger Term Quality

Includes good natural trigger terms: 'PR', 'pull request', 'summarize changes'. Missing some variations like 'merge request', 'PR description', 'PR summary', or 'changelog' that users might naturally say.

4 / 5

Distinctiveness Conflict Risk

Fairly distinct—PR descriptions are a specific niche. Minor overlap risk with skills that generate commit messages or summarize code changes, but the explicit mention of 'pull request' helps differentiate.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

9

/

11

Passed

Repository
koenighotze/wheel-of-meeting
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.