← ClaudeAtlas

single-agent-looplisted

Move a multi-agent system (router, planner, subagents) toward one agent loop with skills and tools, one measured change at a time. Use when asked to audit subagents, decide which to fold, merge, keep or call as tools, fold a subagent into a skill, or check whether a fold held up.
romanized/nebi-skill · ★ 1 · AI & Automation · score 74
Install: claude install-skill romanized/nebi-skill
# Single agent loop This skill takes a codebase where a router or orchestrator delegates to specialist subagents and moves it, in stages, toward one agent loop that loads skills and tools on demand. Every change is measured against the same eval before and after, and a subagent only goes away when the numbers say the replacement holds. Keeping a subagent is a fine outcome. The goal is a system you have evidence for, not the smallest possible number of agents. ## The steps Read only the file for the step you are on. | Step | File | Done when | | --- | --- | --- | | 0. Audit | `steps/00-audit.md` | The person has seen the inventory and agreed the verdicts | | 1. Baseline | `steps/01-baseline.md` | The current system has a score the person trusts | | 2. Merge | `steps/02-merge.md` | One pair is merged and compared | | 3. Fold | `steps/03-fold.md` | One subagent is folded and compared | | 4. Keep as a tool | `steps/04-as-tool.md` | One kept subagent is called as a tool and compared | | 5. Upkeep | `steps/05-upkeep.md` | The prompt, skills and ownership rules are tidy | Steps 2 to 4 repeat, once per row of the plan. ## How to run it Start at step 0, unless `single-loop/PLAN.md` already exists in the repo. If it does, read it and pick up at the first unticked box in its status list, then the first unticked item in its worklist. For each change in the plan: 1. Make the one change on its own branch or commit. If the folder is not a git repository, run `git init` and comm