CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-lookahead-review-branch

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

Quality

66%

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-lookahead-review-branch/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 tight, executable runbook: exact commands with an explicit ref-validation gate, concrete error-recovery guidance, precise result-presentation requirements, and worked examples for both invocation variants. Its only flaws are minor redundancy in restating flag conditions and a length that is borderline for a single-file skill with no reference split.

DimensionReasoningScore

Conciseness

The body is operational throughout — it never explains concepts Claude already knows, and the one definitional sentence (look-ahead/peekahead/future leakage) is domain-specific and earns its place. Minor trimmable redundancy keeps it from 5: the usage string appears twice (## Usage and the Instructions lead-in), and the two bullets after the base-branch snippet restate the if/else conditions already given.

4 / 5

Actionability

Guidance is fully executable: exact copy-paste roborev commands for both the no-base and base cases, a heredoc + `git rev-parse --verify --end-of-options` validation snippet, concrete error-recovery commands (`roborev daemon status`, `roborev init`), and where to find the job ID ("Enqueued job <id> for ..." line). Two worked examples cover the common cases; this matches the anchor for copy-paste ready commands with specific examples.

5 / 5

Workflow Clarity

A clear four-step sequence (validate inputs → build and run → present results → offer next steps) with an explicit validation gate ("If validation fails... Do not proceed") and explicit error-recovery branches for daemon/repo failures including re-running the review. This is a read-only review skill, so the destructive/batch cap does not apply, and the validation-and-retry structure matches the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the single file is organized into clearly signaled sections (Usage, Instructions, Examples, See also) with cross-skill navigation in "See also". It scores 4 rather than 5 because at ~135 lines it exceeds the under-50-line simple-skill exception, and the Panels subsection plus the Examples dialogues are content that could arguably live in a reference file if the skill grows.

4 / 5

Total

18

/

20

Passed

Description

27%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 functions purely as an invocation guard: it is precise about when the skill may run but completely silent about what the skill does or its problem domain. This makes it safe from conflicts but nearly useless for capability discovery, since neither Claude nor a user can tell from the description alone what invoking it will accomplish.

Suggestions

State the capability up front, e.g. "Runs a roborev look-ahead (temporal leakage) review of all commits on the current branch and presents the verdict and findings grouped by severity".

Include the natural trigger vocabulary users would say — "lookahead review", "peekahead", "future leakage", "temporal leakage" — rather than only the literal command token, so the description matches real user phrasing.

Adopt a "what it does + Use when..." structure as in the strong examples, keeping the explicit-invocation constraint as the 'when' clause.

DimensionReasoningScore

Specificity

The description is only "Use only when the user explicitly invokes $roborev-lookahead-review-branch" — it names no capability, domain, or concrete action whatsoever. This matches the anchor 'Entirely vague; no concrete actions' (not 2, which requires at least naming a domain with minimal actions).

1 / 5

Completeness

The 'when' is explicit (only on explicit invocation) but the 'what' — running a look-ahead/temporal-leakage review of branch commits and presenting results — is entirely missing. This exactly matches anchor 2 ('only when is present without what'); it cannot be 3 because a clear 'what' is required.

2 / 5

Trigger Term Quality

The only trigger term is the literal command token "$roborev-lookahead-review-branch"; the natural phrases a user would actually say ("lookahead review", "future leakage", "check the branch for peekahead") are absent. It sits between anchor 1 (only technical jargon) and anchor 3 (some relevant natural keywords), leaning below the midpoint because the token is a technical invocation string rather than a natural keyword.

2 / 5

Distinctiveness Conflict Risk

The explicit-invocation gate makes accidental triggering for the wrong skill very unlikely, giving a clear niche. It is not 5 because the description omits what the skill does, and closely related siblings ($roborev-review-branch, $roborev-lookahead-review) occupy overlapping territory, leaving minor overlap risk.

4 / 5

Total

9

/

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