Iterative Debugging (Fix Loop)

For BEHAVIOR-1K (R1 Pro on Isaac Sim) use the sibling folder behavior/SKILL.md. It is a different protocol, not just different prompts: those tasks are long-horizon, so each seed grows its own policy one code block at a time, and the campaign freezes a skill library rather than a program. Everything below is for the tabletop benchmarks (LIBERO-Pro, Robosuite).

Use this skill to run a coordinated debugging campaign over any list of CaP benchmark tasks. No external baseline code or baseline output directory is used. Runs use the benchmark's own --init-mode (LIBERO: seeded, so development seeds 51–65 and the held-out partition are distinct scenes; Robosuite uses saved).

Setup