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

92%

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

85%Weight 40%Scale 1-3

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

A well-structured, actionable skill body with executable commands, a sequenced workflow, and clean one-level-deep reference navigation. The only weakness is mild redundancy between the Goals, description, and Body Structure sections.

Suggestions

Consolidate the Goals section into the Body Structure section: the five questions duplicate the description and the required sections, so removing Goals would tighten the body without losing information.

Add a one-line example of how the PR body file is produced (e.g. a heredoc or Write tool step) so the "Draft a structured PR body" → "gh pr edit --body-file /tmp/pr-body.md" handoff is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the Goals section ("What changed? Why did we make this change now?...") restates both the frontmatter description and the Body Structure required sections, so it could be tightened.	2 / 3
Actionability	The Commands block gives concrete, executable gh/git commands (e.g. `gh pr view --json ...`, `gh pr edit <pr-number> --body-file /tmp/pr-body.md`) plus a specific reference template.	3 / 3
Workflow Clarity	The 5-step Workflow is clearly sequenced and ends with an explicit verification checkpoint ("Re-open the PR view and confirm body/labels").	3 / 3
Progressive Disclosure	SKILL.md is an overview that links one level deep to the real references/pr-body-template.md, splitting the detailed body structure out of the main file.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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: concrete, third-person action verb, explicit 'Use when' trigger, and a clear niche. It answers what and when without padding.

Dimension	Reasoning	Score
Specificity	"writes a detailed PR description that explains what changed, why it changed, how it was implemented, and how it was tested" enumerates multiple concrete output dimensions rather than vague language.	3 / 3
Completeness	It explicitly answers both what ("writes a detailed PR description that explains...") and when ("Use when opening or updating a GitHub PR").	3 / 3
Trigger Term Quality	"opening or updating a GitHub PR" and "PR description" are natural phrases a user would say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The GitHub PR-description niche is specific with distinct triggers and is unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: 60408ad

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