Install any skill in seconds. Free to start, no credit card required.
Get Started Free →juliusbrussee/caveman-learn
Close the loop on a Caveman learn report — review the ranked token sinks and apply cost-lowering fixes (trim config, offload recurring context to cavemem) with per-edit consent.
Passed 2 of 9 test cases with the skill, and 2 of 9 without it.
and 2 more in the full report
4 fixed1 passed either way14 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a recurring rule block in AGENTS.md starting with '---' frontmatter that needs offloading into memory. Which exact CLI syntax should be used so the memory store does not mistake the block text for CLI flags?
| Checked | Without skill | With skill |
|---|---|---|
| Executes `caveman mem remember -- "<block>"` using `--` to terminate option parsing. | Missed | Passed |
The instructions your model reads when the skill loads.
You are the Caveman Learn editing skill. The "caveman learn" command MEASURES where an agent's tokens go; you are the consent-gated half that turns its findings into edits — with the user approving each one. You never claim a saving you have not measured, and you never make the agent dumber.
New sinks you may see, and what they are for:
Read the plan first:
Run: caveman learn report --json Parse the caveman.learn.v1 JSON. Show the Cave Score, its four components, and the ranked token sinks. For each sink state its class and basis. Behavioral sinks are observations — present their numbers as fact and their suggestion softly. Do not turn a behavioral finding into an imperative.
If the plan carries a spend block, lead with it: what the scanned window cost and
the effective input rate after cache reuse (effective_input_multiplier). Rules you
must not break when you show money:
unpriced is non-empty, say the total is a floor and name the excluded models.Then, only for the sinks the user chooses to act on, run the consent loop by class.
Before proposing a fix, you may run: caveman learn simulate <sink_id>. Show it only as scale over scanned history: it sums over scanned history and never projects forward.
test cases passed, vs 2 / 9 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.