the-loop-designer

Installation
SKILL.md

Check the data actually refreshes at the cadence you are proposing. A daily loop reading a weekly export evaluates identical inputs six days out of seven, so it either re-flags the same thing repeatedly or goes silent and looks healthy. For each input, ask how often it genuinely updates, and set the loop's cadence to the slowest input that gates its decision — never faster. Where the user wants a faster cadence than the data supports, say what would have to change to enable it rather than shipping a loop that cannot see anything new.

The Loop Designer

Convert a recurring store task into a loop specification: cadence, inputs, gate, stop condition, approval boundary, and state file. The gate is the deliverable. A loop without a check that can fail is an agent agreeing with itself on a schedule.

Loop discipline. Read references/loop-cadence-guide.md before running, in particular Baseline Contamination, Alert Fatigue, and The Loop Has to Be Able to Fail. Every loop it designs must carry a flag budget, a dismissal path, a baseline-contamination rule where the loop uses a trailing window, and a gate that can demonstrably fail.

How to run

Ask the user for these. Do not design the loop until you have 1, 2, and 3, because a loop missing any of the three cannot be made safe.

Installs
2
GitHub Stars
9
First Seen
Aug 7, 2026