| name | sp-using-superpowers |
| description | Bootstrap/router skill — establishes how to discover and invoke OpenClaw superpowers skills, requiring skill invocation before ANY response including clarifying questions. Use when starting any conversation or task. |
| tags | ["bootstrap","router","workflow","skills","meta"] |
| version | 1.0.0 |
| risk | safe |
| triggers | ["using superpowers","how do I use skills","discover skills","invoke a skill","what skills are available","starting a new task"] |
| requirements | {"cli":[],"env":[]} |
| upstream_ref | skills/using-superpowers/SKILL.md |
| author | AlphaComposite |
| license | MIT |
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
How to Access Skills
In OpenClaw: Skills live under ~/openclaw/skills/*/SKILL.md. Use the read tool to load the relevant SKILL.md, then follow its instructions directly. Never skip reading the current version — skills evolve.
Ported superpowers use the sp- prefix and live under ~/openclaw/projects/openclaw-superpowers-port/skills/sp-*/SKILL.md (or wherever this pack is installed).
Discovery: List available skills with ls ~/openclaw/skills/ and ls <install-dir>/skills/. Match the task against skill descriptions to find the right one.
Using Skills
The Rule
Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means you should read the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to follow it.
digraph skill_flow {
"User message received" [shape=doublecircle];
"About to enter planning mode?" [shape=doublecircle];
"Already brainstormed?" [shape=diamond];
"Read sp-brainstorming SKILL.md" [shape=box];
"Might any skill apply?" [shape=diamond];
"Read matching SKILL.md" [shape=box];
"Announce: 'Using [skill] to [purpose]'" [shape=box];
"Has checklist?" [shape=diamond];
"Create a task per checklist item" [shape=box];
"Follow skill exactly" [shape=box];
"Respond (including clarifications)" [shape=doublecircle];
"About to enter planning mode?" -> "Already brainstormed?";
"Already brainstormed?" -> "Read sp-brainstorming SKILL.md" [label="no"];
"Already brainstormed?" -> "Might any skill apply?" [label="yes"];
"Read sp-brainstorming SKILL.md" -> "Might any skill apply?";
"User message received" -> "Might any skill apply?";
"Might any skill apply?" -> "Read matching SKILL.md" [label="yes, even 1%"];
"Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
"Read matching SKILL.md" -> "Announce: 'Using [skill] to [purpose]'";
"Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
"Has checklist?" -> "Create a task per checklist item" [label="yes"];
"Has checklist?" -> "Follow skill exactly" [label="no"];
"Create a task per checklist item" -> "Follow skill exactly";
}
Red Flags
These thoughts mean STOP — you're rationalizing:
| Thought | Reality |
|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't count as a task" | Action = task. Check for skills. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
Skill Priority
When multiple skills could apply, use this order:
- Process skills first (sp-brainstorming, systematic-debugging) — these determine HOW to approach the task
- Implementation skills second (domain-specific skills) — these guide execution
"Let's build X" → sp-brainstorming first, then implementation skills.
"Fix this bug" → systematic-debugging first, then domain-specific skills.
Skill Types
Rigid (test-driven-development, systematic-debugging): Follow exactly. Don't adapt away discipline.
Flexible (patterns, design): Adapt principles to context.
The skill itself tells you which type it is.
User Instructions
Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows. Always check for applicable skills before acting.
