CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-lookahead-review

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

Quality

67%

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

Quality

Content

88%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 strong, execution-ready instruction set: concrete commands with validation and error-recovery paths, clearly sequenced steps, and tight prose with almost no padding. Its only structural limitation is that everything lives in one file, which is acceptable at this size but leaves slight room for better organization.

DimensionReasoningScore

Conciseness

The body is lean: the opening paragraph defines the domain-specific term ("look-ahead review... also called peekahead, future leakage, or temporal leakage") without explaining concepts Claude already knows, and commands are given without tutorial padding. Minor trimmable meta-commentary ("These instructions are guidelines, not a rigid script...") keeps it just below the every-token-earns-its-place bar of 5.

4 / 5

Actionability

Both code paths are fully executable and copy-paste ready: `roborev review --from-skill --wait --type lookahead` and the heredoc + `git rev-parse --verify --end-of-options` snippet, plus concrete error triage (`roborev daemon status`, `roborev init`) and two worked examples (default HEAD review and specific commit) covering the common cases. Not 4 because there are no meaningful gaps in the guidance.

5 / 5

Workflow Clarity

A clear four-step sequence (validate inputs → build and run → present results → offer next steps) with explicit validation checkpoints ("If validation fails, inform the user the ref is invalid. Do not proceed.") and feedback loops for error recovery (sandbox escalation retry, daemon diagnostics, panel vs. single-agent handling). Not 4 because validation and recovery are explicit at every branch point.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers (Usage, Sandbox access, When NOT to invoke, Instructions, Panels, Examples, See also) and no nested or buried references; the "See also" section cleanly points to sibling skills. It scores 4 rather than 5 because at ~135 lines it exceeds the under-50-line simple-skill exception and keeps everything (including the Panels detail) inline with no content split, leaving minor organization headroom.

4 / 5

Total

18

/

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 is safe but uninformative: it perfectly prevents accidental triggering (excellent distinctiveness) yet tells neither Claude nor the user what the skill actually does, and contains no natural trigger vocabulary. It falls into the classic 'only when, no what' failure pattern.

Suggestions

Lead with the capability, e.g., "Request a time-series look-ahead (peekahead / future leakage) review of a commit and present the verdict and findings to the user. Use only when the user explicitly invokes /roborev-lookahead-review."

Include the natural synonyms users say — "look-ahead", "peekahead", "future leakage", "temporal leakage" — in the description so the skill is discoverable and self-documenting even under explicit-invocation policy.

Keep the explicit-invocation restriction, but place it after a one-sentence statement of what the skill does so both 'what' and 'when' are explicitly answered.

DimensionReasoningScore

Specificity

The description states only "Use only when the user explicitly invokes /roborev-lookahead-review" — it names the domain via the slash command but describes zero concrete actions the skill performs. It matches the score-2 anchor ("Names the domain but actions are minimal or generic") rather than 1 because it is a precise behavioral rule rather than pure abstract fluff, and not 3 because no actions are listed at all.

2 / 5

Completeness

The description gives an explicit 'when' ("Use only when the user explicitly invokes /roborev-lookahead-review") but completely omits 'what' the skill does, exactly matching the score-2 anchor "only 'when' is present without 'what'". It cannot score 3 because the 'what' is not weakly implied — it is absent.

2 / 5

Trigger Term Quality

The only term present is the literal slash command "/roborev-lookahead-review"; there are no natural keywords or synonyms a user would actually say (e.g., "look-ahead", "peekahead", "future leakage", "temporal leakage"), matching the score-1 anchor of no natural keywords.

1 / 5

Distinctiveness Conflict Risk

The clause "Use only when the user explicitly invokes /roborev-lookahead-review" creates a clear niche with a distinct, unambiguous trigger and minimal conflict risk with any other skill, matching the score-5 anchor ("Clear niche with distinct triggers; minimal conflict risk").

5 / 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/droid/roborev-lookahead-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.