CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-review-branch

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

58

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-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 an exemplary executable instruction skill: concrete commands, robust validation with an explicit do-not-proceed checkpoint, panel-aware result presentation, and worked examples. Its only minor costs are the slightly verbose base-ref explanation and the long inline bash snippet that could be split into a script file.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanation of git or review concepts), with the paragraph explaining the base-ref recovery snippet ("it searches configured remote names from the longest slash-delimited prefix...") being the one spot that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands are provided for every path: the default review command, a complete robust bash snippet for base-branch validation including the upstream/main fetch recovery, and two concrete worked examples covering the default and security-review cases.

5 / 5

Workflow Clarity

A clear numbered sequence (validate inputs → build and run → present results → offer next steps) with an explicit validation checkpoint ("If validation fails, inform the user the ref is invalid... Do not proceed") and error-recovery guidance for daemon, repo-init, and errored-review cases.

5 / 5

Progressive Disclosure

A single self-contained file (no references/, scripts/, or assets/ exist in the bundle) with well-labeled sections and easy navigation; the ~30-line inline base-branch validation snippet is the one piece of content that arguably belongs in a scripts/ file, a minor organization gap.

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 highly distinctive and unambiguous about when to fire, but entirely silent on what the skill does. Adding a one-line capability statement (request a roborev code review of all commits on the current branch and present the verdict and findings) would make it complete without sacrificing its precision.

Suggestions

Add a capability statement before the trigger clause, e.g. "Requests a code review for all commits on the current branch and presents the verdict and findings. Use only when the user explicitly invokes $roborev-review-branch."

Mention the natural task terms users would associate with the skill (code review, branch review) so the skill is discoverable and self-describing even in listing contexts.

Optionally include the plugin invocation variant ($roborev:roborev-review-branch) in the description to cover the common invocation synonyms.

DimensionReasoningScore

Specificity

The description states only "Use only when the user explicitly invokes $roborev-review-branch" — it names the domain (explicit invocation of this specific skill) but describes zero concrete actions, so it sits between the 'no concrete actions' anchor and 'names domain, minimal actions' anchor.

2 / 5

Completeness

Only the 'when' is present (explicit invocation) without any 'what' — the skill never says it requests a code review of branch commits and presents results — structurally matching anchor 2's example 'Use when working with documents'.

2 / 5

Trigger Term Quality

The single exact trigger string "$roborev-review-branch" is precise and natural for an explicit-invocation skill, but no variations or synonyms (e.g. the plugin form "$roborev:roborev-review-branch") appear in the description itself, matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The explicit-invocation-only trigger carves out a clear niche with a distinct trigger string and minimal conflict risk with other skills, since generic requests like "review this branch" are explicitly excluded in the body.

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