pr-description

Use when opening or updating a GitHub PR - writes a detailed PR description that explains what changed, why it changed, how it was implemented, and how it was tested.

Quality

88%

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

Quality

Content

93%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 skill body is well-structured, executable, and lean, with concrete commands and an externalized template. The only meaningful gap is a pre-apply validation checkpoint before the batch PR-body write.

Suggestions

Add a validation checkpoint before applying the body, e.g. preview the drafted /tmp/pr-body.md and confirm required sections are populated before running `gh pr edit --body-file`.

Note label handling explicitly in the verification step (the description mentions confirming labels but no command sets them).

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding, no explaining concepts Claude already knows; every section (Workflow, Commands, Body Structure, Quality Bar) earns its place.	5 / 5
Actionability	Provides copy-paste-ready, fully executable `gh` and `git` commands covering the common cases, plus a concrete referenced template with section scaffolding.	5 / 5
Workflow Clarity	A clear five-step numbered sequence includes a post-apply verification checkpoint (step 5: 'Re-open the PR view and confirm body/labels'), but lacks a pre-apply validation step for the batch `gh pr edit --body-file` write.	4 / 5
Progressive Disclosure	A concise overview SKILL.md with one clearly-signaled, one-level-deep reference (references/pr-body-template.md, confirmed present) and well-organized sections; content is appropriately split and easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

83%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 concise, third-person, and clearly communicates both purpose and trigger. It enumerates the concrete capabilities the skill provides and uses an explicit 'Use when' clause. Trigger-term variation is the main gap.

Suggestions

Broaden trigger terms with synonyms users would naturally say, e.g. 'Use when opening, refreshing, or updating a pull request (PR) description'.

Consider naming the GitHub PR / pull-request extension explicitly to improve natural-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'explains what changed, why it changed, how it was implemented, and how it was tested' — covering the PR description comprehensively across the four core questions.	5 / 5
Completeness	Both 'what' (writes a detailed PR description explaining the four W-aspects) and 'when' (Use when opening or updating a GitHub PR) are explicitly present, though the trigger is a single clause without multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	'Use when opening or updating a GitHub PR' provides good natural keyword coverage, but lacks synonyms and variations such as 'pull request', 'PR description', or 'refresh PR' that users might say.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — PR description authoring — with distinct triggers ('opening or updating a GitHub PR', 'PR description') and minimal risk of overlapping unrelated skills.	5 / 5
	Total	18 / 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: basicmachines-co/basic-memory
Path: .agents/skills/pr-description/SKILL.md
Commit: 328f898

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.