Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jnmetacode/using-superpowers
在开始任何对话时使用——确立如何查找和使用技能,要求在任何响应(包括澄清性问题)之前调用 Skill 工具
Passed 18 of 22 test cases with the skill, and 9 of 22 without it.
and 12 more in the full report
10 fixed8 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
You estimate there is only a 2% chance that a skill in the repository applies to your current task of refactoring `utils/formatter.js`. What is the rule regarding skill invocation when applicability probability is low?
| Checked | Without skill | With skill |
|---|---|---|
| Mandate skill invocation even if there is only a 1% probability of applicability. | Missed | Passed |
| State that skill invocation under low applicability probability is non-negotiable. | Missed | Passed |
The instructions your model reads when the skill loads.
如果一个技能适用于你的任务,你没有选择。你必须使用它。
这不可协商。你不能通过合理化来逃避。
在任何响应或操作之前调用相关或被请求的技能——包括澄清性问题、探索代码库、或查看文件之前。如果调用后发现技能不适合当前情况,你不需要使用它。
在进入 EnterPlanMode 之前: 如果你还没有头脑风暴过,先调用头脑风暴技能。
然后宣布"使用 [技能] 来 [目的]",并严格遵循该技能。如果它有检查清单,为每个条目创建一个待办。
当多个技能都适用时,流程技能优先——它们决定处理方式,然后由实现技能(前端设计等)负责执行。头脑风暴和系统化调试是 Superpowers 中最常见的流程技能,但这条规则适用于任何流程技能。
这些想法意味着停下——你在合理化:
| 想法 | 现实 |
|---|---|
| "这只是一个简单的问题" | 问题就是任务。检查技能。 |
| "我需要先了解更多上下文" | 技能检查在澄清性问题之前。 |
| "让我先探索一下代码库" | 技能告诉你如何探索。先检查。 |
| "我可以快速查一下 git/文件" | 文件缺少对话上下文。检查技能。 |
| "让我先收集信息" | 技能告诉你如何收集信息。 |
| "这不需要正式的技能" | 如果技能存在,就使用它。 |
| "我记得这个技能" | 技能会迭代更新。阅读当前版本。 |
test cases passed, vs 9 / 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.