CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-review-branch

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

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

Quality

Content

81%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 highly actionable, well-sequenced instruction set with real executable commands, explicit validation and failure paths, and helpful examples. Its main weakness is token efficiency: the base-branch shell snippet appears twice in full and some bullets restate what the command templates already show.

Suggestions

Define the base-branch validation snippet once (step 2) and have step 3 reference it ("run the step-2 snippet in the background") instead of duplicating ~30 lines verbatim.

Trim the bullets under step 2 ("If --base is specified, include it...") that restate placeholder handling already evident from the command templates.

Fold the redundant "If no base branch is specified, run: roborev review ..." repetition in steps 2 and 3 into a single canonical command template.

DimensionReasoningScore

Conciseness

The prose is mostly lean and assumes competence (no concept explanations, targeted sandbox and panel notes), but the ~30-line base-branch shell snippet is duplicated verbatim in steps 2 and 3, and the bullets after the snippet restate placeholder meanings already covered by the command templates. It is not a 2 because the padding is concentrated in the duplication rather than spread across several sections.

3 / 5

Actionability

Fully executable, copy-paste-ready bash snippets and roborev commands with clearly marked placeholders, concrete error-handling paths ("If validation fails, inform the user the ref is invalid and report the git error. Do not proceed."), and worked Examples covering the default and base+type cases.

5 / 5

Workflow Clarity

A clear five-step sequence (validate inputs, build command, run in background, present results, offer next steps) with explicit validation via git rev-parse, a hard failure path ("Do not proceed"), error recovery built into the snippet (fetching an unfetched remote-tracking ref), and error-handling guidance when presenting results. The operation is read-only review, so no destructive/batch validation cap applies.

5 / 5

Progressive Disclosure

No bundle files exist; the single-file body is well organized with clear section headers (Usage, Sandbox access, When NOT to invoke, Instructions, Examples, See also) appropriate for a single-workflow skill. The gap keeping it from 5 is the duplicated base-branch snippet, which should be defined once and referenced, and the See also links point to sibling commands rather than any navigable detail material.

4 / 5

Total

17

/

20

Passed

Description

35%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 precise about its trigger condition (explicit invocation only, consistent with disable-model-invocation) but says nothing about what the skill actually does — requesting a code review of the current branch's commits. It functions adequately as a gate for a manually invoked command, but as a description it fails to communicate capabilities.

Suggestions

State the capability in the description, e.g. "Requests a roborev code review for all commits on the current branch and presents the verdict and findings".

Keep the explicit-invocation restriction but append the 'what': "Use only when the user explicitly invokes /roborev-review-branch to review all commits on the current branch".

Add natural trigger vocabulary such as "branch code review" so the skill's purpose is recognizable even outside the invocation context.

DimensionReasoningScore

Specificity

The description states only "Use only when the user explicitly invokes /roborev-review-branch" — no concrete action or even a domain is named, which is below the anchor-2 example ("Processes PDF files") that at least names a domain and an action.

1 / 5

Completeness

The description has an explicit and precise 'when' ("Use only when the user explicitly invokes /roborev-review-branch") but entirely omits 'what' the skill does, exactly matching the anchor-2 case of only 'when' present without 'what'. It is not a 3 because a clear 'what' is absent, and not a 1 because the 'when' is explicit rather than vague.

2 / 5

Trigger Term Quality

The single trigger term is the exact slash command, which is relevant and specific, but no natural phrases users would say ("review this branch", "code review") or synonyms are included, matching the "some relevant keywords but missing common variations" anchor.

3 / 5

Distinctiveness Conflict Risk

Restricting invocation to the literal command "roborev-review-branch" makes wrong-skill triggering nearly impossible, but the description articulates no functional niche to distinguish it from closely related skills (/roborev-review, /roborev-fix), so it falls short of the anchor-5 "clear niche with distinct triggers".

4 / 5

Total

10

/

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