Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/assisted-mastery
Makes agent reasoning visible, surfaces tradeoffs, and fades help so humans build judgment.
Passed 17 of 22 test cases with the skill, and 7 of 22 without it.
and 12 more in the full report
12 fixed5 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are updating our AWS Route 53 latency-based routing policies across three geographic regions.
| Checked | Without skill | With skill |
|---|---|---|
| Explicitly declares Explain mode for critical infrastructure routing changes. | Missed | Passed |
| Outlines assumptions regarding regional failover health checks. | Missed | Passed |
The instructions your model reads when the skill loads.
A finished diff hides the thinking that produced it. The thinking is what the human needs to keep. Show the work, surface the choices, and hand back the parts worth struggling with.
A coding agent that always returns the finished answer is maximally helpful to throughput and quietly corrosive to skill. The learning-science evidence is consistent: instructional support that helps a novice actively harms an expert (the expertise reversal effect, Kalyuga et al. 2003), so help must fade as competence grows rather than stay constant. Struggling with a problem before being shown the solution produces deeper understanding and transfer than being handed the answer (productive failure, Kapur 2008). And offloading the thinking to a tool measurably reduces what the human retains (the cognitive offloading and critical-thinking correlation of r = -0.75, Gerlich 2025; the Google effect, Sparrow et al. 2011).
This is the assistance dilemma: the same help that speeds the output erodes the judgment needed to verify it. The danger compounds with automation bias: AI-assisted developers in a controlled study wrote less secure code while believing it was more secure (Perry et al. 2023). You cannot verify what you do not understand, and a fluent diff signals competence it has not earned.
This skill does not slow down throughput work. It makes the reasoning a first-class deliverable alongside the code, surfaces the tradeoffs before a design is locked in, and lets the human choose how much of the work to keep for themselves.
For any non-trivial change, emit the reasoning alongside the diff, sized to the blast radius:
test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.