CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr

Use when writing a PR body.

Quality

65%

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/pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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-crafted, lean instruction-only skill: a copy-paste PR body template backed by abundant concrete examples and crisp section guidance, with an unambiguous single-step workflow. The main gaps are the absence of worked examples in the Evidence and Merge Danger sections and an inline example catalog that could be split into a reference file.

DimensionReasoningScore

Conciseness

The body is efficient and practices what it preaches ("Skip all preambles and keep prose brief"), assuming Claude's competence throughout. Minor trimmable instances remain, e.g. "You may use one of these, you may use several, it is unlikely you will use all of them" and a long inline catalog of Summary examples, so it is not a clean 5.

4 / 5

Actionability

Gives a copy-paste template with placeholders plus concrete worked examples for four diff shapes ("For a component change", "For a file-layout change") and five visual formats. Not a 5 because the Evidence and Merge Danger sections tell rather than show — no worked example accompanies "Screenshots are S-tier" or the blast-radius definition, leaving minor gaps.

4 / 5

Workflow Clarity

This is a single-purpose skill (write a PR body) whose single action is unambiguous: the template is presented up front and each section's requirements ("Pick the smallest view that makes the key point clear", "Show a before and after") are explicit. The task is non-destructive and non-batch, so no validation checkpoints are required, and the simple-skill exception applies.

5 / 5

Progressive Disclosure

Structure is good — a top-level template followed by clearly headed sections (## Sections, ### Summary/Evidence/Merge Danger) with no nested references and no bundle files to mis-navigate. Not a 5 because ~90 lines of Summary examples are inlined in SKILL.md where a one-level reference file could hold them, and the body points to `CONTEXT.md`, a file not present in the bundle.

4 / 5

Total

17

/

20

Passed

Description

36%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 is a valid trigger clause but only half a description: it says when to use the skill and nothing about what the skill does. The single natural term "PR body" gives it a distinct niche, but the absent capability statement and missing synonyms like "pull request" leave it terse and under-specified.

Suggestions

State what the skill does before the trigger, e.g. "Structures PR bodies with a summary diagram, before/after evidence, and a merge-risk assessment. Use when writing a PR body or pull request description."

Add trigger synonyms and natural variations such as "pull request", "PR description", and "drafting a PR" so users phrasing the need differently still land on this skill.

Mention the skill's distinctive outputs (the Summary/Evidence/Merge Danger template) to distinguish it from adjacent git and code-review skills.

DimensionReasoningScore

Specificity

"Use when writing a PR body." names the domain but states no concrete actions at all — it never says what the skill does (e.g. apply a template, structure sections). This matches anchor 2 ("Names the domain but actions are minimal or generic") rather than 3, which requires 1-2 concrete actions.

2 / 5

Completeness

The description has an explicit 'when' ("Use when writing a PR body") but no 'what' — the skill's actual function (providing a PR body template with Summary/Evidence/Merge Danger sections) is entirely unstated. This is an exact match for anchor 2 ("only 'when' is present without 'what"); anchor 3 requires a clear 'what', which is absent.

2 / 5

Trigger Term Quality

"PR body" is a relevant, naturally-spoken term, but coverage stops there — common variations like "pull request", "PR description", or "draft a PR" are missing. This fits anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The trigger is narrowly scoped to PR bodies, but with no stated 'what', the description could plausibly fire for adjacent skills (PR creation, PR review, commit-message writing). It sits between anchor 3 ("could still overlap with similar skills") and anchor 4 ("mostly distinct"), and the missing capability statement keeps it at 3.

3 / 5

Total

10

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

tonykay/transcriber

Path

.agents/skills/pr/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.