CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-design-review

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

Quality

71%

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/droid/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 an executable, well-sequenced runbook: exact commands for both invocation forms, up-front ref validation with failure handling, explicit error-recovery paths, and conditional presentation and next steps keyed to the verdict. It stays lean and assumes competence, with only minor tightening or splitting opportunities (Panels detail, duplicated invocation rules).

DimensionReasoningScore

Conciseness

The body stays operational ("The `--wait` flag blocks until the review completes", "These instructions are guidelines, not a rigid script") and teaches nothing Claude already knows; the only trimmable redundancy is that the invocation gate is restated across "Explicit invocation only" and "When NOT to invoke this skill", so it matches "Efficient; minor instances of over-explanation that could be trimmed" rather than the fully lean anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover both cases — `roborev review --from-skill --wait --type design` and the heredoc plus `git rev-parse --verify --end-of-options "$commit^{commit}"` validation snippet — with concrete error remedies (`roborev daemon status`, `roborev init`) and worked examples including job IDs (`/roborev-fix 1042`), matching anchor 5.

5 / 5

Workflow Clarity

Four clearly sequenced steps with explicit validation ("git rev-parse --verify ... || exit 1", "If validation fails, inform the user the ref is invalid. Do not proceed."), feedback loops for error recovery (sandbox escalation retry, daemon/repo failure remedies), and conditional next steps keyed to the verdict (offer `/roborev-fix` only on Fail) — matching anchor 5's "explicit validation steps; feedback loops for error recovery"; the operation is a review, not destructive/batch, so no cap applies.

5 / 5

Progressive Disclosure

Sections are well organized (Usage, Sandbox access, When NOT to invoke, numbered Instructions, Examples, See also) with no bundle files present and nothing that clearly belongs in a separate file, but the ~10-line Panels subsection and the sandbox troubleshooting detail are niche enough to live in a reference file, matching "Good structure; most content is appropriately placed ... minor organization gaps".

4 / 5

Total

18

/

20

Passed

Description

40%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 maximally conservative invocation gate with near-zero conflict risk, but it says nothing about what the skill actually does. A reader of the description alone cannot tell it runs a commit design review and presents verdicts and findings, which caps completeness and specificity at the low anchors.

Suggestions

State the 'what' alongside the 'when', e.g. "Runs a design review of a commit via roborev and presents the verdict and severity-grouped findings. Use only when the user explicitly invokes /roborev-design-review."

Include natural domain phrasing (design review, review a commit's design, review findings) so the skill's capability is discoverable even though invocation is restricted.

Distinguish the skill from siblings — note it is the design-review entry point, unlike /roborev-review (generic types) or /roborev-fix (remediation).

DimensionReasoningScore

Specificity

"Use only when the user explicitly invokes /roborev-design-review" names the design-review domain only implicitly via the command name and lists zero concrete actions or capabilities, matching "Names the domain but actions are minimal or generic"; it sits above anchor 1 because it is not pure abstract language, but no capability is ever described.

2 / 5

Completeness

A clear 'when' is present ("Use only when the user explicitly invokes /roborev-design-review") but the 'what' — running a design review of a commit and presenting the verdict and findings — is entirely absent, exactly matching anchor 2's "only 'when' is present without 'what'"; it cannot score 3 because the 'what' is not weakly implied anywhere, let alone clear.

2 / 5

Trigger Term Quality

The description contains the literal command users would type ("/roborev-design-review", "explicitly invokes") with the embedded terms "design" and "review", but offers no natural variations such as "review this commit's design" or "design feedback", matching "Some relevant keywords but missing common variations or synonyms".

3 / 5

Distinctiveness Conflict Risk

The invoke-only gate ("Use only when the user explicitly invokes") makes false triggers very unlikely and the exact command name is distinct, but the description does not differentiate it from the near-equivalent sibling `/roborev-review --type design`, matching "Mostly distinct; minor overlap risk with closely related skills" rather than anchor 5's fully distinct niche.

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