CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

writing-pr-body-title-description

Use when writing or editing a pull request title or body.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/writing-pr-body-title-description/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an efficient, highly actionable rulebook for PR title/body writing with concrete specifics (HTML img embedding with explicit widths, dark-mode screenshot defaults, before/after tables). Its main weakness is an unresolvable pointer to 'shared screenshot guidance' that does not exist in the bundle, and a flat structure with no section organization.

DimensionReasoningScore

Conciseness

The body is a lean list of distinct rules with zero padding and no explanation of concepts Claude already knows (e.g., 'Keep PR titles and bodies concise; do not write essays.'). Every token earns its place.

5 / 5

Actionability

Mostly concrete, executable guidance such as 'always embed screenshots using explicit HTML <img> tags with an explicit width (for example, width="640")' and 'Default screenshots to dark mode'. The instruction to 'follow the shared screenshot guidance' cannot be executed from this bundle, since no such reference file exists.

4 / 5

Workflow Clarity

As a simple single-purpose skill the directives are unambiguous (e.g., 'never use Markdown image syntax', 'For benchmarks, always include a before/after table'), with clear conditional branches for visual changes, benchmarks, and impressive changes. Minor gap: the 'shared screenshot guidance' for 'published-body, rendered-image, and anonymous GET verification' is referenced but not resolvable, leaving that step underspecified.

4 / 5

Progressive Disclosure

All 13 lines of content are appropriately inlined for a skill this size with no bloat that belongs in separate files. However, the body is a flat run of prose with no section headers, and it points to 'the shared screenshot guidance' which is not present in the bundle (no references/ directory), leaving that reference unresolvable.

4 / 5

Total

17

/

20

Passed

Description

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

The description has a clear, explicit trigger ('Use when writing or editing a pull request title or body') and a distinct niche, but it omits any statement of what the skill actually does and lacks common trigger synonyms like 'PR'. This caps both completeness and specificity at the low end.

Suggestions

Add a 'what' clause enumerating concrete capabilities, e.g., 'Write concise PR titles and bodies using bullet points, Mermaid diagrams, and before/after screenshot tables embedded as HTML img tags.'

Include natural trigger variations users actually say, such as 'PR', 'PR description', or 'pull request summary', to improve trigger-term coverage.

Mention a distinguishing capability (e.g., screenshot embedding rules or benchmark tables) in the description to further separate it from generic writing and commit-message skills.

DimensionReasoningScore

Specificity

The description names the domain ('pull request title or body') but the only actions are the generic pair 'writing or editing', matching 'Names the domain but actions are minimal or generic'. It is not a 3 because no concrete capability of the skill (concise bullet-point bodies, HTML img screenshot embedding, before/after tables) is stated.

2 / 5

Completeness

An explicit 'when' clause is present ('Use when writing or editing a pull request title or body') but the 'what' is entirely absent — the description never states what the skill does. This matches the anchor 'only when is present without what'.

2 / 5

Trigger Term Quality

'pull request', 'title', 'body', 'writing', and 'editing' are phrases users would naturally say, but common variations like 'PR', 'PR description', or 'pull request summary' are missing, matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The PR title/body niche is mostly distinct with only minor overlap risk against generic writing or commit-message skills, matching 'Mostly distinct; minor overlap risk with closely related skills'. It is not a 5 because the bare 'writing or editing' phrasing could also plausibly trigger broader PR-creation or documentation skills.

4 / 5

Total

11

/

20

Passed

Validation

100%

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

langchain-ai/open-swe

Path

.agents/skills/writing-pr-body-title-description/SKILL.md

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.