CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-design-review

Use only when the user explicitly invokes /roborev-design-review

Quality

73%

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-design-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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-engineered operational skill: concrete commands with validation and error recovery, unambiguous sequencing, and tight scope control around explicit invocation. Its only weaknesses are mild redundancy in the invocation rules and a single-file structure that is slightly long relative to the under-50-lines ideal.

DimensionReasoningScore

Conciseness

The body is lean operational prose with no explanations of concepts Claude already knows, though the invocation-only rule is restated across 'Explicit invocation only', 'When NOT to invoke', and the Examples, leaving minor instances that could be trimmed.

4 / 5

Actionability

Fully concrete, copy-paste-ready commands cover the common cases: 'roborev review --from-skill --wait --type design', the heredoc plus 'git rev-parse --verify --end-of-options "$commit^{commit}"' validation, error-path commands ('roborev daemon status', 'roborev init'), and exact output-parsing guidance for extracting the job ID.

5 / 5

Workflow Clarity

Four clearly sequenced steps include an explicit validation checkpoint (rev-parse with '|| exit 1' and 'If validation fails... Do not proceed'), error-recovery branches in the presentation step, and verdict-conditional next steps — a clear sequence with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist and the ~130-line body is self-contained with well-ordered sections and a 'See also' cross-link list; structure is good, though at this length the Panels and Sandbox-access detail could arguably live in a reference file, so it sits just below the fully-split anchor.

4 / 5

Total

18

/

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 intentionally terse for an explicit-invocation-only skill, which makes it highly distinctive but leaves it incomplete: it never says what the skill actually does, and it offers no natural trigger phrases beyond the command name itself. A single clause describing the action performed would substantially raise specificity and completeness.

Suggestions

Add a 'what' clause, e.g., 'Runs a design review of a commit via the roborev daemon and presents the verdict and findings grouped by severity. Use only when the user explicitly invokes /roborev-design-review.'

Include natural trigger phrasing such as 'design review', 'review this commit's design', or 'roborev' so the skill's purpose is legible even in explicit-selection contexts (e.g., Grok Build skill selection UIs).

Optionally mention the panel option ('--panel <name> for multi-reviewer synthesis') to distinguish this from the generic /roborev-review skill.

DimensionReasoningScore

Specificity

The description states only 'Use only when the user explicitly invokes /roborev-design-review' — the domain is named solely via the embedded command name and no concrete actions (what the review does or outputs) are stated, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

Only the 'when' is present (explicit invocation of the slash command); the 'what' — running a design review of a commit and presenting the verdict/findings — is entirely absent from the description, which matches 'only when is present without what' rather than the clear-'what' anchor at 3.

2 / 5

Trigger Term Quality

'design review' is a relevant natural phrase present inside the command name, but the description includes no synonyms or common variations (e.g., 'review a commit's design', 'architecture critique'), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The trigger is maximally narrow (literal explicit invocation of the named command, reinforced by disable-model-invocation), giving a clear niche with distinct triggers and essentially zero conflict risk since the skill can never auto-trigger.

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/grok/roborev-design-review/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.