A tight, well-structured body that respects token budget and gives specific, actionable rules with clear guardrails against fabrication. The only meaningful improvement would be showing a brief example of a good title and body rather than only describing them.

Suggestions

Add a short worked example (one example title plus a compact example body) so the title/body rules are demonstrably executable rather than only descriptive, lifting actionability.

Optionally specify how to gather the diff (e.g., compare against the base branch and list commits with git log) so the inspection step is copy-paste executable for any repository layout.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding and no explanation of concepts Claude already knows; every line is a rule or a guardrail ("Inspect the diff against the base branch and the included commits before writing."), matching the leanest anchor.	5 / 5
Actionability	Guidance is concrete and specific ("Do not use Conventional Commit prefixes such as `feat:` or `fix:`", "List only validation that was actually run, including the result"), and as an instruction-only skill code absence is not penalized. It stops short of fully executable coverage because no example title or body template illustrates the common case, which is what the top anchor requires.	4 / 5
Workflow Clarity	The single task is unambiguous with a clear order (inspect diff and commits, then title, then body) and explicit guardrails; no destructive or batch operations are involved so no validation cap applies, and the simple-skill exception for a clear single-purpose workflow holds.	5 / 5
Progressive Disclosure	At roughly 25 lines with well-organized ## Title and ## Body sections and no need for external references, the skill meets the under-50-lines rule for a top progressive-disclosure score.	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 concise, well-formed description that clearly states both what the skill does and when to use it, with low conflict risk. Its main gap is breadth: it names only two actions and omits common trigger synonyms like "PR".

Suggestions

Add one or two more concrete actions to the what clause, e.g., "summarizes the diff and commit history into a pull request title and description", to lift specificity.

Include the abbreviation users naturally say, e.g., "Use when preparing, creating, or editing a pull request (PR), writing a PR description, or filling in a PR template", to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Draft or update a pull request title and description" names the domain plus two concrete actions on two artifacts, matching the anchor for 1-2 concrete actions that are not comprehensive. It does not list several specific actions (e.g., summarizing the diff or commit history), so it falls short of a 4.	3 / 5
Completeness	It explicitly answers both parts: "Draft or update a pull request title and description for the current repository" (what) and "Use when preparing, creating, or editing a pull request" (when), with concrete trigger phrases matching the top anchor.	5 / 5
Trigger Term Quality	Natural phrases like "pull request", "preparing, creating, or editing a pull request" give good keyword coverage, but common user variations such as the "PR" abbreviation or "PR description" are missing, which keeps it below the comprehensive-synonyms anchor of 5.	4 / 5
Distinctiveness Conflict Risk	"Pull request title and description" is a clear niche with distinct, unambiguous triggers, minimally overlapping with related writing skills such as commit-message generation.	5 / 5
	Total	17 / 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: chdb-io/chdb
Path: .agents/skills/pr-description/SKILL.md
Commit: e93104d

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