CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-design-review-branch

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

Quality

74%

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

Quality

Content

92%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-engineered operational instruction: fully executable commands, an explicit input-validation checkpoint with a do-not-proceed guard, error-recovery paths, and clear presentation/next-step branching for both single-agent and panel reviews. Its only weakness is minor redundancy — the conditional-construction bullets and the guidelines/IMPORTANT meta-framing could be tightened. Structure and progressive disclosure are appropriate for a single-purpose skill with no bundle files.

DimensionReasoningScore

Conciseness

The body is efficient — concrete commands, no explanations of concepts Claude already knows — but has minor trimmable redundancy: the bullets after the code block restate the conditional construction already shown ("If `--base` is specified, include it (otherwise auto-detects the base branch)"), and the meta-text "These instructions are guidelines, not a rigid script" plus the duplicated IMPORTANT/guidelines framing add padding. This matches anchor 4 (efficient, minor instances of over-explanation) rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Guidance is fully executable: the exact command `roborev review --from-skill --branch --wait --type design`, a copy-paste-ready base-branch snippet with heredoc ref handling and `git rev-parse --verify --end-of-options` validation, concrete error-recovery commands (`roborev daemon status`, `roborev init`), and worked examples covering both the default and --base cases. Matches anchor 5.

5 / 5

Workflow Clarity

The four-step sequence (validate inputs → build and run → present results → offer next steps) includes an explicit validation checkpoint with a stop condition ("If validation fails, inform the user the ref is invalid. Do not proceed."), error-recovery feedback loops for command failures, and pass/fail branching for presentation and next steps. This is a read-only review operation, so the destructive/batch cap does not apply; matches anchor 5.

5 / 5

Progressive Disclosure

This is a single-task skill with no bundle files (references/, scripts/, assets/ are absent) and no content that warrants external files — command snippets, panel behavior, and examples are all appropriately inline at ~130 lines. Sections are clearly organized (Usage, Instructions, Examples, See also) with well-signaled pointers to sibling skills, satisfying the simple-skill organization standard.

5 / 5

Total

19

/

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 precise about when to trigger (the exact slash command) and carries minimal conflict risk, but it omits any statement of what the skill does, so a reader cannot learn its capabilities from the frontmatter alone. While this brevity is consistent with the skill's disable-model-invocation design, the rubric scores only what is explicitly stated, and the missing capability statement caps specificity and completeness. Adding one clause describing the action (e.g., requesting and presenting a design review of all commits on the current branch) would raise both dimensions without weakening the explicit-invocation constraint.

Suggestions

Add a concrete capability statement before the trigger clause, e.g., "Requests a design review of all commits on the current branch and presents the verdict and findings. Use only when the user explicitly invokes /roborev-design-review-branch" — this would lift both specificity and completeness.

Include the natural key phrase "design review" and "branch" as readable words (not only inside the command slug) so the description still communicates the domain if the slug is rendered without slashes.

Optionally name the concrete outputs (verdict Pass/Fail, findings grouped by severity with file paths and line numbers) to make the 'what' comprehensive rather than minimal.

DimensionReasoningScore

Specificity

The description states only "Use only when the user explicitly invokes /roborev-design-review-branch" — it names the domain (design review of a branch) solely via the command slug and lists zero concrete actions or capabilities. It is not anchor 1 (a precise directive, not abstract language) but lacks the actions needed for anchor 3.

2 / 5

Completeness

The "when" is maximally explicit ("Use only when the user explicitly invokes"), but the "what" — what the skill actually does — is entirely absent. Anchor 2's second clause ("only 'when' is present without 'what'") is the exact structural match; it cannot reach 3 because anchor 3 requires a clear 'what', which is not stated anywhere in the description.

2 / 5

Trigger Term Quality

The only trigger term is the literal command "/roborev-design-review-branch"; "design", "review", and "branch" appear only inside the slug with no natural-language variations or synonyms. This matches anchor 3 (some relevant keywords, missing common variations) rather than anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"Use only when the user explicitly invokes /roborev-design-review-branch" pins triggering to one exact command, a clear niche with a distinct trigger and minimal conflict risk with any other skill, matching anchor 5.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

kenn-io/roborev

Path

internal/skills/grok/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.