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.

73

Quality

91%

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.

An opinionated, actionable writing guide that assumes competence and sequences the work with an explicit final validation checklist. The only soft spot is mild redundancy where the OpenInference example and Tests/structure guidance recur across sections.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no primers on what a PR or GitHub is), but the OpenInference example recurs in both section 3 and the section 9 worked example, and the Tests/structure guidance overlaps across sections 0, 2, and 6 — minor trimming available.

4 / 5

Actionability

Highly concrete, executable guidance: exact title prefix format with issue-id suffix, a ~70-char limit, a body template with named headings, an explicit before/after shape, a banned marketing-word list, and an absolute 'no em dashes' rule, all reinforced with good/bad examples.

5 / 5

Workflow Clarity

Clear numbered sequence (title → body → show-don't-restate → cut padding → prose → tests → QA) culminating in section 8's first-30-seconds self-audit checklist with an explicit 'if any answer is no, edit before you push' validation/feedback loop.

5 / 5

Progressive Disclosure

Well-organized into clearly numbered, navigable sections with no external bundle files referenced; appropriately kept as a single cohesive guide, though at ~190 lines it exceeds the under-50-line simple-skill case that would score 5 on sections alone.

4 / 5

Total

18

/

20

Passed

Description

95%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, concrete description with explicit 'what' and 'when' clauses and natural trigger phrasing. The only minor gap is that the capability list is framed as a single staff-engineer persona rather than an enumerated action set, keeping specificity just below full marks.

DimensionReasoningScore

Specificity

Names the domain (PR titles and descriptions) and several concrete actions (drafting/editing a title and body, running `gh pr create`, release-notes-style writeups), but the 'what' leans on one staff-engineer framing rather than enumerating a comprehensive action list.

4 / 5

Completeness

Explicitly answers both 'what' (write PR titles and descriptions) and 'when' (Use when drafting/editing, before `gh pr create`, any time the user asks for a PR description/summary/release-notes), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrasing users would actually say ('asks for a PR description, summary, or release-notes-style writeup', 'before running `gh pr create`'), with synonyms covered.

5 / 5

Distinctiveness Conflict Risk

Clear niche (PR description authoring) with distinct triggers tied to `gh pr create` and release-notes writeups; minimal conflict risk with unrelated skills.

5 / 5

Total

19

/

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.