Ringer

Orchestrator playbook and routing rules for Ringer, the verified-swarm delegation tool (ringer.py). TRIGGER — load BEFORE acting, not after — whenever: you are about to run ANY script or command that calls a model or drives a conversational/eval harness (probe, smoke test, simulation, grader, persona conversation) outside a live Ringer run; you are about to start an edit→test→edit loop or a batch of similar edits across files; you are about to do a "quick check" that spawns a model or a CLI agent; you are reviewing or diagnosing failed worker or model output; you catch yourself thinking a task is "small enough to just do myself" — that thought IS the trigger (a single task is a one-task manifest, and a bounded read-only question is `ringer.py ask`); or you are writing or reviewing a manifest, choosing a swarm pattern (review swarm, fix swarm, focus group, bakeoff, research-with-proof), picking a worker engine, or debugging a failed run. SKIP only for: reading or searching files, git operations, a one-file few-line ONE-SHOT edit (once — if you are back for a second pass, that is a loop: TRIGGER), authoring prose/specs/docs straight from your own context, or pure conversation.

mkdir -p ~/.claude/skills/ringer
curl -L https://claudskills.com/skills/ringer/SKILL.md \
  -o ~/.claude/skills/ringer/SKILL.md

@misc{ringer-2026,
  author    = {NateBJones-Projects},
  title     = {Ringer [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/ringer/}
}