CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-lookahead-review

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

Quality

73%

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/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-focused skill: exact commands for both invocation forms, explicit commit-ref validation with failure handling, clear error-recovery guidance, and concrete presentation/next-step instructions. Its only weaknesses are mild — slight meta-padding and redundancy between the Instructions and Examples sections, and a somewhat detailed Panels subsection inline.

DimensionReasoningScore

Conciseness

The body is lean and operational — exact commands, short sections, no re-teaching of concepts Claude already knows. Minor instances of over-explanation could be trimmed ("These instructions are guidelines, not a rigid script. Use the conversation context. Skip steps that are already satisfied." and the Examples section repeating the instruction steps), matching anchor 4 rather than anchor 5's "every token earns its place". It is clearly above anchor 3 because there is no unnecessary conceptual explanation.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: the no-commit case ("roborev review --from-skill --wait --type lookahead") and the specific-commit case (a complete bash snippet with heredoc, "git rev-parse --verify --end-of-options", and "|| exit 1"), plus concrete error-recovery commands ("roborev daemon status", "roborev init") and a specific follow-up offer with job-ID extraction guidance. This matches anchor 5.

5 / 5

Workflow Clarity

The four steps (validate inputs → build and run command → present results → offer next steps) are clearly sequenced with explicit validation ("git rev-parse --verify" with "If validation fails, inform the user the ref is invalid. Do not proceed."), error-recovery branches (daemon not running, repo not initialized), and conditional next steps keyed on the verdict. This matches anchor 5's "clear sequence with explicit validation steps; feedback loops for error recovery".

5 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized, clearly headed sections and a "See also" section pointing to sibling skills; all content is operational and needed at invocation time, so nothing is buried or nested. It scores 4 rather than 5 because at ~135 lines, inlined detail like the Panels subsection and the duplicated Examples could be tightened, and there is no overview-style signposting of the skill's longer sections.

4 / 5

Total

18

/

20

Passed

Description

43%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 a deliberate explicit-invocation guard that excels at distinctiveness and avoids false triggers, but it completely omits what the skill does. A user (or Claude) reading only the frontmatter learns the invocation condition without learning that the skill runs a time-series look-ahead (peekahead/future leakage) review of a commit and presents its verdict and findings.

Suggestions

State the capability first, e.g. "Runs a time-series look-ahead (peekahead / future leakage) review of a commit and presents the verdict and findings" — this would raise both specificity and completeness.

Keep the explicit-only trigger as a suffix ("Use only when the user explicitly invokes $roborev-lookahead-review") so the 'when' clause remains while adding the missing 'what'.

Optionally name the alias forms users say ("look-ahead review", "peekahead check") in the 'when' clause as things that must NOT auto-trigger, which clarifies boundaries without inviting implicit invocation.

DimensionReasoningScore

Specificity

The description states only "Use only when the user explicitly invokes $roborev-lookahead-review" — it names the invocation target but describes zero concrete actions or capabilities. It is not entirely vague (anchor 1), but it falls below anchor 2's "actions are minimal or generic" since no actions are given at all.

2 / 5

Completeness

The "when" is explicit ("Use only when the user explicitly invokes..."), but the "what" — what the skill actually does (a look-ahead/temporal-leakage review of a commit) — is entirely absent from the description. This matches anchor 2: "only 'when' is present without 'what'". It cannot score 3 because a clear 'what' is a prerequisite for that anchor.

2 / 5

Trigger Term Quality

The single trigger term "$roborev-lookahead-review" is exactly what a user must type to invoke it, so it is highly relevant, but the description includes no other natural keywords or synonyms (e.g., "look-ahead", "peekahead", "future leakage"), matching anchor 3's "some relevant keywords but missing common variations". It is above anchor 2 because the term is specific rather than generic, and below anchor 4 because one term does not constitute good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

Triggering is restricted to an exact literal command ("explicitly invokes $roborev-lookahead-review"), so accidental triggering for the wrong skill is essentially impossible, and sibling skills ($roborev-review, $roborev-fix) require their own distinct literal invocations. This matches anchor 5's "clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

12

/

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