CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-respond

Use only when the user explicitly invokes /roborev-respond

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./internal/skills/claude/roborev-respond/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 lean, highly actionable operational guide: exact commands, a validation step before the destructive close, failure-mode remedies, and both usage examples. Its only weakness is mild redundancy from the Examples section repeating the instruction commands.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence (no concept explanations), but the Examples section repeats the exact comment/close commands already shown in Instructions, and the "These instructions are guidelines, not a rigid script" paragraph is trimmable meta-commentary — minor over-explanation, matching anchor 4.

4 / 5

Actionability

Commands are fully executable and copy-paste ready (`roborev job show --from-skill --job <job_id> --json`, the chained comment && close command), and worked examples cover both common cases (message provided vs. not) with concrete job IDs. This matches the anchor-5 example coverage.

5 / 5

Workflow Clarity

The sequence is explicit (validate input → comment and close → verify) with a pre-close validation checkpoint (inspecting the job and checking `job.panel_role`/synthesis parent) and an enumerated failure-cause list with remedies. Validation is present, so the destructive/batch cap does not apply, and the simple-skill exception permits a 5 for an unambiguous single task.

5 / 5

Progressive Disclosure

There are no bundle files and no nested references; the ~105 lines are compact single-file operational guidance organized into clear sections (Usage, Sandbox access, Instructions, Examples, See also), with a one-line pointer to the sibling /roborev-fix skill. Nothing here warrants splitting into separate files.

5 / 5

Total

19

/

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 functions purely as an invocation guard (consistent with disable-model-invocation: true) and does that job well for distinctiveness, but it never states what the skill does. Scoring only what is explicitly written, it falls short on specificity and completeness.

Suggestions

Prepend a capability clause stating what the skill does, e.g. "Records a comment on a roborev code review and closes it. Use only when the user explicitly invokes /roborev-respond" — this would raise both specificity and completeness without weakening the invocation guard.

Add one or two natural trigger nouns (e.g. "roborev review", "code review response") so the description carries keyword coverage beyond the bare command name, even though model invocation is disabled.

Keep the explicit-invocation constraint as the final sentence so the 'when' guidance remains unambiguous while the added 'what' clause fronts the capability.

DimensionReasoningScore

Specificity

The description names the command ("explicitly invokes /roborev-respond") but lists no actions whatsoever — nothing about commenting on or closing a review. It is not the pure abstraction of anchor 1, so it sits at anchor 2: domain named, actions absent.

2 / 5

Completeness

"Use only when the user explicitly invokes /roborev-respond" answers 'when' clearly but omits 'what' entirely — the anchor-2 case of only 'when' present without 'what'. A 3 would require a clear statement of what the skill does.

2 / 5

Trigger Term Quality

The single trigger term is the literal command "/roborev-respond", which is relevant but has no variations, synonyms, or related natural phrases. This is 'some relevant keywords but missing common variations', not the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The trigger is a single, highly specific slash command gated by an explicit "Use only when the user explicitly invokes" guard, giving it a clear niche with minimal conflict risk against any other skill.

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

Path

internal/skills/claude/roborev-respond/SKILL.md

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.