CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-respond

Use only when the user explicitly invokes /roborev-respond

59

Quality

74%

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/grok/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 an exemplary instruction-only skill: concrete, executable commands, an explicit validation checkpoint before closing a review, and error-recovery guidance. Only minor redundancy between the IMPORTANT section, Instructions, and Examples keeps it from a perfect conciseness score.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no concept explanations, no library background), but the 'IMPORTANT' section partially restates the Instructions and the Examples section duplicates the command forms already shown, so minor trimming is possible.

4 / 5

Actionability

Commands are fully executable and copy-paste ready ('roborev show --job <job_id> --json', 'roborev comment --job <resolved_job_id> "<message>" && roborev close <resolved_job_id>'), and the Examples cover the common with-message and without-message cases with concrete job ID 1019.

5 / 5

Workflow Clarity

The three-step sequence is explicit with a genuine validation gate before the destructive close (inspect the job, refuse panel members, resolve the synthesis parent) and a verification step enumerating failure causes with remedies (daemon not running, missing job, uninitialized repo, already closed).

5 / 5

Progressive Disclosure

This is a self-contained single-purpose skill with well-organized sections and no content that belongs in separate files; no bundle files exist, so everything is appropriately inlined with clear navigation.

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 is highly distinctive and unambiguous about its trigger, but it omits any statement of what the skill actually does — recording a comment on a roborev code review and closing it. Because the capability content lives only in the body, the description under-informs anyone browsing the skill catalog.

Suggestions

State the capability in the description, e.g. 'Record a comment on a roborev code review and close it. Use only when the user explicitly invokes /roborev-respond.'

Include natural trigger phrasing users might say, such as 'respond to a roborev review' or 'comment on and close a review', while keeping the explicit-invocation constraint.

Keep the description in third person and avoid padding — the current one-line form is the right length once the 'what' is added.

DimensionReasoningScore

Specificity

The description ('Use only when the user explicitly invokes /roborev-respond') names the domain only via the command name and states zero concrete actions; the capabilities ('Record a comment... and close it') exist only in the body, so it sits between the vague-no-actions anchor (1) and the domain-plus-generic-action anchor (2).

2 / 5

Completeness

'When' is explicitly present ('Use only when the user explicitly invokes') but 'what the skill does' is entirely absent from the description, exactly matching the only-'when'-present-without-'what' anchor; it is not a 3 because the 'what' is missing outright rather than merely weak.

2 / 5

Trigger Term Quality

The literal command '/roborev-respond' is a precise trigger, but no natural phrases users would say ('respond to a review', 'comment on a code review') or synonyms are included, matching the some-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

The unique command name combined with explicit-invocation-only gating gives a clear niche with the literal command as its sole trigger, so conflict with other skills is minimal.

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