CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-lookahead-review-branch

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

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-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 well-structured, highly actionable runbook: concrete commands, explicit validation and error handling, and clear result-presentation guidance. Its only weakness is mild redundancy around panel semantics and a Panels section that carries detail that could live closer to the command reference.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — the peekahead/future-leakage terminology mapping and sandbox-escalation note are non-obvious and earn their tokens — but the --panel semantics are explained in three places (Usage, step 2, Panels), which could be trimmed.

4 / 5

Actionability

Fully executable copy-paste commands for both the default and base-branch cases, including a heredoc plus `git rev-parse --verify` validation snippet, concrete error-path suggestions (`roborev daemon status`, `roborev init`), and worked examples with realistic job IDs.

5 / 5

Workflow Clarity

A clear four-step sequence with explicit input validation ("If validation fails... Do not proceed"), an explicit error-recovery branch in step 3, and conditional next-step logic in step 4; the review operation is read-only, so no destructive-operation validation cap applies.

5 / 5

Progressive Disclosure

No bundle files exist or are needed, sections are well-organized with clear headers, and "See also" cleanly cross-references sibling skills; at ~135 lines with the multi-paragraph Panels subsection inlined it is good but not maximally split.

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 unambiguous about when to use the skill and completely distinct from other skills, but it says nothing about what the skill does. Since it omits any capability statement or natural trigger vocabulary, it reads as a guard clause rather than a description.

Suggestions

State what the skill does, e.g., "Runs a roborev time-series look-ahead review of all commits on the current branch and presents the verdict and findings"

Include natural trigger vocabulary such as "look-ahead", "future leakage", "peekahead", or "temporal leakage" so the purpose is legible without the command name

Keep the explicit-invocation constraint but append it after the capability statement, e.g., "...; use only when the user explicitly invokes /roborev-lookahead-review-branch"

DimensionReasoningScore

Specificity

"Use only when the user explicitly invokes /roborev-lookahead-review-branch" names the domain only implicitly through the command name and states no concrete actions; it is not pure abstract fluff (anchor 1) but lists no capabilities (anchor 3).

2 / 5

Completeness

The "when" is explicit ("Use only when the user explicitly invokes...") but the "what" is entirely missing, matching the anchor where only 'when' is present without 'what'.

2 / 5

Trigger Term Quality

The only trigger term is the literal command path; natural phrases a user would say (e.g., "future leakage", "peekahead", "temporal leakage" — all present in the body) are absent from the description.

2 / 5

Distinctiveness Conflict Risk

Requiring literal explicit invocation of a specific command gives it a clear niche with essentially zero risk of triggering for the wrong skill.

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