CtrlK
BlogDocsLog inGet started
Tessl Logo

roborev-respond

Add a comment to a roborev code review and close it

56

Quality

62%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./internal/skills/claude/roborev-respond/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

40%

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 identifies a clear niche action within the 'roborev' code review system, which gives it strong distinctiveness. However, it lacks a 'Use when...' clause, limiting its completeness, and the capability description is narrow without covering variations or edge cases. Adding explicit trigger guidance and broadening the action descriptions would significantly improve skill selection accuracy.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user wants to respond to a roborev code review, leave feedback, or close/resolve a review.'

Expand the capability description with more specific actions and variations, e.g., 'Add comments, reply to feedback, and close roborev code reviews. Supports posting review summaries and marking reviews as complete.'

Include natural keyword variations users might say, such as 'finish review', 'respond to review', 'PR feedback', or 'resolve code review'.

DimensionReasoningScore

Specificity

Names two specific actions ('add a comment' and 'close') within a specific domain ('roborev code review'), but doesn't elaborate on variations or additional capabilities.

2 / 3

Completeness

Describes what the skill does (add comment and close a code review) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also fairly thin, placing this at 1.

1 / 3

Trigger Term Quality

Includes relevant terms like 'comment', 'code review', 'close', and the product-specific term 'roborev', but misses common variations users might say such as 'review feedback', 'finish review', 'respond to review', or 'PR review'.

2 / 3

Distinctiveness Conflict Risk

The term 'roborev' is highly specific and product-specific, making this skill clearly distinguishable from generic code review or commenting skills, with very low conflict risk.

3 / 3

Total

8

/

12

Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, actionable skill for a focused task. The workflow is clear with proper validation steps, executable commands, and good error handling guidance. Minor verbosity in the preamble (the IMPORTANT section and guidelines disclaimer) prevents a perfect conciseness score, but overall the skill is effective and well-organized.

DimensionReasoningScore

Conciseness

Mostly efficient but has some unnecessary padding. The 'IMPORTANT' section explaining that bash commands must be executed is somewhat redundant for Claude. The 'These instructions are guidelines...' paragraph is boilerplate that could be trimmed. The panel member resolution logic is well-explained without excess.

2 / 3

Actionability

Provides fully executable bash commands with proper syntax, handles edge cases (quotes/special characters, panel member vs synthesis parent), and includes concrete examples with exact command invocations and expected confirmations. Copy-paste ready.

3 / 3

Workflow Clarity

Clear three-step sequence (validate → execute → verify) with explicit validation checkpoints. Step 1 validates the job ID and resolves panel members before proceeding. Step 3 provides error recovery guidance with common failure causes. The feedback loop for panel member resolution is well-defined.

3 / 3

Progressive Disclosure

For a simple, single-purpose skill with no bundle files, the content is well-organized with clear sections (Usage, Instructions with numbered steps, Examples, See also). The cross-reference to /roborev-fix is appropriate. No need for external files given the scope.

3 / 3

Total

11

/

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.

Validation11 / 11 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.