CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-name

Review or correct a Remotion pull request title

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pr-name/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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, dense instruction skill: it encodes the repo's PR-title conventions as concrete templates and examples with almost no waste. The only weakness is that the special-handling classification, which can override the default package prefix, is presented after the default rule rather than as an upfront decision step.

Suggestions

Move the special-handling classification up so it is evaluated before defaulting to a package-name prefix (e.g., a short 'First, classify the change' step ahead of 'Choose the prefix').

Turn the implicit workflow into an explicit ordered checklist (inspect diff → classify → pick prefix → craft description) so the path through the sections is unmistakable.

State explicitly what to do when a change matches multiple special categories (e.g., tests inside packages/it-tests) to remove the one remaining ambiguity.

DimensionReasoningScore

Conciseness

The body is lean and prescriptive — every rule and example encodes repo-specific conventions Claude could not infer, with no explanation of concepts Claude already knows. The paragraph contrasting the two examples teaches the naming pattern rather than padding.

5 / 5

Actionability

Fully executable guidance: an exact title template, four reusable title shapes, three complete examples, ordered description guidelines, and a concrete example for every special prefix category. An instruction-only skill with copy-paste-ready outputs covering the common cases.

5 / 5

Workflow Clarity

The sequence is mostly clear ('inspect its current title and diff', 'Use these guidelines in order', prefix then description), but the special-handling categories that override the default package prefix appear after 'Choose the prefix', so the classification decision arrives late in the flow. Not a destructive or batch operation, so the validation cap does not apply.

4 / 5

Progressive Disclosure

A single-purpose skill with well-organized sections (prefix, description, special handling) and no bundle files; nothing warrants external references, so the simple-skill standard for full marks is met.

5 / 5

Total

19

/

20

Passed

Description

57%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 concise, distinctive description that clearly states what the skill does, but it is missing the 'when to use it' half and under-represents the skill's main output (proposing titles). Trigger coverage is adequate but thin on the synonyms users actually say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to name, rename, or review the title of a Remotion pull request.'

Include natural trigger synonyms such as 'PR title', 'PR name', and 'naming' so users' phrasing matches without exact wording.

Broaden the 'what' to cover the primary action the body teaches, e.g. 'Propose, review, or correct a Remotion pull request title following the repo's prefix conventions.'

DimensionReasoningScore

Specificity

'Review or correct a Remotion pull request title' names the domain and two concrete actions, matching anchor 3. It is not 4 because the central activity the body teaches — proposing or naming a title — is absent from the description; not 2 because the actions are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear (review or correct a Remotion PR title) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ('Remotion', 'pull request', 'title') but common natural variations users say — 'PR', 'PR name', 'naming a PR' — are missing, which fits anchor 3 better than anchor 4's 'a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

A clear niche — Remotion pull request titles — with triggers unlikely to collide with other skills; matches the anchor-5 example's profile of a distinct, low-conflict trigger set.

5 / 5

Total

14

/

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
remotion-dev/remotion
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.