CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-design-review-branch

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

54

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

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

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 content is highly actionable and clearly sequenced with validation checkpoints and error handling. Its only weakness is minor verbosity from the duplicated base-branch snippet and a few over-explained guard clauses.

DimensionReasoningScore

Conciseness

The body is largely lean with direct commands and short sections, though the base-branch bash snippet is duplicated verbatim and the sandbox/explicit-invocation guidance slightly over-explains.

4 / 5

Actionability

It provides fully executable, copy-paste-ready bash commands for both base and no-base cases, plus concrete worked examples covering the common cases.

5 / 5

Workflow Clarity

A clear five-step sequence with an explicit validation checkpoint (git rev-parse --verify, exit 1 on failure), error-handling guidance, and result-presentation rules forms a strong feedback loop.

5 / 5

Progressive Disclosure

With no bundle files present, the single self-contained SKILL.md is well-organized under clear headers with a 'See also' section for sibling skills, which is appropriate for a self-contained skill.

5 / 5

Total

19

/

20

Passed

Description

28%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 functions solely as an invocation guard and never tells the reader what the skill actually does. It needs a concrete action statement (request and present a branch design review) to reach completeness.

Suggestions

Add a concrete 'what' clause, e.g. 'Request a design review of all commits on the current branch and present the results.'

Include natural trigger terms users would say, such as 'design review', 'review my branch', or 'branch review'.

Combine what + when: 'Request and present a design review of all commits on the current branch. Use only when the user explicitly invokes /roborev-design-review-branch.'

DimensionReasoningScore

Specificity

The description ('Use only when the user explicitly invokes /roborev-design-review-branch') names the domain only via the command name and gives zero concrete actions describing what the skill does.

2 / 5

Completeness

It provides a clear 'when' (explicit invocation) but entirely omits the 'what' — it never states that it requests and presents a design review of branch commits.

2 / 5

Trigger Term Quality

It surfaces the literal command '/roborev-design-review-branch' and the word 'review', but offers only one or two generic keywords with no natural synonyms or variations users would say.

2 / 5

Distinctiveness Conflict Risk

The unique command name makes it mostly distinguishable, but the absence of any 'what' context leaves overlap ambiguity with sibling skills like /roborev-design-review and /roborev-review-branch.

3 / 5

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
roborev-dev/roborev
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.