CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-lookahead-review

Use only when the user explicitly invokes /roborev-lookahead-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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./internal/skills/grok/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 instruction set: exact commands for every input case, explicit validation with fail-fast behavior, concrete error-recovery paths, and precise presentation rules for verdicts, findings, and panel synthesis. Its only weaknesses are minor — slight redundancy in the IMPORTANT/Examples sections and a single-file structure that is a touch long for the simple-skill ideal.

DimensionReasoningScore

Conciseness

The body is tight and operational throughout — the one-line definition of look-ahead review ("checks whether the change uses information that would not yet be available... also called peekahead, future leakage, or temporal leakage") is domain knowledge Claude lacks, not padding. Minor trims are possible: the "These instructions are guidelines, not a rigid script" meta-paragraph and an Examples section that restates the numbered steps.

4 / 5

Actionability

Commands are copy-paste ready for both the no-commit case (`roborev review --from-skill --wait --type lookahead`) and the commit case (heredoc plus `git rev-parse --verify --end-of-options "$commit^{commit}" || exit 1`), with placeholders explained, error remediation commands given (`roborev daemon status`, `roborev init`), and even the job-ID extraction location specified ("the `Enqueued job <id> for ...` line or in the review header").

5 / 5

Workflow Clarity

A clear four-step sequence (validate inputs, build and run, present results, offer next steps) with an explicit fail-fast checkpoint ("If validation fails, inform the user the ref is invalid. Do not proceed."), an error-recovery feedback loop for command failures (daemon status / init / re-run), and verdict-conditional branching for next steps. This is a read-only review operation, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

A single self-contained file with clear sections, a See-also list pointing one level deep to sibling commands, and no nested or buried references. It scores 4 rather than 5 because the skill is ~135 lines — beyond the under-50-lines simple-skill exception — and content like the Panels subsection and the worked Examples could plausibly live in a reference file, though nothing is badly placed.

4 / 5

Total

18

/

20

Passed

Description

36%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 written as an invocation guard for an explicit-only slash-command skill, which makes it perfectly distinct but leaves it functionally opaque. It answers 'when' with precision while omitting 'what' entirely, and carries no natural trigger synonyms beyond the command name itself. Its low scores reflect the guard-only style rather than vagueness.

Suggestions

Add a brief 'what' clause before the invocation guard, e.g. "Runs a time-series look-ahead (peekahead / future leakage) review of a commit via roborev and presents the verdict and findings. Use only when the user explicitly invokes /roborev-lookahead-review."

Include natural trigger synonyms — look-ahead, peekahead, future leakage, temporal leakage — so the skill description maps to phrasing users actually say when they need this review.

Name one or two concrete capabilities (validates the commit ref, runs the review, presents findings grouped by severity with file paths and line numbers) so the description is self-explanatory without relying on the command name.

DimensionReasoningScore

Specificity

The description ("Use only when the user explicitly invokes /roborev-lookahead-review") names no concrete capability actions, but it is a precise conditional that alludes to the lookahead-review domain rather than pure abstract language, placing it above the entirely-vague anchor yet below the 1-2-concrete-actions anchor.

2 / 5

Completeness

It explicitly and precisely answers 'when' ("Use only when the user explicitly invokes") but says nothing about 'what' the skill does, exactly matching the anchor for only-'when'-present-without-'what'.

2 / 5

Trigger Term Quality

The only keyword is the literal slash-command name; natural phrases a user would say when needing this skill (peekahead, future leakage, temporal leakage, look-ahead) are absent from the description, so coverage is a single exact term with no variations or synonyms.

2 / 5

Distinctiveness Conflict Risk

The trigger is the exact literal command invocation, which is maximally distinct and cannot fire for the wrong skill; conflict risk with any other skill is minimal, matching the clear-niche anchor.

5 / 5

Total

11

/

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