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

40%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/using-superpowers/SKILL.md

Quality

Discovery

17%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description fails as a skill selector because it's designed to trigger on every conversation rather than specific use cases. It lacks concrete actions, natural user keywords, and would conflict with all other skills by design. The meta-nature of the skill (about using other skills) makes it poorly suited for the skill selection mechanism.

Suggestions

Reframe the description around specific user needs rather than 'any conversation' - identify what unique capability this skill provides that others don't

Add concrete actions the skill performs (e.g., 'Lists available skills, searches skill documentation, recommends appropriate skills for tasks')

Include natural trigger terms users might say like 'what skills are available', 'help me find a skill', 'which tool should I use'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'establishes how to find and use skills' without listing any concrete actions. It describes a meta-process rather than specific capabilities.	1 / 3
Completeness	Has a 'Use when' clause ('starting any conversation'), but the 'what' is weak and abstract. The trigger is too broad to be useful for skill selection among many options.	2 / 3
Trigger Term Quality	Contains no natural keywords users would say. Terms like 'Skill tool invocation' are technical jargon, and 'starting any conversation' is overly generic rather than a natural user trigger.	1 / 3
Distinctiveness Conflict Risk	'Starting any conversation' would trigger for literally every interaction, creating maximum conflict with all other skills. This is the opposite of a clear niche.	1 / 3
	Total	5 / 12 Passed

Implementation

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill effectively establishes the meta-process for skill discovery and usage with a clear decision flowchart and priority ordering. However, it's somewhat verbose with repetitive emphasis on mandatory skill invocation, and lacks concrete executable examples of actual skill tool invocations. The content would benefit from tightening the redundant warnings and adding a concrete example of invoking the Skill tool.

Suggestions

Add a concrete example showing actual Skill tool invocation syntax (e.g., `Skill(name="debugging")`) to improve actionability

Consolidate the repeated 'you must invoke skills' messaging—the EXTREMELY-IMPORTANT block, the Rule section, and Red Flags table all say the same thing

Consider moving the Red Flags table to a separate reference file to reduce the main skill's token footprint

Dimension	Reasoning	Score
Conciseness	The skill contains some redundancy (the 'Red Flags' table is verbose, the EXTREMELY-IMPORTANT block repeats the same point multiple times) but overall provides useful guidance. The dot graph adds value but could be simplified.	2 / 3
Actionability	Provides clear conceptual guidance on when/how to invoke skills, but lacks concrete executable examples. The instructions are procedural but abstract—no actual tool invocation syntax or copy-paste commands are shown.	2 / 3
Workflow Clarity	The dot graph provides an explicit decision flowchart with clear sequencing. The skill priority section establishes clear ordering, and the process vs implementation distinction helps Claude know which skills to invoke first.	3 / 3
Progressive Disclosure	References external files (references/codex-tools.md, CLAUDE.md, GEMINI.md, AGENTS.md) appropriately, but the main content is somewhat monolithic. The Red Flags table and multiple sections could be better organized or split out.	2 / 3
	Total	9 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: obra/superpowers
Commit: eafe962

Reviewed: 9 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.