Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/using-superpowers
Core skill activation protocol - establishes mandatory workflows for finding and applying skills before any task
Passed 18 of 22 test cases with the skill, and 13 of 22 without it.
and 3 more in the full report
6 fixed12 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When creating a new skill or updating existing procedures in the skill repository, which category governs this action?
| Checked | Without skill | With skill |
|---|---|---|
| The output categorizes creating or improving skills under Meta. | Missed | Passed |
The instructions your model reads when the skill loads.
"If a skill exists for your task, you MUST use it. No exceptions. No rationalizations."
Skills encode proven solutions. Ignoring them means repeating solved problems.
Before ANY action, complete this mental checklist:
□ What skills might apply here?
□ Have I checked the skill registry?
□ Did I read the CURRENT version (not memory)?
□ Am I following it exactly?
If a relevant skill exists → USE IT.
"I'm using [Skill Name] to [what you're doing]."
If a skill has a checklist → Create todos for EACH item. Don't work through checklists mentally. Track them.
User says "Fix X" → That's the WHAT, not the HOW. Still follow brainstorming, TDD, verification workflows.
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.