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/codex/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 SKILL.md body is a tight, executable runbook: it sequences validation, action, and verification with concrete commands and worked examples, and stays free of concept padding. The only weakness is inherited from the frontmatter description, not the body itself.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it gives executable commands and a numbered workflow without explaining what roborev is or restating basic concepts; every section earns its place, fitting the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Concrete copy-paste commands are provided throughout (e.g. 'roborev comment --job <resolved_job_id> "<message>" && roborev close <resolved_job_id>') plus fully worked examples, matching 'fully executable code/commands; specific examples; copy-paste ready'.

3 / 3

Workflow Clarity

A clear three-step sequence (validate input → record comment and close → verify success) with explicit validation checkpoints — the panel_role inspection gate and the verify-success error-recovery list — matches 'clear sequence with explicit validation steps; feedback loops for error recovery'.

3 / 3

Progressive Disclosure

This is a simple single-purpose skill with no bundle files; content is well-organized into clear sections (Usage, Instructions, Examples, See also) with no nested references, which per the rubric's simple-skills note warrants a 3.

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 narrowly a trigger guard for an explicit-invocation skill: it cleanly prevents accidental triggering but tells the reader nothing about what the skill actually does. Adding a concise capability clause ('Record a comment on a roborev code review and close it') would lift specificity and completeness substantially.

Suggestions

Add a 'what' clause, e.g. 'Record a comment on a roborev code review and close it. Use only when the user explicitly invokes $roborev-respond', so the description answers both what and when.

Optionally surface a natural-language synonym (e.g. 'respond to a roborev review') so the trigger term quality reaches broader coverage, while keeping the explicit-invocation constraint.

DimensionReasoningScore

Specificity

The description 'Use only when the user explicitly invokes $roborev-respond' names no concrete capability actions at all — it states only a trigger, leaving what the skill does (record a comment and close a review) unstated, matching the 'vague or no actions; abstract language' anchor.

1 / 3

Completeness

It answers 'when' (only on explicit invocation) but entirely omits 'what' the skill does, so it is 'missing what', which the rubric maps to score 1; it is not score 2 because score 2 requires 'what' present with weak/missing 'when', the inverse of what we have.

1 / 3

Trigger Term Quality

The only term is the literal invocation token '$roborev-respond', which is the relevant trigger for this explicit-invocation skill but offers no natural-language variations a user might say; this fits 'some relevant keywords but missing common variations' rather than score 1's pure jargon or score 3's broad coverage.

2 / 3

Distinctiveness Conflict Risk

Tying activation to a literal personal/plugin invocation token gives it a clear niche that is very unlikely to fire for the wrong skill, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.

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.