← ClaudeAtlas

local-workerlisted

Invoke a configured local LLM for a bounded, cheaply-verifiable subtask a Claude subagent has already decided is a good local-delegation candidate.
LouPineWays/Loop-Dee-Loup · ★ 1 · Code & Development · score 67
Install: claude install-skill LouPineWays/Loop-Dee-Loup
# Local worker The local-worker adapter (`tools/local-worker/adapter.mjs`) lets a Claude subagent delegate a narrow, self-contained subtask to a configured local LLM instead of doing it with hosted Claude tokens. It is a cheaper execution substrate beneath the subagent, not an independent authority: local output is candidate work, never accepted work, until the dispatching Claude subagent independently verifies it. ## When to use it A local LLM is not another rung in the deterministic-mechanism hierarchy (`script-maker` → `skill-maker` → `persona-maker` → ordinary instructions). If deterministic code can safely perform the operation, use a script instead — see `.claude/skills/script-maker/SKILL.md` — rather than spending any model inference, local or hosted, on it. Local delegation applies only to work that still requires model judgment: deterministic mechanism where possible → local LLM when suitable → hosted Claude when needed. Only after `model-check` (or the dispatching subagent's own equivalent judgment) has determined the task is a good local-delegation candidate. Good candidates: localized implementation from settled requirements; boilerplate; straightforward tests; fixture/test-data generation; mundane documentation derived from settled facts; bounded transformations or classifications; first-pass analysis that's cheap for Claude to check. Reject local delegation when the work depends on: unresolved founder intent; architecture/product-direction decisions; mater