CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-review

Use only when the user explicitly invokes /roborev-review

52

Quality

57%

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/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 content is highly actionable with executable commands and a clearly sequenced, validated workflow including error-recovery guidance. Its only weakness is moderate verbosity from a duplicated command block and some meta-commentary that could be trimmed.

DimensionReasoningScore

Conciseness

The body is largely action-oriented and assumes Claude's competence, but the commit-specified command block is duplicated across "Build the command" and "Run the review in the background", and meta-commentary like "These instructions are guidelines, not a rigid script" is mild padding. It is efficient but could be tightened, matching the middle anchor.

2 / 3

Actionability

It provides fully executable commands (the roborev review invocation, git rev-parse validation heredoc, Task tool with subagent_type Bash) and concrete examples with real job ids (1042, 1043). This matches the copy-paste-ready, fully-executable anchor.

3 / 3

Workflow Clarity

Five steps are clearly sequenced with an explicit validation checkpoint in step 1 (ref invalid => stop) and an error-recovery feedback loop in step 4 (report errors, suggest roborev status/init/re-run). This matches the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist, so there is no nested-reference risk; the single file is well-organized into clearly labeled sections (Usage, Instructions, Examples, See also) with a one-level See-also pointer to sibling skills. This matches the well-organized, easy-navigation anchor.

3 / 3

Total

11

/

12

Passed

Description

30%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 functions well as a strict invocation gate but fails to describe what the skill actually does, leaving it incomplete and non-specific on capabilities. Its distinctiveness is strong thanks to the explicit slash-command trigger and disabled model invocation.

Suggestions

Add a clause stating what the skill does, e.g. "Requests a roborev code review for a commit and presents the verdict and findings."

Include natural trigger keywords like "code review" or "review a commit" alongside the slash command to aid discoverability.

Combine into a single sentence covering both what and when, e.g. "Requests a roborev code review for a commit and presents the results. Use only when the user explicitly invokes /roborev-review."

DimensionReasoningScore

Specificity

The description states only "Use only when the user explicitly invokes /roborev-review", which names no concrete actions the skill performs (it never says it requests/presents a code review). It matches the vague/no-actions anchor rather than the domain-and-actions or multi-action levels.

1 / 3

Completeness

It answers "when" (only on explicit invocation) but omits "what" entirely — the skill's purpose of requesting and presenting a commit review is absent from the description. Missing one of what/when maps to the lowest anchor.

1 / 3

Trigger Term Quality

The single trigger term is the literal slash command "/roborev-review", which is exactly what a user would type, but there are no natural-language variations such as "code review" or "review a commit". It is above the no-natural-keywords anchor yet below the good-coverage anchor.

2 / 3

Distinctiveness Conflict Risk

Naming a unique slash command combined with disable-model-invocation gives it a clear niche and makes accidental triggering for the wrong skill very unlikely, matching the clear-niche anchor.

3 / 3

Total

7

/

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.