CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-design-review-branch

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

48

Quality

50%

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

Quality

Content

85%Weight 40%Scale 1-3

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, actionable runbook: concrete commands, a clearly sequenced workflow with validation and error handling, and tidy sectioning. The only minor weakness is a few lines of explanation Claude could infer.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-structured, but includes some explanation Claude could infer (e.g. 'The --wait flag blocks until the review completes' and the --base auto-detect note), so it could be tightened.

2 / 3

Actionability

It provides fully executable, copy-paste-ready commands — 'roborev review --branch --wait --type design', the 'git rev-parse --verify' validation snippet, and 'roborev status'/'roborev init' remediation — with concrete examples.

3 / 3

Workflow Clarity

The four-step sequence (validate → run → present → next steps) includes an explicit validation checkpoint ('If validation fails… Do not proceed') and error-recovery paths for daemon/init failures.

3 / 3

Progressive Disclosure

This single-purpose skill is organized into clear, well-signaled sections (Usage, When NOT to invoke, Instructions, Examples, See also) with no need for external references, and none are present.

3 / 3

Total

11

/

12

Passed

Description

15%Weight 40%Scale 1-3

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 excels at conflict avoidance via its strict explicit-invocation trigger but fails to tell Claude what the skill actually does or offer any natural trigger terms. It reads as a guardrail rather than a capability statement.

Suggestions

Add a what-it-does clause, e.g. 'Request a design review for all commits on the current branch and present the results.' before the invocation guidance.

Include natural trigger phrasing so users can discover it, e.g. 'Use for design reviews of an entire branch's commits.'

Keep the explicit-invocation constraint, but combine it with the capability statement so both 'what' and 'when' are present in one concise sentence.

DimensionReasoningScore

Specificity

The description ("Use only when the user explicitly invokes $roborev-design-review-branch") names no concrete actions at all — it states only the invocation condition, matching the 'vague or no actions' anchor.

1 / 3

Completeness

It explicitly answers 'when' (explicit invocation only) but entirely omits 'what' the skill does, so it is missing one of the two required answers.

1 / 3

Trigger Term Quality

The only term is the command token '$roborev-design-review-branch', which is technical jargon rather than a natural phrase a user would say; it deliberately excludes natural trigger phrasing.

1 / 3

Distinctiveness Conflict Risk

The explicit-invocation-only trigger and the unique skill name make accidental triggering very unlikely, giving it a clear niche unlikely to conflict.

3 / 3

Total

6

/

12

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.