CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-design-review-branch

Request a design review for all commits on the current branch and present the results

59

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is well-structured, actionable, and workflow-clear with proper validation and error recovery. The main weakness is redundant duplication of the command blocks across steps 2 and 3.

Suggestions

Avoid restating the full bash blocks in step 3; reference the command built in step 2 instead to reduce token cost.

Optionally factor the base-branch validation snippet into a single reusable block rather than embedding it inline twice.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no conceptual padding, but it duplicates the full bash command blocks verbatim in both step 2 ('Build the command') and step 3 ('Run the review in the background'), which could be tightened by referencing the earlier block.

2 / 3

Actionability

It provides concrete, executable commands with exact flags ('roborev review --branch --wait --type design') and a copy-paste-ready validation snippet ('git rev-parse --verify -- "$branch"'), so the guidance is fully actionable.

3 / 3

Workflow Clarity

A clear five-step sequence includes explicit validation ('If validation fails... Do not proceed') and error-recovery guidance (suggesting 'roborev status' / 'roborev init'), giving explicit checkpoints and a feedback loop.

3 / 3

Progressive Disclosure

No bundle files exist, but the body is well-organized into clearly signaled sections (Usage, When NOT to invoke, Instructions, Examples, See also) with one-level references to sibling skills, satisfying the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

50%

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 clear and specific about the task and scope but omits any explicit usage trigger, which caps both completeness and trigger quality. Adding a 'Use when...' clause would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review the design of commits on the current branch before merging.'

List a couple more concrete actions or outcomes (e.g. 'validate inputs, launch a background review, and surface verdict and findings grouped by severity') to strengthen specificity.

Sharpen distinctiveness by contrasting with sibling skills, e.g. 'Use this for whole-branch design reviews; use /roborev-design-review for a single commit.'

DimensionReasoningScore

Specificity

Phrases 'Request a design review for all commits on the current branch and present the results' name the domain and two actions (request review, present results), but the actions are generic rather than a comprehensive list of concrete capabilities.

2 / 3

Completeness

It states what the skill does but provides no 'when to use it' guidance; per the rubric a missing 'Use when...' clause caps completeness at 2.

2 / 3

Trigger Term Quality

Domain terms like 'design review' and 'commits on the current branch' are relevant, but there are no natural trigger phrasings (e.g. 'Use when...') and common variations a user might say are missing.

2 / 3

Distinctiveness Conflict Risk

It targets a fairly specific niche (design review of branch commits) but overlaps with sibling skills listed in 'See also' (roborev-design-review, roborev-review-branch), so it could still trigger for the wrong skill.

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