repeatedly-apply-skill
Made by JeffIteratively apply a named skill or slash command N times with progressive deepening. Use when "apply 10 times", "keep improving", "run again", iterative polish, improvement loop, or multi-pass refinement.
Works With
Quality and Utility come from canonical skill metadata. Community ratings appear separately as stars when subscriber reviews exist.
Subscribe to download
Public previews are available, but downloads, CLI sync, and premium content require an active subscription.
Sign In to Subscribe- Full skill content with deterministic versioning
- CLI sync + local search index
- Access to Jeffrey’s premium library
Save to your account
Saved skills live in your cloud list. Run jsm sync on each machine to pull them locally.
What's New with this Skill
1Updates, enhancements, and release notes for this skill.
New Skill: Repeatedly Apply Skill
A meta-skill that orchestrates N iterative passes of any other skill against a target, with each pass focusing on a different analytical dimension. Delegates each pass to a fresh subagent to prevent laziness accumulation.
- Orchestrator + subagent architecture prevents laziness accumulation
- Skill-adaptive missions: each skill gets domain-specific pass focuses
- Strictly serial execution with mandatory git diff verification
- Progress file (.skill-loop-progress.md) survives context compactions
- Anti-laziness rules: no hollow passes, later passes treated as MORE valuable
- Works with any skill or slash command: /ui-polish, /ubs, /simplify, etc.
Built on the observation that later passes of a skill find what early passes miss: someone who asks for 10 passes wants passes 5-10 to go deeper than 1-4. Each pass is a different mission, not a repetition. The skill generates missions adapted to whatever skill is being applied (ui-polish gets layout/color/animation passes; ubs gets null-paths/security/edge-case passes). Uses subagent delegation so each pass gets fresh context. Includes anti-laziness safeguards, strictly serial execution, a compaction-surviving progress file, and git-diff-based verification after every pass.