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.

70

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 lean, well-structured instruction-only skill: an exact git command, a numbered workflow, and a concrete output template with no padding. The only gap is the absence of a worked example showing a completed PR description.

Suggestions

Add one short filled-in example PR description after the template so the expected output style is fully concrete.

Optionally note a fallback for branches without a main branch (e.g. use the default base branch for the three-dot diff).

DimensionReasoningScore

Conciseness

Roughly 20 lean lines with no over-explanation of concepts Claude already knows; every instruction adds value. Matches the 'lean and efficient' anchor exactly.

5 / 5

Actionability

The command `git diff main...HEAD` is copy-paste ready and the What/Why/Changes template is concrete. Not 5 because no filled-in example description is provided to cover the common case.

4 / 5

Workflow Clarity

A simple single-purpose skill with a clear, unambiguous two-step sequence (diff, then write per the template). It is a read-only plus writing task, so the destructive/batch validation cap does not apply; the simple-skill exception holds.

5 / 5

Progressive Disclosure

Under 50 lines, no bundle files present, and the body is well-organized into a numbered procedure plus a clearly delimited template format. Per the rubric note, skills under 50 lines with no need for external references can score 5 with just well-organized sections.

5 / 5

Total

19

/

20

Passed

Description

82%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 description: concise, third-person, with an explicit 'Use when' trigger clause covering multiple natural phrasings. The only weakness is that the 'what' side lists a single action rather than enumerating what the skill actually does (format, structure, summarize a diff).

Suggestions

Enumerate 2-3 concrete capabilities in the 'what' half, e.g. 'Writes pull request descriptions from git diffs, following a What/Why/Changes format' to raise specificity.

Add common trigger variations such as 'open a PR' or 'draft a PR' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ('Writes pull request descriptions') but coverage is not comprehensive — no mention of the format, structure, or updating existing descriptions. Not 4 because only a single action is listed rather than several.

3 / 5

Completeness

Explicitly answers both what ('Writes pull request descriptions') and when ('Use when creating a PR, writing a PR, or when the user asks to summarize changes for a pull request') with three concrete trigger phrases, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'creating a PR', 'writing a PR', 'summarize changes for a pull request'. Not 5 because common variations like 'open a PR', 'draft a PR', or 'PR body' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — PR description writing — with distinct PR/pull-request triggers and only minimal theoretical overlap with commit-message skills. Uses third-person voice as required.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 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

14

/

16

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.