CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-setup-review

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./internal/skills/claude/roborev-setup-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 an unusually actionable, well-sequenced workflow with exact commands, complete examples, explicit validation, and a hard approval gate — the operational core is excellent. Its weaknesses are length and layout: the giant config-mapping table and confidentiality detail are inlined where one-level-deep reference files would keep the overview lean.

Suggestions

Move the long-tail rows of the configuration mapping table (CI comment filtering, default-branch review, draft-PR handling, budget routing) into a references/ file such as CONFIG-MAPPING.md, keeping the dozen most common mappings inline.

Extract the detailed Confidential material routing checklist into its own reference file, leaving a short in-line summary plus the "ask whether that is acceptable" instruction.

Deduplicate the binary_evidence and draft-PR guidance that currently appears in both the mapping table and the "Rules that matter" list.

DimensionReasoningScore

Conciseness

The body is information-dense and never explains concepts Claude already knows (ruling out 1-2), but at ~550 lines it could be tightened: several table rows are dense multi-line paragraph dumps (e.g. the post_commit_quiet_period and comment_min_confidence rows), and content repeats between the mapping table and the "Rules that matter" list (binary_evidence and draft-PR handling each appear twice). Not 4 because the redundancy and length are more than minor over-explanation.

3 / 5

Actionability

Guidance is fully executable: exact commands ("roborev doctor --from-skill --json", "git check-ignore --no-index -v review-rubrics/facts.md"), a complete .roborev.toml example, a complete rubric template, and concrete gotchas like "Write a literal `{{` as `{{"{{"}}`". The legal-brief example covers the common non-code case.

5 / 5

Workflow Clarity

A clear end-to-end sequence (Look first → conversation → playback → configuration → proposal → build and verify → trial review → hand off) with explicit validation checkpoints (config validate, doctor, git check-ignore, git rev-parse --verify, git show for sources), a hard approval gate, and a tune-rerun feedback loop ("Show each rubric change, get approval, commit it, and request a new review").

5 / 5

Progressive Disclosure

No bundle files exist, so everything is inlined in one ~550-line SKILL.md. Section headers are clear (better than anchor 2's minimal structure), but large blocks that clearly belong in reference files are inline: the 30+ row configuration table and the detailed confidentiality routing rules. Not 4 because the split-out opportunity is substantial, not a minor organization gap.

3 / 5

Total

16

/

20

Passed

Description

51%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 deliberately scoped as an explicit-invocation guard: it is highly distinctive and carries the exact trigger term, but it says nothing about what the skill does. For its disable-model-invocation design this is partially intentional, yet a reader gains zero capability information from it.

Suggestions

Add one clause stating what the skill does, e.g. "Designs a review for a repository and writes the roborev configuration and rubrics that run it. Use only when the user explicitly invokes /roborev-setup-review."

If keeping invocation-only gating, at least name the scope of the skill's work (configuration, rubrics, review setup) so the description is not solely a 'when' clause.

Mention the material types it covers (code, legal briefs, contracts, reports) to give the description a minimal 'what' without inviting model-initiated invocation.

DimensionReasoningScore

Specificity

The description ("Use only when the user explicitly invokes /roborev-setup-review") contains no capability verbs or concrete actions at all — it describes only the invocation condition. It is not entirely vague abstract language (ruling out 1), but it names zero actions the skill performs, below anchor 3's "1-2 concrete actions".

2 / 5

Completeness

Only the "when" is present ("Use only when the user explicitly invokes /roborev-setup-review") with no "what" whatsoever — matching anchor 2 ("only 'when' is present without 'what'") exactly. The 'when' is explicit and strong, ruling out 1, but the total absence of any capability description rules out 3 and above.

2 / 5

Trigger Term Quality

It contains the exact literal trigger a user would type ("/roborev-setup-review") plus natural words like "invokes" and "explicitly", which is the complete trigger surface for an explicit-invocation skill. Not 5 because there is no coverage of synonyms or phrasing variations at all.

4 / 5

Distinctiveness Conflict Risk

The unique command name combined with "Use only when the user explicitly invokes" makes triggering for any other skill essentially impossible. This is a clear niche with a distinct, literal trigger and minimal conflict risk.

5 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (555 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

kenn-io/roborev

Path

internal/skills/claude/roborev-setup-review/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.