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.

68

Quality

83%

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

88%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.

A well-structured, actionable style guide with concrete templates, good/bad contrasts, a worked example, and an explicit validation checklist. Minor conciseness redundancy and the absence of any progressive disclosure split are the only weak points.

DimensionReasoningScore

Conciseness

Mostly lean and efficient with concrete rules, good/bad contrasts, and no padding or explanation of concepts Claude already knows; minor redundancy between the section 3 OpenInference example and the section 9 worked example keeps it just below the fully lean anchor at 5.

4 / 5

Actionability

Fully actionable for an instruction-only skill: a copy-paste body template, explicit prose rules (no em dashes, named marketing words), concrete commands (pnpm test, pytest), and a complete worked before/after rewrite covering the common case.

5 / 5

Workflow Clarity

Clear drafting sequence (title, body structure, show/cut, prose, tests, QA) culminating in an explicit validation checkpoint (section 8, the reviewer's first-30-seconds test) with a feedback loop ('If any answer is no, edit before you push'), matching the validation-loop anchor at 5.

5 / 5

Progressive Disclosure

Well organized into nine clearly numbered, navigable sections with no external references needed for a self-contained style guide; at ~170 lines it is slightly above the simple-skill threshold, keeping it just below the ideal split/overview anchor at 5.

4 / 5

Total

18

/

20

Passed

Description

78%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 with an explicit 'Use when' clause and good synonym coverage of natural trigger phrases. The main weakness is specificity, which states the single action of writing titles/descriptions without listing several concrete sub-actions.

Suggestions

Add one or two more concrete actions to lift specificity, e.g. 'Write PR titles and descriptions, structure the body as Context/Changes/Tests, and draft QA checklists for user-visible changes.'

Clarify the boundary with commit-message and release-note skills to further reduce distinctiveness overlap, e.g. 'for pull requests specifically, not commit messages.'

DimensionReasoningScore

Specificity

Names the domain and one concrete action ('Write PR titles and descriptions the way a staff engineer would') but does not enumerate several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action anchor at 4.

3 / 5

Completeness

Explicitly answers both what ('Write PR titles and descriptions') and when ('Use when drafting or editing... before running gh pr create, or any time the user asks for a PR description, summary, or release-notes-style writeup'), matching the concrete-trigger anchor at 5.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say — 'pull request title and body', 'gh pr create', 'PR description, summary, or release-notes-style writeup' — with good synonym coverage, falling just short of the fully comprehensive anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The PR-description niche has distinct triggers (gh pr create, release-notes writeup) with minimal conflict risk, but 'release-notes-style writeup' creates minor overlap with commit-message or release-note skills, keeping it just below 5.

4 / 5

Total

16

/

20

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.