using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Install with Tessl CLI
npx tessl i github:projectbluefin/dakota --skill using-superpowers63
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 to communicate specific capabilities, instead describing a meta-level process about skill discovery. The overly broad trigger ('any conversation', 'ANY response') would cause constant conflicts with other skills, and the lack of concrete actions or natural user keywords makes it nearly impossible for Claude to appropriately select this skill.
Suggestions
Replace vague language with specific concrete actions this skill performs (e.g., 'Lists available skills, searches skill documentation, recommends appropriate skills for tasks').
Add natural trigger terms users would actually say, such as 'what skills do you have', 'help me find a skill', 'what can you do', 'list capabilities'.
Narrow the 'Use when' clause from 'any conversation' to specific scenarios like 'Use when the user asks about available capabilities, requests skill recommendations, or needs help finding the right tool for a task'.
| 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 extremely vague ('establishes how to find and use skills'). The when clause is present but overly broad rather than specific. | 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 | Triggering on 'any conversation' and 'ANY response' makes this maximally generic and would conflict with virtually every other skill in a collection. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured meta-skill that clearly explains when and how to invoke skills. Its strengths are actionability and workflow clarity with explicit decision trees and priority ordering. The main weakness is some verbosity in the red flags section and repeated emphasis that could be condensed.
Suggestions
Condense the red flags table to 4-5 most critical examples rather than 12, or move to a separate reference file
Remove or simplify the dot graph - the textual workflow description is sufficient and more token-efficient
Consolidate the repeated 'MUST invoke' messaging into a single clear statement
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy (the red flags table is extensive, the dot graph adds tokens without clear value). The repeated emphasis on 'MUST invoke' could be tightened. | 2 / 3 |
Actionability | Provides concrete, specific guidance: exact directory paths, clear tool names (Skill tool, TodoWrite), specific workflow steps, and a decision table. The instructions are immediately actionable. | 3 / 3 |
Workflow Clarity | Clear sequence with the dot graph visualization, explicit decision points ('Has checklist?'), and priority ordering for multiple skills. The flow from message received to response is unambiguous. | 3 / 3 |
Progressive Disclosure | References README.md for integration guidance but most content is inline. The red flags table and skill types section could potentially be separate files, though the skill is not excessively long. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.