CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-design-review

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

Quality

69%

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

Quality

Content

85%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 strong, executable runbook: fully concrete commands, explicit input validation, background execution guidance, error recovery, and clear result-presentation rules. Its main weakness is redundancy — the command construction is repeated verbatim across sections 2 and 3 and then again narratively in the Examples — which costs tokens without adding guidance.

DimensionReasoningScore

Conciseness

The body is mostly lean instructional content, but the full heredoc plus git rev-parse validation block is duplicated verbatim in sections 2 and 3 (~12 repeated lines), and the Examples section restates the entire workflow a third time — more than the 'minor instances' of the anchor above.

3 / 5

Actionability

Commands are copy-paste ready and complete: `roborev review --from-skill --wait --type design`, the executable commit-validation snippet with `git rev-parse --verify --end-of-options "$commit^{commit}" || exit 1`, explicit panel flag semantics, and worked examples with exact agent responses covering the common cases.

5 / 5

Workflow Clarity

Five clearly sequenced steps with an explicit validation checkpoint ("If validation fails, inform the user the ref is invalid. Do not proceed.") and error-recovery feedback in step 4 (suggest `roborev daemon status`, `roborev init`, or re-running). The operation is a read-only review, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The skill is a single self-contained file with no references/, scripts/, or assets/ directories, and every section is directly needed to execute the workflow, so nothing belongs in a separate file. Sections are well-organized with clear headers and easy navigation, satisfying the no-external-references case.

5 / 5

Total

18

/

20

Passed

Description

38%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 works as a pure invocation gate (consistent with disable-model-invocation: true): it answers 'when' unambiguously and is highly distinctive, but it communicates zero capabilities. A user or model reading only the description cannot tell what the skill actually does.

Suggestions

State the core capability explicitly, e.g. "Requests a design review for a commit via the local roborev daemon and presents the verdict and findings grouped by severity to the user."

Combine the 'what' with the existing 'when' clause so both are in one description: "Requests a design review for a commit and presents the results. Use only when the user explicitly invokes /roborev-design-review."

Include natural trigger phrasing such as "design review of a commit" so the description remains informative in skill listings even though invocation is restricted to the explicit command.

DimensionReasoningScore

Specificity

The description ("Use only when the user explicitly invokes /roborev-design-review") states no capability or action whatsoever — not even a generic one like anchor 2's "Processes PDF files" — so it entirely fails to describe concrete actions.

1 / 5

Completeness

The 'when' is fully explicit ("Use only when the user explicitly invokes..."), but the 'what' is entirely absent — the description never says the skill requests a design review for a commit and presents the results, exactly matching the anchor for only 'when' present without 'what'.

2 / 5

Trigger Term Quality

The literal command "/roborev-design-review" is the one relevant trigger and exactly matches how the skill is invoked, but natural variations users might say ("design review", "review this commit's design") are missing, matching the anchor for some relevant keywords without synonyms.

3 / 5

Distinctiveness Conflict Risk

Gating on literal invocation of a uniquely named slash command gives a clear niche with a distinct trigger and minimal conflict risk — no other skill could be triggered by this description.

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

kenn-io/roborev

Path

internal/skills/claude/roborev-design-review/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.