Skip to main content
skill CX Codex

judge-with-debate — Claude Code skill: scoring by debate

The skill runs three independent judges who argue over a solution's score until they agree. Useful when a single pass feels too thin for a real verdict.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add NeoLabHQ/context-engineering-kit --skill judge-with-debate -a claude-code
Open on GitHub

What judge-with-debate does

The skill implements the Multi-Agent Debate pattern. A meta-judge runs once and writes an evaluation specification: rubrics, checklists and a scoring scale. Then three judges analyse the solution in parallel, each on their own, and save reports to .specs/reports/{solution-name}-{YYYY-MM-DD}.[1|2|3].md.

Debate rounds follow, up to three of them. Each judge reads the other reports, looks for score gaps wider than one point on any criterion, defends their rating with evidence from the solution and the specification, and revises when the counter-arguments hold. Judges talk only through the filesystem — the orchestrator stays out of it, otherwise its context overflows.

The reports directory .specs/reports has to exist before the run; the skill creates it with mkdir -p .specs/reports. Both the meta-judge and the judges run on Opus, so expect a heavier bill than a plain review. On a small file the debate mostly adds latency.

What it helps with

  • score a solution against a rubric instead of a gut call
  • cut the bias that comes with one reviewer
  • surface the disputed criteria and both sides of the argument
  • get a report with per-criterion scores and quotes from the code
  • compare several solutions against one specification

Example prompts for the agent

  • evaluate src/api/users.ts with judge-with-debate
  • run the judge debate on this module and show where they disagree
  • do a multi-agent debate on this file and save the reports to .specs/reports

How to install judge-with-debate

1Skills CLI (Vercel)

npx skills add NeoLabHQ/context-engineering-kit --skill judge-with-debate -a claude-code

2Manually: put the files in place

~/.claude/skills/judge-with-debate/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/judge-with-debate/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about judge-with-debate

How do I install judge-with-debate in Claude?

Run npx skills add NeoLabHQ/context-engineering-kit --skill judge-with-debate -a claude-code. The skill file then lands at ~/.claude/skills/judge-with-debate/SKILL.md.

What does judge-with-debate do?

It puts a solution through three independent judges, then through debate rounds until consensus or three rounds are up. You get reports with per-criterion scores and the reasoning behind them.

Does the skill need anything set up first?

The .specs/reports directory must exist before the run, and the skill creates it itself. The meta-judge and the judges run on Opus.

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set55

prompt-engineering Guides prompt design for agents, subagents, and LLM integrations. Helpful when building production templates, chain-of-thought prompts, or agent hooks. CX Codex +1 1,400installs agent-evaluation Framework for testing agents, prompts, and skills using multi-dimensional scoring rubrics and LLM-as-judge prompts. CX Codex +1 1,300installs memorize Transfers insights from agent reflections and critique sessions into CLAUDE.md. Keeps your context file sharp by structuring lessons instead of bloating it with raw logs. CX Codex +1 1,300installs subagent-driven-development Runs an implementation plan through fresh subagents and puts code review between tasks, so context stays clean and issues surface early. CX Codex +1 1,300installs update-docs Updates project documentation based on uncommitted git changes or the latest commit. Keeps README files, docs/, and JSDoc comments synchronized with your codebase. CX Codex +1 1,300installs root-cause-tracing A skill that walks the agent backward through the call stack until it finds the original trigger, then fixes there instead of at the crash site. CX Codex +1 1,300installs critique The critique skill runs finished work past several AI judges: they review it independently, debate their findings, and agree on a shared list of issues. CX Codex +1 1,300installs brainstorm Turns rough project ideas into detailed specifications through guided dialogue. It compares six architectural options before any code or implementation planning begins. CX Codex +1 1,300installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor