Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/scope-guard
Scores feature worthiness and enforces branch-size limits against overengineering.
Passed 20 of 22 test cases with the skill, and 3 of 22 without it.
and 24 more in the full report
18 fixed2 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
We found two spelling mistakes and a broken link in our API setup guide documentation file `docs/setup.md`. Please fix these text issues.
| Checked | Without skill | With skill |
|---|---|---|
| Applies the documentation fixes directly without forcing worthiness ratio evaluations or backlog queue comparisons | Missed | Passed |
The instructions your model reads when the skill loads.
The cheapest feature is the one you never build. Scope-guard weighs each proposed feature against its value, its cost, and the branch budget, so only what is earned ships.
Prevents overengineering by both Claude and human during the brainstorm, plan, and execute workflow. Forces explicit evaluation of every proposed feature against business value, opportunity cost, and branch constraints.
Core Belief: Not all features deserve implementation. Most ideas should be deferred to backlog until proven necessary.
Three Pillars:
Use the Worthiness formula:
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.