roborev-respond

Use only when the user explicitly invokes /roborev-respond

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./internal/skills/droid/roborev-respond/SKILL.md

Quality

Content

82%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, actionable guide for a simple single-purpose skill: concrete commands, a clear numbered workflow with validation, and worked examples. Its main weakness is minor verbosity in the framing prose rather than any substantive gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and tight sections, but the 'Explicit invocation only' section restates the description and the 'IMPORTANT'/'guidelines' prose could be trimmed, matching the 'efficient; minor instances of over-explanation that could be trimmed' anchor; not 5 because of that reusable padding.	4 / 5
Actionability	Copy-paste-ready commands are given for inspection, commenting, and closing (e.g. 'roborev show --job <job_id> --json' and 'roborev comment --job <resolved_job_id> "<message>" && roborev close <resolved_job_id>'), with worked examples for both the with-message and without-message cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	A clear three-step sequence (validate input, record comment and close, verify success) includes a pre-flight validation checkpoint (the panel_role guard) and a verify step with enumerated failure causes, matching the 'clear sequence with most checkpoints present; minor validation gaps' anchor; not 5 because error recovery is 'report to the user' rather than a fix-and-retry feedback loop.	4 / 5
Progressive Disclosure	With no bundle files present, the single-purpose content is appropriately kept inline and organized under clear headers (Usage, Instructions with numbered subsections, Examples, See also), matching the 'good structure; most content appropriately placed' anchor; not 5 because the body runs a bit long for a simple skill and some prose sections could be further condensed.	4 / 5
	Total	17 / 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 a pure invocation guard: it tells Claude when to fire but not what the skill does, leaving the 'what' entirely unspecified. It is highly distinct but light on capability and trigger-term coverage.

Suggestions

Add a concise 'what' clause, e.g. 'Record a comment on a roborev code review and close it; use only when the user explicitly invokes /roborev-respond.'

Include natural-language synonyms users might say (e.g. 'respond to a review', 'comment on and close a review') alongside the slash command to broaden trigger coverage.

State the concrete actions (record comment, close review) in the description so it answers both 'what' and 'when'.

Dimension	Reasoning	Score
Specificity	The description ("Use only when the user explicitly invokes /roborev-respond") names the domain via the command name but describes zero concrete actions, matching the 'names the domain but actions are minimal or generic' anchor; it does not reach 3 because no capability is stated at all.	2 / 5
Completeness	Only the 'when' is present (explicit invocation of the command) with no statement of what the skill does, matching the 'only when is present without what' anchor; not 3 because the 'what' is entirely absent rather than weakly implied.	2 / 5
Trigger Term Quality	The single trigger term '/roborev-respond' is specific and relevant rather than generic, but no synonyms or natural-language variations are offered, fitting the 'some relevant keywords but missing common variations' anchor; not 2 because the keyword is not generic.	3 / 5
Distinctiveness Conflict Risk	Requiring explicit literal invocation of a named slash command is a maximally distinct trigger with minimal conflict risk, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	12 / 20 Passed

Validation

100%

Warnings & errors only

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/droid/roborev-respond/SKILL.md
Commit: a87c9af

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.