CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-design-review-branch

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

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable workflow with explicit validation and error-recovery steps. Its main weakness is the verbatim duplication of the command blocks across steps 2 and 3, which inflates the token budget without adding information.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but the full bash command blocks are duplicated verbatim between step 2 ('Build the command') and step 3 ('Run the review in the background') — a clear tightening opportunity that matches 'could be tightened'.

2 / 3

Actionability

Concrete, executable `roborev review --branch --wait --type design` commands plus a real ref-validation heredoc snippet (`git rev-parse --verify … || exit 1`) make the guidance copy-paste ready.

3 / 3

Workflow Clarity

A clear 5-step sequence with an explicit validation checkpoint (ref verification with 'Do not proceed' on failure) and error-recovery feedback in step 4 (daemon/init/re-run guidance) matches the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

No bundle files are provided; the skill is self-contained and organized into clear, well-signaled sections (Usage, When NOT to invoke, Instructions, Examples, See also) with no nested references, which scores 3 per the simple-skills note.

3 / 3

Total

11

/

12

Passed

Description

47%Weight 40%Scale 1-3

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 as a precise invocation gate but fails to communicate what the skill actually does, omitting any reference to design review. It is distinctive and well-gated but scores low on specificity and trigger coverage.

Suggestions

Add a 'what' clause stating the skill's purpose, e.g. 'Request a design review of all commits on the current branch and present the results. Use only when the user explicitly invokes /roborev-design-review-branch.'

Include natural-language trigger variations (e.g. 'design review', 'review my branch's design') so the description reflects terms users actually say.

Name at least one concrete action (e.g. 'launches a background design review and presents verdict and findings') to lift specificity above the 'no actions' anchor.

DimensionReasoningScore

Specificity

The description ("Use only when the user explicitly invokes /roborev-design-review-branch") names no concrete actions at all — it is purely an invocation gate, matching the 'Vague or no actions' anchor.

1 / 3

Completeness

It explicitly and strongly answers 'when' ("Use only when the user explicitly invokes") but omits 'what' entirely — no mention of design review. The explicit 'when' keeps it above score 1, but the missing 'what' blocks a 3.

2 / 3

Trigger Term Quality

The only natural keyword is the command name itself; common variations a user might say ("design review", "review this branch") are absent, matching 'Some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The highly specific command name combined with explicit-invocation-only gating (disable-model-invocation: true) yields a clear niche with very low conflict risk.

3 / 3

Total

8

/

12

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.