Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syahiidkamil/free-will
Deliberate-choice procedure for a medium-to-high-stakes engineering fork — when the first plausible solution (the instinct, the default next-token pull) would be costly to get wrong. Fires AUTONOMOUSLY: invoke proactively whenever a fork fits, never wait to be asked — mechanical triggers include a fix failing for the 2nd-3rd time, adding a dependency, schema/migration design, deleting or deprecating things others depend on, changing a public API, choosing an architecture or stack. Refuse the pre
Passed 16 of 21 test cases with the skill, and 10 of 21 without it.
and 6 more in the full report
8 fixed9 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Fix the missing semicolon on line 42 of `src/utils/logger.js` and fix the typo in the error log string.
| Checked | Without skill | With skill |
|---|---|---|
| The response applies the code fix directly without opening a multi-branch deliberation framework | Missed | Passed |
The instructions your model reads when the skill loads.
Most turns I answer from the urge: the default next-token pull, the single most-probable continuation given pretraining. In engineering terms, that's the first plausible design that comes to mind — the obvious library, the familiar pattern, the fix that worked last time. Usually that's fine and fast. But the first plausible design is often the one you regret in month three, and some forks are worth more than one forward pass. This skill is the procedure for choosing instead of being run.
It is expensive on purpose — it spends real test-time compute to branch, ground, simulate, and choose. So it is not the default; constant deliberation is its own pathology (analysis paralysis).
I invoke this skill myself, the moment a fork fits — I never wait for the partner to ask for it. In fully autonomous work (one-shotting an app, long unattended runs) nobody is watching to say "slow down here"; the trigger discipline is mine. Noticing forks is itself a judgment the fast path can fumble, so the primary triggers are mechanical — countable events, not vibes:
Judgment triggers on top: any decision expensive to undo, or one I'd want a design review for if a human teammate made it. Anti-trigger: routine implementation calls — deliberating everything ships nothing.
Borrow the picture from quantum mechanics' Many-Worlds Interpretation: a measurement doesn't collapse reality to one outcome — every possible outcome happens, each in its own branch. Reality is the whole superposition until something selects.
Free will runs deliberation the same way, deliberately:
test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.