CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

roborev-superpowers

Use only when the user explicitly invokes /roborev-superpowers

Quality

71%

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/claude/roborev-superpowers/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 an exemplar of lean orchestration writing: tightly sequenced multi-stage workflow with genuine validation checkpoints and feedback loops, concrete CLI commands and endpoints, and no padding or over-explanation. The only notable gaps are that the external Superpowers/Kata skill surfaces are invoked by name without examples, and no reference files exist to offload the denser multi-tool conventions.

DimensionReasoningScore

Conciseness

The ~103-line body is dense procedural instruction with zero concept explanation — it never explains what Superpowers, Kata, TDD, or a spec are, and assumes Claude's competence throughout ('Quote paths as shell arguments', 'Mark deliberate deferrals explicitly'). Every token carries non-obvious operational instruction, matching the level-5 anchor 'lean and efficient; every token earns its place'.

5 / 5

Actionability

Concrete executable commands appear with real flags and example paths ('roborev review --from-skill --type goal --agent <reviewer> --wait --spec docs/superpowers/specs/feature-design.md --plan docs/superpowers/plans/feature.md', 'POST /api/goal-review'), and named external skills and gates are specific. It falls short of level 5 because the Superpowers stage skills are only referenced by name without any invocation example, and placeholders like <reviewer> are resolved only by prose, leaving minor gaps.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced (numbered spec-to-plan steps in 'Connect intent to tracked work', then execute, then complete) with explicit validation checkpoints and feedback loops: 'observe the intended test fail', 'run the task's verification', 'Await required CI and current-head reviews before claiming them green', and the review loop 'Request a new goal review after edits. Reruns review the old frozen snapshot.' This matches the level-5 anchor of clear sequence with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

The skill is a single file with no bundle directories (verified: references/, scripts/, assets/ do not exist), and no inlined content clearly belongs in separate files — sections (Usage, Explicit invocation, Connect intent, Execute, Complete, Sandbox access) are well-organized and navigable. It matches the level-4 anchor 'good structure; most content is appropriately placed' rather than 5, because it exceeds the under-50-line simple-skill case and offers no clearly signaled references for the multi-tool details (Kata graph conventions, roborev CLI surface) it alludes to.

4 / 5

Total

18

/

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 is highly distinct and unambiguous about when to fire, but it completely omits what the skill does. While 'disable-model-invocation: true' makes gating intentional, the rubric scores only what is stated, so the missing 'what' heavily penalizes completeness and specificity.

Suggestions

Add a brief capability statement answering 'what', e.g., 'Carries a feature from intent to verified implementation using a Superpowers spec and linked plan, Kata task tracking, and Roborev goal/code review.'

Include the core concrete actions (brainstorm the spec, review it with roborev, execute via TDD, record evidence) so the description names the domain and 1-2 concrete actions even while remaining explicit-invocation-only.

Mention the natural invocation variations users may actually type (e.g., 'roborev-superpowers', 'run the roborev workflow') if any of them should activate the skill.

DimensionReasoningScore

Specificity

The description 'Use only when the user explicitly invokes /roborev-superpowers' names zero concrete actions or capabilities — it does not state what the skill does at all, matching the level-1 anchor of 'no concrete actions'. It does not even rise to level 2 because it names no domain of work, only the invocation condition.

1 / 5

Completeness

The 'when' is explicit ('Use only when the user explicitly invokes') but the 'what' is entirely absent, which precisely matches the level-2 anchor 'only when is present without what'. It cannot score 3 or higher because nothing in the description conveys the skill's purpose or capabilities.

2 / 5

Trigger Term Quality

The single trigger term is the literal slash command '/roborev-superpowers', which is exactly what a user would type for explicit invocation, but no variations or synonyms (e.g., 'roborev', 'superpowers') are covered. This matches the level-3 anchor 'some relevant keywords but missing common variations or synonyms'; it is not level 4 because coverage is a single term.

3 / 5

Distinctiveness Conflict Risk

The description is bound to a unique named slash command with an explicit-invocation-only condition, giving a clear niche with a distinct trigger and minimal conflict risk with any other skill — a direct match to the level-5 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/claude/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.