CtrlK
BlogDocsLog inGet started
Tessl Logo

write-pr-description

Write PR titles and descriptions the way a staff engineer would. Use when drafting or editing a pull request title and body, before running `gh pr create`, or any time the user asks for a PR description, summary, or release-notes-style writeup of a change. Apply this skill from the start, not as a cleanup pass after a generic first draft.

79

Quality

100%

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

100%

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

A high-quality, self-contained skill body: concrete templates and before/after examples make it immediately actionable, the numbered workflow ends in a real validation checkpoint, and the organization is clean with no padding. It respects Claude's competence throughout.

DimensionReasoningScore

Conciseness

Lean, example-driven guidance that assumes Claude's competence; it avoids explaining concepts Claude already knows and every example (good/bad titles, before/after shapes, worked rewrite) earns its place.

3 / 3

Actionability

Provides a copy-paste body template, concrete before/after data shapes, explicit prose rules (e.g. "No em dashes"), and a full worked example showing a bad draft rewritten — fully executable guidance.

3 / 3

Workflow Clarity

Sections are numbered and sequenced (title → body → show-don't-restate → cut padding → prose → tests → QA → review), culminating in the "Reviewer's first-30-seconds test" as an explicit validation checkpoint with a clear "if no, edit before you push" feedback loop.

3 / 3

Progressive Disclosure

A single self-contained writing-style skill with no need for external references, organized into well-signaled numbered sections; navigation is easy and nothing is nested or split unnecessarily.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: it states concrete actions, gives an explicit "Use when" trigger covering both proactive and on-demand use cases, and stays concise without over-claiming. It is clearly distinct from other skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Write PR titles and descriptions", "drafting or editing a pull request title and body", and a "release-notes-style writeup" — rather than vague capabilities.

3 / 3

Completeness

Explicitly states both what it does ("Write PR titles and descriptions...") and when to use it via an explicit "Use when..." clause covering drafting, pre-`gh pr create`, and on-demand requests.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would actually say: "pull request", "PR description", "gh pr create", "release-notes", and "summary".

3 / 3

Distinctiveness Conflict Risk

Occupies a clear PR-description niche with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
Agenta-AI/agenta
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.