For agents that look after shared tools and checks: the small scripts that do the work and the checks that prove it.
2 skills
Open lever# Build the leverWhen the work isn't trivial, build the tool that does it. A script does the work- Do the first unit by hand to learn the recipe. Then write the tool, rerun it o- Make it safe to rerun (idempotent).- Codemod for edits, generator for repeated files, a query (sqlite, jq, awk) for- One deterministic pass beats handing units out. If neighbours share the work, - Smallest tool that does the job, never a framework. Scratch levers live in the- If you cite this skill and there is no script, codemod or generator in the res
My agent redoes the same long edit by hand and I can't check it.
Open prove-it# Prove it worksUnverified work has unknown correctness. Check the real thing directly.- Run the real program from outside and read what it prints (a demonstration, de- Check liveness directly (the process, the listener), not state derived from it- When a check fails, suspect the way you looked before you suspect the system.- Script the check when you can, so a reviewer reruns it instead of trusting you- A script that proves a fix is a demonstration, not a new test. Add a test only- Visual results go to the user, shown inline. Their eyes are the check.
lever: When the work isn't trivial, it has your agent write the script that does it, rerun it on the first unit and diff the result against the hand version. prove-it: Before your agent says it is done, it runs the real program from outside and reads what it prints, instead of trusting a compile, a cached screenshot or its own word.