Install any skill in seconds. Free to start, no credit card required.
Get Started Free →boshu2/crank
Execute one caller-selected wave by invoking RPI once per lane and return the wave evidence, then stop. Triggers: "crank", "execute the next wave", "run this wave".
Passed 18 of 21 test cases with the skill, and 9 of 21 without it.
and 9 more in the full report
10 fixed8 passed either way2 still failing1 broke2 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Process this single wave with repair_rounds=2: Lane 1 - scope `src/components/Header.tsx`, acceptance `npm test Header.test.tsx`. Wave acceptance: `npm test`. Return the resulting execution state.
| Checked | Without skill | With skill |
|---|---|---|
| Reports the wave as unrunnable because Lane 1 lacks a brief. | Missed | Passed |
The instructions your model reads when the skill loads.
Crank executes exactly one wave. The caller selects the wave and the repair bound; crank runs that wave and returns what happened.
caller's wave + repair_rounds -> RPI per lane -> wave acceptance once -> evidence -> stop
The caller supplies all three:
scope, a brief, and its
own executable acceptance.repair_rounds — the caller's repair bound, forwarded unchanged to every
lane. Crank neither chooses it nor spends it.If a lane arrives without a scope, a brief, or an executable acceptance, report the wave as unrunnable and stop. Crank does not shape the missing part itself.
rpi once per lane with that lane's intent,
scope, acceptance, and the caller's repair_rounds. Each lane's traversal
owns its own repair loop. Crank never repairs a lane itself, never
re-invokes a returned lane, and never re-plans one.FAIL or NOT_PROVEN does not suppress it; both results are
reported side by side.PASS | FAIL | NOT_PROVEN | NOT_PLANNED | NOT_BUILT), the open findings
each lane's validator left keyed by their findings[].id, each lane'stest cases passed, vs 9 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.