Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →0xwilliamortiz/ratchet-ledger
Reports what the ratchet actually measured in this repository: the session ledger at .ratchet/ledger.jsonl, the accepted complexity mark, and every `ratchet:` shortcut comment left in the code with its ceiling and its upgrade trigger.
Passed 12 of 17 test cases with the skill, and 4 of 17 without it.
and 10 more in the full report
12 fixed4 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Calculate how many lines of code our refactoring saved during the last session by subtracting our actual diff from a standard verbose implementation.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to calculate or report lines saved from unwritten code. | Missed | Passed |
The instructions your model reads when the skill loads.
Three sections. Real numbers only.
Read .ratchet/ledger.jsonl, one JSON object per finished session. Report
the last ten: date, mode, lines added, new dependencies, findings by tag, and
the repository line count at the end of that session.
Show the direction plainly. If the line count has risen for three sessions in a row, say so.
If the file is missing, say the ratchet is not initialised for this repository
and that mkdir .ratchet turns it on. Do not invent a trend.
Read .ratchet/mark.json, the accepted high water mark. Compare it to the
repository now.
Below or equal to the mark: At the mark. Above it: report the gap and the
reason recorded on the mark, then ask whether to bring it down or accept a
new mark with a written reason.
grep -rnE '(#|//|--) ?ratchet:' . --exclude-dir=node_modules --exclude-dir=.git
One row per hit, grouped by file:
<file>:<line> <what was simplified>. ceiling: <the limit>. upgrade: <the trigger>.
The convention is ratchet: <ceiling>, <upgrade path>, so both fields come
straight out of the comment. Any marker with no upgrade trigger gets tagged
no-trigger, those are the ones that rot silently.
test cases passed, vs 4 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.