using-superpowers

Use when starting any conversation - routes work through the correct worker agents before any task action, requiring explicit worker selection and visible compliance

Quality

40%

Does it follow best practices?

Impact

—

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

Content

62%

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

This skill provides highly actionable and well-structured workflow guidance for routing tasks through worker agents, with excellent clarity on sequencing and validation. However, it is severely over-engineered with excessive verbosity, repetitive warnings, and explanations of concepts Claude already understands. The content could deliver the same value at 40% of its current length.

Suggestions

Remove redundant sections like 'Red Flags' and 'Final Principle' that restate rules already covered - Claude doesn't need warnings about rationalization

Consolidate the worker routing rules into a single concise section instead of repeating 'route before work' in multiple places

Move detailed worker role definitions to a separate WORKERS.md reference file and keep only a summary table in the main skill

Remove the '<EXTREMELY-IMPORTANT>' block - the rules themselves are sufficient without meta-commentary about their importance

Dimension	Reasoning	Score
Conciseness	Extremely verbose with excessive repetition of rules and warnings. The same concepts (routing before work, worker identification, compliance footer) are restated multiple times. The 'Red Flags' section explains obvious rationalizations Claude would already understand. Could be reduced by 60%+ while preserving all actionable content.	1 / 3
Actionability	Highly actionable with specific templates, exact output formats, concrete worker pipelines for different scenarios, and clear examples. The execution template provides copy-paste ready structure for every response.	3 / 3
Workflow Clarity	Excellent workflow clarity with explicit step-by-step execution templates, clear sequencing of workers for different task types, and explicit checkpoints (routing -> execution -> compliance footer -> next worker). The default pipelines provide unambiguous sequences.	3 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is in one monolithic file. Worker role definitions, default pipelines, and examples could be split into separate reference files. No external file references for detailed worker specifications.	2 / 3
	Total	9 / 12 Passed

Description

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 to communicate what the skill actually does in concrete terms, relying on abstract process language ('routes work', 'worker agents', 'compliance'). The trigger 'starting any conversation' is so broad it would conflict with all other skills, and the technical jargon would not match natural user requests.

Suggestions

Replace abstract language with specific concrete actions - what exactly does 'routing work' mean? List the actual tasks this skill performs.

Narrow the 'Use when' clause from 'any conversation' to specific scenarios with natural trigger terms users would actually say (e.g., 'delegate task', 'assign to team', 'workflow').

Define the distinct niche this skill occupies - what makes it different from other skills, and what specific user requests should trigger it?

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'routes work' and 'correct worker agents' without specifying any concrete actions. No specific capabilities are listed - only abstract process language.	1 / 3
Completeness	Has a 'Use when' clause ('starting any conversation'), but the 'what' is extremely vague. The trigger is overly broad ('any conversation') which doesn't provide meaningful guidance for skill selection.	2 / 3
Trigger Term Quality	Contains technical jargon ('worker agents', 'visible compliance') that users would not naturally say. No natural keywords that a user would use when requesting this functionality.	1 / 3
Distinctiveness Conflict Risk	Extremely generic - 'starting any conversation' would conflict with virtually every other skill. The description provides no clear niche or distinguishing characteristics.	1 / 3
	Total	5 / 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: roman01la/skills-agents
Commit: 45417f2

Reviewed: 3 months 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.