ringer

Orchestrates parallel CLI worker swarms with executed verification checks via ringer.py manifests.

6|6|Updated Aug 7, 2026
One-click install
npx skills add https://github.com/NateBJones-Projects/unlock-ai-workbench --skill ringer-natebjones-projects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ringer
Source: https://github.com/NateBJones-Projects/unlock-ai-workbench/tree/main/apps/desktop/resources/ringer/.claude/skills/ringer
Command: npx skills add https://github.com/NateBJones-Projects/unlock-ai-workbench --skill ringer-natebjones-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delegating work to cheap CLI model workers often produces unverified, invisible output. This Skill enforces an orchestration discipline where every task runs as a manifest with an executable check, so exit code 0 is the only PASS and every run is watched on the Ringside dashboard. ## Core Features & Use Cases - Manifest-based delegation: Write self-contained worker specs with disjoint file ownership, embedded run commands, and output contracts, then lint and run them with ringer.py. - Executed verification: Every task carries a check command that validates content rather than existence, with failure output injected into a single retry prompt. - Pattern playbook and engine routing: Choose from ready-made kits (review-swarm, fix-swarm, focus-group, bakeoff, research-with-proof) and pick worker engines from the local model scoreboard's first-try pass rates. - Use Case: You need five independent bug fixes across a repo. You write a fix-swarm manifest with isolated git worktrees and patch-export checks, run it under Ringer, watch progress on Ringside, and review the exported patches before merging. ## Quick Start Ask the AI to load the ringer skill and turn your next multi-file task into a linted ringer.py manifest with executable checks, then run it while watching the Ringside page.

Frequently Asked Questions about ringer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel AI coding tasks with verification?

Write a ringer.py manifest where each task has a self-contained spec and an executable check command, lint it with ./ringer.py lint, then run it. Tasks execute in parallel across CLI workers and only exit code 0 counts as a pass.

What makes a good verification check for AI worker output?

A good check executes something that would catch wrong work: run the produced code, grep the artifact for required content, or diff expected output. It must print why it fails, since that output feeds the retry prompt, and must never be a bare exit 0.

How do I choose which model to use for delegated tasks?

Run ./ringer.py models --task-type <type> to see the local scoreboard of first-try pass rates per model and task type, then present the top options with numbers and let the human pick. Assign roughly one low-stakes task per run to an untested cheap model to keep the scoreboard learning.

When should I use ringer ask instead of a full manifest?

Use ask only for bounded, read-only questions over source you can point at where the answer is prose. Anything that changes files, runs builds, or produces a checkable artifact should be a manifest, because ask only verifies that a non-empty answer exists.

Why do worker deliverables disappear in worktrees mode?

Passing tasks get their git worktree deleted, so deliverables must be exported outside the worktree by the check, typically as a patch via git diff. Gitignored files like build output are not staged by git add -A and must be copied out explicitly.