CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-review-branch

Use only when the user explicitly invokes /roborev-review-branch

56

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./internal/skills/claude/roborev-review-branch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%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 a tightly written, executable workflow with explicit validation checkpoints and error-recovery guidance, scoring high across actionability and workflow clarity. Minor duplication of the command blocks and the absence of any reference files keep it just below a perfect score on conciseness and progressive disclosure.

Suggestions

De-duplicate the no-base and base command blocks by defining each once and referencing it from both step 2 and step 3.

Consider moving the Panels sub-section into a short reference file to keep the main flow lean, if the skill grows.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, giving executable commands and focused steps, with minor repetition such as the no-base and base command blocks duplicated across steps 2 and 3 that could be tightened.

4 / 5

Actionability

It provides fully executable, copy-paste-ready bash commands for both the no-base and base cases, including a validated base-ref snippet, plus concrete output-parsing guidance ('Enqueued job <id>').

5 / 5

Workflow Clarity

The five-step sequence is explicit with validation checkpoints: validate the ref before proceeding, report errors and suggest remediation, and only present results after the background task completes; error-recovery feedback loops are present.

5 / 5

Progressive Disclosure

Content is well-organized into clear sections (Usage, Instructions, Examples, See also) with no bundle files to offload, but the no-base/base command duplication and the inline Panels sub-section could be slightly better factored.

4 / 5

Total

18

/

20

Passed

Description

37%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 essentially a usage guardrail rather than a capability statement: it states when to invoke but not what the skill does, capping completeness. It is distinctive thanks to the explicit-invocation constraint but under-specifies the concrete actions.

Suggestions

Add a capability clause to the description, e.g. 'Requests a code review of all commits on the current branch and presents the grouped findings', so the 'what' is explicit.

Include natural trigger phrases beyond the slash command, such as 'use when the user asks to review their branch commits'.

Lead with the action rather than the invocation constraint so the description reads as third-person capability first.

DimensionReasoningScore

Specificity

The phrase 'Request a code review for all commits on the current branch and present the results' names a concrete action, but the description field itself ('Use only when the user explicitly invokes /roborev-review-branch') states only a usage constraint with no capability actions at all, fitting the 'names the domain but actions are minimal' anchor.

2 / 5

Completeness

The 'when' is explicit ('Use only when the user explicitly invokes'), but the 'what' is absent from the description field itself; the what lives only in the body, fitting the 'only when present without what' or vague-what anchor.

2 / 5

Trigger Term Quality

'code review' and 'commits on the current branch' are natural terms a user might say, but the description relies on the slash-command name as the primary trigger and omits common synonyms like 'review my changes' or 'check this branch'.

3 / 5

Distinctiveness Conflict Risk

The explicit-invocation-only trigger is a distinct, narrow niche tied to a specific command, with minor overlap risk against other review-related skills like /roborev-review.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
roborev-dev/roborev
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.