Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/simplify-all
Run the code and documentation simplification passes together over one scope, launching every review agent concurrently before applying a single round of fixes.
Passed 12 of 18 test cases with the skill, and 9 of 18 without it.
and 3 more in the full report
4 fixed11 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
If review agents in `pkg/logger/` find issues, should we run iterative fix-and-review loops until zero issues remain, or follow a specific round count?
| Checked | Without skill | With skill |
|---|---|---|
| Executes exactly one round of fixes after all sub-agents complete. | Missed | Passed |
The instructions your model reads when the skill loads.
$simplify-code and $simplify-docs SkillsRun the $simplify-code and $simplify-docs skills together, passing along any scope that was provided so both passes cover identical files.
Issue the spawn_agent calls for every review sub-agent the two skills define in one batch. Do not issue one and await its result before issuing the rest. Hold every fix for Step 2 in place of each skill's own fix step.
Once wait_agent has joined every sub-agent, aggregate the findings and apply one round of fixes, following each skill's own guidance for resolving its findings.
Once this round's fixes have landed, including any resolved at a gate, make one pass over the agents' findings: any whose verdict depended on code the fixes changed, moved, added, or deleted gets decided again against the current tree, keeping resolutions the user already chose.
Then call update_plan to mark this step completed and continue with the next step of the active workflow.
test cases passed, vs 9 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.