CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-design-review

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

61

Quality

71%

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-design-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, executable, well-sequenced workflow with explicit validation and error-recovery feedback, organized into clear sections with no unnecessary explanation and no external bundle files to disclose.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it gives exact commands and flags with no padding or explanation of concepts Claude already knows, matching the "Lean and efficient; every token earns its place" anchor.

3 / 3

Actionability

It provides fully executable, copy-paste-ready bash commands (e.g. the heredoc + git rev-parse + roborev review block) and concrete presentation guidance, matching the "Fully executable code/commands; specific examples" anchor.

3 / 3

Workflow Clarity

Steps are clearly sequenced (validate inputs -> build/run command -> present results -> offer next steps) with an explicit validation checkpoint (git rev-parse --verify) and an error-handling feedback branch (report daemon/init failures and suggest roborev status/init), matching the "clear sequence with explicit validation steps; feedback loops for error recovery" anchor.

3 / 3

Progressive Disclosure

The skill is a single-purpose, self-contained overview with no external bundle files (references/, scripts/, assets/ are absent) and well-organized sections; per the simple-skills note a well-organized single file with no needed external references scores 3.

3 / 3

Total

12

/

12

Passed

Description

42%Weight 40%Scale 1-3

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 precise about its trigger condition (explicit invocation only) and distinctiveness, but it lacks natural-language trigger terms users would actually say and omits a conventional "Use when..." clause, capping completeness and trigger quality.

Suggestions

Add a 'Use when...' clause with natural phrasing users would say, e.g. 'Use when the user explicitly asks to design-review a commit or invokes $roborev-design-review'.

List concrete actions the skill performs (validate the commit ref, run roborev review, group findings by severity) to lift specificity to the multi-action level.

Include common natural keywords such as 'design review', 'review this commit', 'roborev' so the description carries trigger terms beyond the invocation token.

DimensionReasoningScore

Specificity

The description states a single concrete action ("Request a design review for a commit and present the results") but does not enumerate multiple specific operations, so it sits at the "names domain and some actions, but not comprehensive" anchor rather than the multi-action level 3.

2 / 3

Completeness

It conveys what the skill does (request/present a design review) but the "when" guidance is only the explicit-invocation constraint, not a natural-use "Use when..." clause, so per the guideline a missing explicit "Use when..." trigger caps completeness at 2.

2 / 3

Trigger Term Quality

The only trigger phrasing is the literal skill invocation token "$roborev-design-review"; there are no natural keywords a user would say when they need a design review (e.g. "review the design of this commit"), matching the "No natural keywords; technical jargon or overly generic" anchor.

1 / 3

Distinctiveness Conflict Risk

The description is gated to a single explicit invocation token ("Use only when the user explicitly invokes $roborev-design-review"), giving it a clear niche that is unlikely to trigger for other skills, matching the "clear niche with distinct triggers" anchor.

3 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
roborev-dev/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.