CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-superpowers

Use only when the user explicitly invokes $roborev-superpowers

Quality

67%

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-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 well-sequenced, validation-heavy orchestration workflow with concrete commands and explicit feedback loops, written tersely without padding. Its main structural weakness is that everything lives in one ~100-line file with no reference material split out, and a few steps delegate to external skills without invocation syntax.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and assumes competence — no tutorial padding or explanations of known concepts ("Use the installed Superpowers skills for their respective stages"). Minor tightening is possible: the "Explicit invocation only" section duplicates frontmatter policy, and dense policy sentences like "Automatic watching is useful feedback, but a queued job is not a pass" could be trimmed, matching anchor 4 rather than anchor 5.

4 / 5

Actionability

Concrete, executable detail is present: the full `roborev review --from-skill --type goal --agent <reviewer> --wait --spec <spec-path>` command, a complete bash example with concrete paths, the `POST /api/goal-review` endpoint, and named external skills (writing-plans, verification-before-completion). It stops short of anchor 5 because many steps ("Use Superpowers brainstorming", "claim its Kata issue") give direction rather than copy-paste commands, but it clearly exceeds anchor 3's pseudocode level.

4 / 5

Workflow Clarity

The multi-step process is explicitly sequenced (brainstorm → spec → goal review → resolve findings → plan → linked review → execute → complete) with validation checkpoints and feedback loops throughout: "Request a new goal review after edits", "observe the intended test fail", "verify each finding, fix valid in-scope defects with regression tests", "Await required CI and current-head reviews before claiming them green". This matches anchor 5's explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

No bundle files exist, and the ~100-line body is organized into well-ordered sections (Usage, invocation policy, intent-to-work, execute/review, completion, sandbox access) with command details inline where needed. It matches anchor 4 (good structure, most content appropriately placed, minor organization gaps); it falls short of anchor 5 because the skill exceeds 50 lines and some self-contained material (sandbox troubleshooting, the Kata integration endpoint contract) could plausibly live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

36%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 maximally distinctive and unambiguous about when to trigger (explicit invocation only), but it says nothing about what the skill actually does. A user or model scanning descriptions cannot learn its capabilities (feature spec-to-implementation with Superpowers, Kata, and Roborev) from the frontmatter alone.

Suggestions

Add a 'what' clause describing concrete capabilities, e.g. "Carries a feature from intent to verified implementation using Superpowers specs/plans, Kata task tracking, and Roborev goal reviews. Use only when the user explicitly invokes $roborev-superpowers."

Include natural trigger terms users might pair with the invocation, such as "feature", "spec", "implementation plan", or "goal review", so the description communicates the skill's domain even to readers who never invoke it.

State the concrete actions involved (brainstorm the spec, create the linked plan, run goal review, implement with TDD, record evidence) rather than relying solely on the invocation literal.

DimensionReasoningScore

Specificity

The description names the domain ("$roborev-superpowers") but states zero concrete capabilities — nothing about what the skill does (spec creation, task tracking, goal review, TDD execution) appears. It sits between anchor 1 (no concrete actions at all, which would require pure abstraction) and anchor 3 (domain plus 1–2 concrete actions, which is absent here), so it lands on anchor 2: domain named, actions minimal.

2 / 5

Completeness

The 'when' is explicit ("Use only when the user explicitly invokes $roborev-superpowers") but the 'what' is entirely missing — the description never says what the skill does. This matches anchor 2's 'only when is present without what' case (example: "Use when working with documents"); it cannot be anchor 3 because that requires a clear 'what'.

2 / 5

Trigger Term Quality

The only trigger token is the literal "$roborev-superpowers" — a single explicit-invocation keyword with no natural phrases a user would say ("implement this feature", "spec", "plan", "review loop"). That matches anchor 2 (one or two generic keywords, missing the natural phrases users say); it does not reach anchor 3 because no relevant natural-language keywords or synonyms are present.

2 / 5

Distinctiveness Conflict Risk

"Use only when the user explicitly invokes $roborev-superpowers" restricts triggering to an exact literal command, giving it a clear niche with a distinct trigger and minimal conflict risk with any other skill. It matches anchor 5 and exceeds anchor 4, which still allows minor overlap risk.

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