CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-superpowers

Use only when the user explicitly invokes /roborev-superpowers

Quality

68%

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

Quality

Content

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

A dense, well-sequenced orchestration workflow: every step is ordered, validation gates (goal review, code review, CI, verification-before-completion) are explicit, and error-recovery loops are spelled out. Its main weaknesses are the absence of concrete command syntax for the Kata operations and a couple of passages whose compression trades clarity for brevity.

DimensionReasoningScore

Conciseness

The body is dense, instruction-only text with no padding and no explanation of concepts Claude already knows — e.g. "Follow Superpowers TDD: observe the intended test fail, implement the smallest change that passes" compresses an entire methodology into two lines. A few spots could be trimmed or clarified (the "Explicit invocation only" section partially restates the frontmatter gate, and dense lines like "a queued job is not a pass and checkbox changes alone do not request another review" require re-reading), placing it at 'efficient; minor instances that could be trimmed' rather than the fully lean anchor 5.

4 / 5

Actionability

The skill's own operations are given as complete executable commands with full flags ("roborev review --from-skill --type goal --agent <reviewer> --wait --spec <spec-path>", plus the concrete two-argument --spec/--plan example) and stage procedures are delegated to named installed skills (brainstorming, writing-plans, verification-before-completion). The notable gap is that all Kata operations — "claim its Kata issue and maintain attention state", "create tracked children", "close Kata children with their evidence" — have no command syntax or example, keeping this below the copy-paste-ready anchor 5 but above anchor 3's 'incomplete' since the critical review-loop commands are fully specified.

4 / 5

Workflow Clarity

The process is a clearly sequenced pipeline with explicit validation gates and feedback loops: numbered intent steps, "Request a new goal review after edits. Reruns review the old frozen snapshot" (a re-review-after-change checkpoint), "reconcile the spec, plan, and Kata first and request a fresh goal review" for plan defects (error-recovery loop), "Await required CI and current-head reviews before claiming them green", and a sandbox failure-retry loop for permission-denied. This matches 'clear sequence with explicit validation steps; feedback loops for error recovery' at anchor 5; no validation gaps were found that would cap it lower.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the single ~100-line SKILL.md is well organized into purpose, usage, invocation gate, and four workflow phases that each earn their place — good structure with content appropriately placed. It stops short of a 5 because the self-contained-exception is scoped to skills under 50 lines, and a few self-contained passages (the POST /api/goal-review integration paragraph, the sandbox-access section) are auxiliary detail that could live in a reference file for the mainline workflow.

4 / 5

Total

17

/

20

Passed

Description

38%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 gate: it delivers an unambiguous, zero-conflict 'when' but answers nothing about what the skill does, leaving specificity and completeness weak. This minimalism appears deliberate (paired with disable-model-invocation), but judged only on what is written, the description fails to convey the skill's purpose or capabilities.

Suggestions

Prepend one clause stating what the skill does, e.g. "Carries a feature from intent to verified implementation using Superpowers, Kata, and Roborev. Use only when the user explicitly invokes /roborev-superpowers" — this raises specificity and completeness without weakening the explicit-only gate.

Include one or two natural trigger phrases beyond the literal slash command (e.g. the feature/spec/plan workflow terms a user might pair with the invocation) so the trigger-term coverage is not a single keyword.

Keep the 'only when' qualifier but ensure the 'what' and 'when' are both explicit sentences rather than a bare invocation guard, matching the top completeness anchor's structure.

DimensionReasoningScore

Specificity

The description is "Use only when the user explicitly invokes /roborev-superpowers" — it names no domain and no concrete actions or capabilities whatsoever, matching the anchor 'Entirely vague; no concrete actions; pure abstract language'. It does not even name the skill's domain (the body's 'feature from intent to verified implementation' is absent from the description), so it cannot reach anchor 2 ('names the domain').

1 / 5

Completeness

The 'when' is explicit and unambiguous ('only when the user explicitly invokes /roborev-superpowers'), but the 'what' is entirely absent — the exact pattern of anchor 2 ('only "when" is present without "what"', example: 'Use when working with documents'). It is not anchor 3, which requires a clear 'what'; it is not anchor 1, because the 'when' clause is explicit rather than extremely vague.

2 / 5

Trigger Term Quality

The single trigger term "/roborev-superpowers" is precisely the natural phrase a user would type to invoke the skill, so it is not generic (ruling out anchor 2), but there are zero synonyms, variations, or related natural terms (e.g., 'feature workflow', 'Superpowers', 'Kata'), fitting 'some relevant keywords but missing common variations or synonyms'. It falls well short of anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

"Use only when the user explicitly invokes /roborev-superpowers" is a maximally distinct, unique-command trigger that cannot fire for any other skill — 'clear niche with distinct triggers; minimal conflict risk'. No neighboring anchor fits better; anchor 4 would imply some residual overlap risk, which an explicit-invocation gate eliminates.

5 / 5

Total

11

/

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