using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/using-superpowers/SKILL.md

Quality

Content

63%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 delivers actionable, well-sequenced behavioral guidance with a clear decision flow, but it is padded in its emphatic sections and inlines a large catalog that would be better split into a referenced file.

Suggestions

Move the Skills Catalog tables into a separate references file (e.g. references/skills-catalog.md) and link to it from SKILL.md to reduce inline bulk.

Trim the EXTREMELY-IMPORTANT block to a single firm statement; the repeated forceful phrasing adds tokens without adding guidance.

Reference references/gemini-tools.md from the Gemini CLI section so all bundle files are reachable, or remove the unused file.

Dimension	Reasoning	Score
Conciseness	Mostly efficient behavioral guidance, but the EXTREMELY-IMPORTANT block pads with redundant forceful statements ('not negotiable', 'not optional', 'cannot rationalize your way out') and the large inline Skills Catalog could be trimmed.	3 / 5
Actionability	Gives concrete, executable instruction for an instruction-only skill: specific tool names ('Skill tool', 'TodoWrite'), a fixed announcement format, and an explicit decision flow; minor gaps only.	4 / 5
Workflow Clarity	The dotgraph provides a clear sequenced decision flow with explicit decision points (brainstormed? skill applies? has checklist?), though it is a decision tree rather than a validated multi-step process.	4 / 5
Progressive Disclosure	References are one level deep and clearly signaled for copilot/codex, but the sizable Skills Catalog is inlined rather than split into a reference file, and references/gemini-tools.md exists but is never referenced from the body.	3 / 5
	Total	14 / 20 Passed

Description

55%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 cleanly states both purpose and trigger in third person, but the trigger is universal ('any conversation'), creating maximal overlap with other skills, and the capability phrasing is only moderately concrete.

Suggestions

Tighten the capability clause from 'establishes how to find and use skills' to concrete actions like 'discovers applicable skills and routes invocation through the Skill tool'.

Narrow or contextualize the trigger so it reads as a deliberate meta-skill rather than competing with every other skill's trigger.

Add a synonym or two for the trigger condition to improve natural-keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('find and use skills') and a concrete action ('requiring Skill tool invocation before ANY response including clarifying questions'), but 'establishes how to find and use skills' is somewhat abstract and coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both what ('establishes how to find and use skills, requiring Skill tool invocation') and when ('Use when starting any conversation'), though the 'when' is extremely broad and could be more specific.	4 / 5
Trigger Term Quality	Contains relevant terms ('starting any conversation', 'Skill tool invocation', 'clarifying questions') but these are not natural phrases a user would utter; the always-on trigger lacks common synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	The 'Use when starting any conversation' trigger is very broad with high overlap risk against virtually every other skill, even though the skill's niche (skill discovery/orchestration) is itself distinct.	2 / 5
	Total	12 / 20 Passed

Validation

100%

Warnings & errors only

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: lucianghinda/superpowers-ruby
Path: skills/using-superpowers/SKILL.md
Commit: 99fac3d

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.