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

93%

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 exemplary: lean, fully executable, with a clear workflow and a well-signaled one-level-deep reference to a real template file. The only gap is the absence of an error-recovery loop after applying the PR body, which keeps workflow clarity at 4.

Suggestions

Add a brief recovery step after applying the body (e.g., 'If gh pr edit fails, re-run with a fresh /tmp/pr-body.md and confirm labels separately'), which would lift workflow clarity to 5.

Include the fallback for branches with no open PR (gh pr view errors), since the workflow depends on that command succeeding.

Dimension	Reasoning	Score
Conciseness	The body is lean — short sections, copy-paste commands, and no explanation of concepts Claude already knows (no gh tutorializing, no git basics). It matches the level-5 anchor ("Lean and efficient; assumes Claude's competence; every token earns its place"); level 4 would require "minor instances of over-explanation" to trim, and none are present.	5 / 5
Actionability	The Commands section gives executable, copy-paste-ready commands ("gh pr view --json number,title,url,baseRefName,headRefName", "gh pr edit <pr-number> --body-file /tmp/pr-body.md"), a concrete required-sections list, and a real template file. This matches the level-5 anchor ("Fully executable; copy-paste ready code or commands"); the only placeholder, <pr-number>, is filled by step 1's own command.	5 / 5
Workflow Clarity	The five-step workflow is clearly sequenced and includes a verification checkpoint ("Re-open the PR view and confirm body/labels"), fitting the level-4 anchor ("Clear sequence with most checkpoints present"). It does not reach level 5 because there is no error-recovery feedback loop (e.g., what to do if the edit fails or the body renders wrong), and it does not fall to level 3 since a validation step is explicitly present.	4 / 5
Progressive Disclosure	The body is a concise overview that delegates the full template to a single, clearly-signaled, one-level-deep reference ([references/pr-body-template.md], verified to exist and contain the five required sections), and nothing that belongs in a separate file is inlined. This matches the level-5 anchor ("Clear overview with well-signaled one-level-deep references").	5 / 5
	Total	19 / 20 Passed

Description

92%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: it is in third person, states both the capability and an explicit 'Use when' trigger, and enumerates four concrete facets of the output. The only improvement space is broader synonym coverage (e.g., 'pull request', 'PR body').

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete facets of the deliverable — "writes a detailed PR description that explains what changed, why it changed, how it was implemented, and how it was tested" — which comprehensively covers the skill's actions. It matches the level-5 anchor ("multiple specific concrete actions; comprehensive coverage") and exceeds level 4, whose "minor gaps in coverage" would understate the four explicitly enumerated aspects.	5 / 5
Completeness	Both halves are explicit: "Use when opening or updating a GitHub PR" answers when, and "writes a detailed PR description that explains what changed, why it changed, how it was implemented, and how it was tested" answers what. This matches the level-5 anchor (both what and when with concrete trigger phrases); level 4 would require the 'when' to be less explicit, which it is not.	5 / 5
Trigger Term Quality	Natural trigger phrases "opening or updating a GitHub PR" and "PR description" are exactly what a user would say, but common synonyms like "pull request" (spelled out) or "PR body" are absent. This fits the level-4 anchor ("Good keyword coverage; a few natural terms missing") and not level 5, which requires synonyms and extensions.	4 / 5
Distinctiveness Conflict Risk	"Writes a detailed PR description" carves out a clear niche distinct from PR review or merge skills, and the trigger (opening/updating a PR) is narrowly scoped. Minimal conflict risk matches the level-5 anchor; level 4's "minor overlap risk with closely related skills" does not apply since the description never mentions reviewing or merging.	5 / 5
	Total	19 / 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: 194afe1

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