CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-design-review

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

58

Quality

66%

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

Quality

Content

88%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 well-structured, executable workflow with clear validation checkpoints and feedback loops; the main weakness is minor duplication of the command snippets across steps 2 and 3.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, but the full command snippet (both no-commit and commit variants) is duplicated verbatim in step 2 and step 3, a minor redundancy that could be trimmed; this fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean anchor 5.

4 / 5

Actionability

Copy-paste-ready executable commands are provided including the heredoc ref-validation snippet ('git rev-parse --verify -- "$commit^{commit}" || exit 1') and the roborev invocation, with examples covering default and commit-specific cases, matching 'fully executable; copy-paste ready code or commands'.

5 / 5

Workflow Clarity

Five steps are clearly sequenced (validate inputs, build command, run in background, present results, offer next steps) with an explicit validation checkpoint ('git rev-parse --verify ... || exit 1') and error-recovery feedback in step 4 (suggesting 'roborev status', 'roborev init', re-run), matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor; no destructive/batch cap applies since reviews are read-only.

5 / 5

Progressive Disclosure

The skill is a single well-organized SKILL.md with clear sections (Usage, Sandbox access, Instructions, Examples, See also) and no bundle files to reference, fitting 'good structure; most content is appropriately placed; minor organization gaps'; not 5 because it exceeds the simple-skill under-50-lines exception and the panel/explanation detail could arguably be factored out.

4 / 5

Total

18

/

20

Passed

Description

43%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 highly distinctive as an explicit-invocation trigger but fails to describe what the skill actually does, leaving the 'what' half of completeness unanswered and limiting specificity.

Suggestions

Add a concrete capability clause, e.g. 'Request a design review for a commit and present the results' before the trigger guidance.

Include natural trigger phrasings such as 'design review' or 'review this commit's design' alongside the slash command to broaden trigger-term coverage.

Merge into a single 'what + when' sentence to lift completeness from 2 toward 4-5.

DimensionReasoningScore

Specificity

The phrase 'Use only when the user explicitly invokes /roborev-design-review' names the trigger/domain via the command but states no concrete actions the skill performs, fitting 'names the domain but actions are minimal or generic' rather than the entirely-vague anchor 1 because it does point at a specific command.

2 / 5

Completeness

Only the 'when' is present ('Use only when the user explicitly invokes...') with no statement of what the skill does, matching 'only when is present without what'; it has an explicit trigger clause so it is not capped, yet the missing 'what' keeps it below 3.

2 / 5

Trigger Term Quality

The literal '/roborev-design-review' is a precise trigger a user would type, but no natural-language synonyms or variations are present, matching 'some relevant keywords but missing common variations or synonyms'; not 4 because coverage is limited to the single command token.

3 / 5

Distinctiveness Conflict Risk

The explicit, unique slash-command trigger creates a clear niche with minimal conflict risk against other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

12

/

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.