Choose and compose relevant skills when the workflow or tool route is unclear. Use known routers directly or list `skills/` for discovery; load only matching contracts. No skill invocation before every response and no universal design gate.
Installs into .claude/skills of the current project.
Are you the author of Using Superpowers?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/youlianvr-using-superpowers)
---
name: using-superpowers
description: >-
Choose and compose relevant skills when the workflow or tool route is unclear.
Use known routers directly or list `skills/` for discovery; load only matching
contracts. No skill invocation before every response and no universal design gate.
---
# Using skills — task-relevant composition
> Workspace adaptation, owner decisions 2026-10-03. The vendor's universal
> skill-first ceremony is superseded by AGENTS.md and task-local navigation.
## Procedure
1. Start from the request, current files and relevant workspace context. A known
router can be loaded directly; otherwise list `skills/` and read the
matching router's contract. Do not load every possible skill on a speculative match.
2. Choose the method that solves the task: debugging for unexplained failures,
brainstorming for open product choices, planning for coherent multi-step work,
verification for observable completion. A specified repair needs no design
interview or permission before ordinary commands.
3. Load the router first and only its needed parts. Short part names are not
standalone skills. Prefer existing workspace routes over a duplicate stack.
4. Follow useful checks with depth proportional to the work. Keep one coherent
task plan rather than copying every imported checklist into another ceremony.
5. If a skill conflicts with current policy, check source, scope and supersession.
Host instructions remain authoritative; repository authority is in AGENTS.md.
Report a material conflict and repair authorized repository drift in scope.
## Platform boundaries
Read tool schemas from the active host. This workspace runs on Freebuff: the only
mapping we keep is `HOSTS.md`, and even that is guidance, not
proof a tool is exposed. Never invent a skill tool, subagent capability, live
server or permission to patch the host. Freebuff is a coding worker; loading a
skill does not assign a persona.
## Verification
The chosen contract exists, matches the task and does not introduce an unrelated
startup, approval or background-work requirement. Verify the actual deliverable
through its usage path; selecting a skill is not evidence that the work succeeded.
