Loopify debug
Skill AndreRatzenberger/loopify/plugins/loopify/skills/loopify-debug
Loop yes. Prompt no. Agent skills that turn specs into checked agent loops with receipts.
npx -y skills add AndreRatzenberger/loopify --skill loopify-debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a loop is stuck, repeating failures, flaking, patching the wrong target, hitting an authority conflict, or burning turns without convergence.
SKILL.md
1.3 KB, as published. Nobody here has run it
loopify-debug
Rescue stuck loops.
When To Use
- The same failure repeats.
- Checks are flaky or invalid.
- The evaluator is weak.
- The loop is burning turns without convergence.
- The next useful step might be blocked or escalated, not another patch.
Do Not Use
- Do not keep applying cosmetic patches to repeated failures.
- Do not weaken checks just to escape a stuck loop.
- Do not ignore authority-boundary conflicts.
Workflow
- Read Loop Contract and trace.
- Classify the stuck pattern with
references/stuck-loop-taxonomy.md. - Identify whether the issue is implementation, check, spec, context, authority, or budget.
- Recommend recovery using
templates/recovery-plan.md. - Write a blocked report if no authorized recovery exists.
- Patch only when recovery is clear and authorized.
Output
Diagnosis, recovery plan, or blocked/escalated report.
Validation
- The repeated pattern is named.
- The next diagnostic differs from the failed attempts.
- Blocked/escalated recommendations cite the contract rule.
Example
Use loopify-debug on docs/examples/stuck-loop-debug/trace.md and classify why the loop is not converging.