CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-lookahead-review-branch

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

Quality

64%

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

Quality

Content

81%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 a strong, executable runbook: concrete commands, explicit input validation, error-recovery guidance, and a clear four-step workflow. Its weaknesses are moderate redundancy (repeated flag explanations and near-verbatim Examples) and an inline-heavy structure. Trimming the duplicated material would improve token efficiency without losing actionability.

Suggestions

Remove the duplicated flag explanations under 'Build and run the command' — the two command variants and the Usage line already convey when --base and --panel apply.

Cut or compress the Examples section, which restates the Instructions nearly verbatim; a single short example with realistic output framing would suffice.

Consider moving the Panels detail into a short reference file (or tightening it to 3-4 lines) so the core workflow stays scannable.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it defines the domain term and gives operational guidance Claude would not infer — but there is noticeable repetition: the usage line is restated in Instructions, the --base/--panel bullet explanations restate what the two command variants already show, and the Examples section replays the instructions nearly verbatim. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not a 4 because the redundancy spans several sections.

3 / 5

Actionability

Commands are copy-paste ready and cover the common cases: "roborev review --from-skill --branch --wait --type lookahead" for the default case, and a complete base-branch snippet with "git rev-parse --verify --end-of-options" plus a heredoc template. Error-remediation commands ("roborev daemon status", "roborev init", "/roborev-fix <job_id>") and concrete job-ID extraction guidance ("Look for it in the `Enqueued job <id> for ...` line") are also specified.

5 / 5

Workflow Clarity

The four steps (validate inputs → build and run command → present results → offer next steps) are clearly sequenced, with an explicit validation checkpoint ("git rev-parse --verify --end-of-options ... || exit 1" and "If validation fails, inform the user the ref is invalid. Do not proceed.") and error-recovery feedback loops (report daemon/repo errors and suggest "roborev daemon status", "roborev init", or re-running). The destructive/batch cap does not apply since the skill only runs a read-only review.

5 / 5

Progressive Disclosure

The body is well-organized with clear section headers (Usage, Sandbox access, When NOT to invoke, Instructions, Examples, See also) and all content lives in one appropriately sized file with no nested references. However, the skill exceeds 50 lines and detailed material (the Panels subsection and the largely duplicative Examples) is inlined where a leaner core or a single reference file could carry it, so it sits at 'good structure; minor organization gaps' rather than the clear split-and-reference ideal.

4 / 5

Total

17

/

20

Passed

Description

31%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 conservative for an explicitly-invoked skill, which makes it highly distinctive but leaves it with no capability statement. A user reading only the description cannot tell what the skill does. Adding a one-line 'what' (runs a look-ahead/temporal-leakage review of all commits on the current branch) would raise completeness and specificity substantially without increasing auto-trigger risk.

Suggestions

Add a capability clause to the description, e.g. "Runs a time-series look-ahead (future/temporal leakage) review of all commits on the current branch and presents the verdict and findings. Use only when the user explicitly invokes /roborev-lookahead-review-branch."

Include the natural synonyms (look-ahead, peekahead, future leakage, temporal leakage) in the description so it is discoverable, while keeping the 'explicit invocation only' restriction to prevent accidental triggering.

Keep the distinctiveness strength: retain the exact-command trigger condition even after adding the 'what' and keyword coverage.

DimensionReasoningScore

Specificity

The description states only "Use only when the user explicitly invokes /roborev-lookahead-review-branch" — no concrete actions or capabilities are named anywhere in the description. It does not even name the domain (look-ahead review), so it falls below the 'names the domain but actions are minimal' anchor.

1 / 5

Completeness

The 'when' is explicit ("Use only when the user explicitly invokes...") but the 'what' is entirely absent — the description never says the skill runs a time-series look-ahead review of branch commits. This matches the anchor 'only when is present without what' exactly, and is not a 3 because there is no clear 'what' at all.

2 / 5

Trigger Term Quality

The only trigger term is the literal command name "/roborev-lookahead-review-branch"; natural phrases a user might say ("lookahead review", "future leakage", "temporal leakage") appear only in the body, not the description. It has one exact keyword but misses the natural variations, matching 'one or two generic keywords; missing the natural phrases users say'.

2 / 5

Distinctiveness Conflict Risk

Triggering is restricted to the exact literal command string (or structured Factory skill selection), which is maximally distinct and cannot fire on generic requests like "check this branch for leakage". This gives minimal conflict risk even against sibling skills such as /roborev-lookahead-review, matching the 'clear niche with distinct triggers' anchor.

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-branch/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.