CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-respond

Use only when the user explicitly invokes /roborev-respond

57

Quality

65%

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/claude/roborev-respond/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, actionable instruction set with executable commands, a well-sequenced workflow including validation and verification, and clean organization. It assumes Claude's intelligence and avoids concept over-explanation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it gives commands directly without explaining what roborev or code review is, and every section (including the invocation-only guard) earns its place.

3 / 3

Actionability

It provides fully executable bash commands (roborev show, comment, close) with real job IDs in worked examples that are copy-paste ready.

3 / 3

Workflow Clarity

A clear 3-step sequence (validate → record & close → verify) with an explicit validation checkpoint (panel_role guard, job inspection) and an error-recovery checklist in step 3.

3 / 3

Progressive Disclosure

A single self-contained file with well-organized sections and a clean one-level 'See also' pointer to a sibling skill; no nested or deeply chained references.

3 / 3

Total

12

/

12

Passed

Description

30%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 highly distinctive and has an explicit trigger clause, but it omits any statement of what the skill actually does and relies on a single technical command name rather than natural user keywords. It reads as a guardrail rather than a capability description.

Suggestions

Add a concrete capability statement, e.g. 'Records a comment on a roborev code review and closes it.' so the description answers 'what does this do'.

Include natural trigger phrasing users might say, such as 'code review' or 'respond to a review', rather than relying solely on the slash-command token.

Combine both halves into one line, e.g. 'Records a comment on a roborev code review and closes it. Use only when the user explicitly invokes /roborev-respond.'

DimensionReasoningScore

Specificity

The description ('Use only when the user explicitly invokes /roborev-respond') names no concrete actions — what the skill does (record a comment and close a review) appears only in the body, not the description.

1 / 3

Completeness

It explicitly answers 'when' with a 'Use only when...' clause but entirely omits 'what' the skill does, so it fails to answer both halves of the completeness question.

1 / 3

Trigger Term Quality

It names a relevant trigger (the literal /roborev-respond command) but offers no natural-language variations a user might actually say, leaning on a technical slash-command invocation rather than natural phrasing.

2 / 3

Distinctiveness Conflict Risk

The explicit invocation-only framing plus the unique /roborev-respond command name give it a clear, narrow niche that is unlikely to trigger for the wrong skill.

3 / 3

Total

7

/

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.