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

The body is a strong orchestration skill: it sequences a complex multi-tool workflow with explicit validation gates, feedback loops, evidence requirements, and edge-case handling (missing prerequisites, sandbox denial, absent integrations). Its main weaknesses are mild — some jargon-dense prose assumes ecosystem knowledge, and Kata-side operations lack concrete command examples.

DimensionReasoningScore

Conciseness

The body is dense instructional prose with essentially no padding or explanation of concepts Claude already knows, but a few defensive hedging sentences (e.g. 'a queued job is not a pass and checkbox changes alone do not request another review') and the Kata-integration paragraph could be trimmed — 'minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

The body gives a fully executable command with concrete flags ('roborev review --from-skill --type goal --agent <reviewer> --wait --spec ... --plan ...'), a usage template, and specific field-level guidance ('**Spec:**' link, deliverable/verification per task), but operations on Kata (claim issue, create children, record evidence) are named without concrete commands or examples — 'mostly executable guidance with minor gaps'.

4 / 5

Workflow Clarity

The multi-phase sequence (brainstorm → goal review → resolve findings → linked plan → joint review → TDD execution → code review → reconcile → verify → close) is explicit, with validation checkpoints (observe the test fail, run verification, review before executing the plan, await CI before claiming green) and genuine feedback loops (findings → fix → fresh goal review; plan defect → reconcile spec/plan first).

5 / 5

Progressive Disclosure

No bundle files exist and sections are well-organized by workflow phase with appropriately inlined orchestration detail; only minor gaps remain, such as the inline POST /api/goal-review integration detail and the absence of pointers to the external Superpowers/Kata/Roborev materials, which keeps it below the fully reference-split anchor 5.

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 is deliberately and cleanly explicit about its single trigger — the literal slash command — which maximizes distinctiveness but sacrifices everything else: it states no capability, no domain, and no purpose, so it scores poorly on specificity and completeness. A one-sentence statement of what the skill does (feature lifecycle with Superpowers specs, Kata tracking, and Roborev reviews) could be prepended without weakening the explicit-invocation gate.

Suggestions

Prepend a 'what' clause before the trigger, e.g. 'Carries a feature from intent to verified implementation using Superpowers specs/plans, Kata task tracking, and Roborev goal and code reviews. Use only when the user explicitly invokes /roborev-superpowers.'

Include a few natural domain keywords (feature implementation, spec, plan, review loop) so the skill's purpose is discoverable from the description alone while keeping the explicit-invocation-only trigger.

Keep the third-person imperative voice already used; no change needed there — the gap is content, not tone.

DimensionReasoningScore

Specificity

The description states only an invocation condition ('Use only when the user explicitly invokes /roborev-superpowers') and names no capability or concrete action the skill performs, matching the 'no concrete actions; pure abstract language' anchor rather than level 2, which requires naming a domain with at least minimal actions.

1 / 5

Completeness

Only the 'when' is present (explicit invocation), and it is explicit, but the 'what' is entirely absent — the reader cannot learn what the skill does — matching the anchor 'only when is present without what' exemplified by 'Use when working with documents'.

2 / 5

Trigger Term Quality

The single trigger term is the exact slash command a user would type to invoke the skill, which is precise and correct, but there are no supporting domain keywords (feature, spec, plan, review, implementation) or synonyms for discovery — 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Requiring literal invocation of a unique command name ('/roborev-superpowers') makes false triggers essentially impossible and overlap with other skills' triggers minimal, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

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