CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-review

Use only when the user explicitly invokes /roborev-review

51

Quality

56%

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

The body is highly actionable and well-sequenced with strong validation and error-recovery guidance. Its main weakness is redundancy from the duplicated command block and minor boilerplate, which slightly undercuts conciseness.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the commit-specific command block is duplicated verbatim in both the 'Build the command' and 'Run the review in the background' sections, and the 'guidelines, not a rigid script' boilerplate could be trimmed.

3 / 5

Actionability

It provides fully executable, copy-paste-ready bash and heredoc snippets (git rev-parse validation, roborev review --wait) and concrete examples covering both default-HEAD and security-commit cases.

5 / 5

Workflow Clarity

A clear five-step sequence is given with an explicit validation checkpoint (ref verification with exit on failure) and error-recovery guidance in step 4 for daemon/init failures.

5 / 5

Progressive Disclosure

The file is well-organized into clearly headed sections (Usage, Sandbox access, When NOT to invoke, Instructions, Examples, See also) with no nesting; no bundle files exist, so references are appropriately absent, though the single-file structure is dense.

4 / 5

Total

17

/

20

Passed

Description

31%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 functions well as a strict invocation gate but fails to convey the skill's purpose, omitting any statement of what it does. It is distinctive but scores low on capability specificity and completeness.

Suggestions

Add a brief 'what' clause, e.g. 'Requests a code review for a commit and presents the results. Use only when the user explicitly invokes /roborev-review.'

Include natural trigger terms such as 'code review' or 'review this commit' so the skill is recognizable beyond the literal command name.

Name one or two concrete actions (request review, present verdict and findings) to lift specificity above the vague floor.

DimensionReasoningScore

Specificity

The description ("Use only when the user explicitly invokes /roborev-review") states no concrete actions whatsoever — it describes only when to invoke, never what the skill does.

1 / 5

Completeness

Only the 'when' is present without any 'what' — the description never says it requests and presents a code review, matching the anchor where only 'when' is given.

2 / 5

Trigger Term Quality

Only a single trigger keyword (the literal slash command) is present; natural phrases or synonyms a user might say ("review this commit", "code review") are missing.

2 / 5

Distinctiveness Conflict Risk

The trigger is a unique explicit command, giving it a clear niche with minimal risk of firing for the wrong skill.

5 / 5

Total

10

/

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.