CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-design-review-branch

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

Quality

73%

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

73%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, highly actionable runbook: exact commands, explicit input validation with failure handling, background execution, concrete result-presentation and error-recovery guidance. Its main weaknesses are the verbatim duplication of the command blocks between steps 2 and 3 and a slightly incorrect Task-tool invocation instruction.

Suggestions

Deduplicate the command blocks: state the full commands once in '### 2. Build the command' and have '### 3. Run the review in the background' reference them ('launch the command from step 2 as a background task'), cutting ~16 lines.

Correct the background-launch instruction to match the harness (Bash tool with run_in_background rather than 'Task tool with subagent_type: "Bash"') so the launch step is executable as written.

Trim the bullets under the step-2 command ('If --base is specified, include it...') that restate points already made in step 1 and the surrounding prose.

DimensionReasoningScore

Conciseness

The body is generally lean and assumes competence, but the full bash command blocks are duplicated verbatim in '### 2. Build the command' and '### 3. Run the review in the background' (roughly 16 repeated lines), and the bullets after the step-2 commands restate what the surrounding prose already says. This is more than the 'minor instances' of anchor 4, fitting 'mostly efficient but could be tightened'.

3 / 5

Actionability

The 'roborev review --from-skill --branch --wait --type design' and 'git rev-parse --verify --end-of-options' commands are copy-paste ready, with concrete error remedies ('roborev daemon status', 'roborev init') and worked example dialogues. The one gap is 'Use the Task tool with run_in_background: true and subagent_type: "Bash"', which does not match the harness's actual background-bash mechanism — concrete guidance with a minor executability gap (anchor 4).

4 / 5

Workflow Clarity

A clear five-step sequence (validate inputs, build command, run in background, present results, offer next steps) with an explicit validation checkpoint — 'git rev-parse --verify --end-of-options' plus 'If validation fails... Do not proceed' — and error-recovery guidance for daemon/init failures. This is not a destructive or batch operation, so no cap applies, and the checkpoints and feedback loops match anchor 5.

5 / 5

Progressive Disclosure

A single-file skill with no bundle directories; all content (commands, workflow, panels, examples, see-also) appropriately lives in SKILL.md under clearly headed, navigable sections. Minor organization gaps — the duplicated sections 2/3 and an Examples section that could be trimmed — keep it at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

58%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 a deliberate invocation gate for an explicit-only skill: it is maximally distinct and states its sole valid trigger exactly, but it omits any statement of capability. As a result completeness and specificity are weak even though conflict risk and trigger quality are excellent.

Suggestions

State the capability explicitly, e.g. 'Request a design review for all commits on the current branch and present the results. Use only when the user explicitly invokes /roborev-design-review-branch' — the missing 'what' caps completeness at 2.

Include the concrete actions (validate the base ref, launch the background review, present the verdict and findings grouped by severity) so the description conveys what the skill actually does, not just when it may run.

Confirm the minimal gating description is intentional given disable-model-invocation: true; if so, pairing it with a one-line capability summary costs few tokens and removes the specificity penalty.

DimensionReasoningScore

Specificity

The description states no concrete actions whatsoever; the only concrete content is the literal command token '/roborev-design-review-branch', which incidentally names the domain (design review of a branch). It is precise but action-free, matching 'names the domain but actions are minimal or generic' rather than anchor 1's vague abstract language.

2 / 5

Completeness

It answers 'when' (only on explicit invocation) but never 'what' — the description never states that the skill runs a design review over commits on the current branch. This matches anchor 2 ('only when is present without what', e.g. 'Use when working with documents'); anchor 3 requires a clear 'what', which is absent.

2 / 5

Trigger Term Quality

For a disable-model-invocation skill the trigger space has exactly one element — the literal slash command — and the description states it exactly ('Use only when the user explicitly invokes /roborev-design-review-branch'), with the body explicitly excluding paraphrase triggers. No natural trigger term is missing because none are permitted, so this exceeds anchor 4 ('a few natural terms missing').

5 / 5

Distinctiveness Conflict Risk

The skill can only fire on the exact literal command, making overlap with any other skill essentially impossible — a clear niche with a distinct trigger and minimal conflict risk (anchor 5), not merely 'minor overlap risk' (anchor 4).

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

kenn-io/roborev

Path

internal/skills/claude/roborev-design-review-branch/SKILL.md

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.