judge — Claude Code skill: evaluation and installation
The skill runs a two-stage review of work from the current conversation: one sub-agent sets the criteria, another scores the result with evidence.
npx skills add NeoLabHQ/context-engineering-kit --skill judge -a claude-codeWhat judge does
judge extracts the task, produced result, involved files, and acceptance criteria from the current conversation. It then runs two stages: a meta-judge prepares a tailored review rubric, while a judge sub-agent applies it in a separate context. This keeps the assessment apart from the session state built up earlier.
The review uses structured scores, checklists, and evidence tied to concrete work locations, including files and lines. The skill returns findings without changing the project automatically. You still need to handle any fixes yourself.
What it helps with
- review code after an implementation task
- create criteria for checking documentation
- verify a result against files and line references
- get a structured sub-agent report
- spot gaps between a score and its reasoning
Example prompts for the agent
- Evaluate the result of the current coding task and cite evidence from the files.
- Review the documentation: create the criteria first, then run a separate judgment.
- Produce a quality report for the changed files without applying automatic fixes.
How to install judge
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill judge -a claude-code2Manually: put the files in place
~/.claude/skills/judge/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/judge/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill judge -a codex2Manually: put the files in place
.agents/skills/judge/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill judge -a cursor2Manually: put the files in place
.cursor/skills/judge/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NeoLabHQ/context-engineering-kit judge2Manually: put the files in place
.github/skills/judge/SKILL.md1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill judge -a gemini-cli2Platform CLI
gemini skills install https://github.com/NeoLabHQ/context-engineering-kit --path skills/judgeManually: put the files in place
.devin/skills/judge/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill judge -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about judge
How do I install judge in Claude Code?
Run npx skills add NeoLabHQ/context-engineering-kit --skill judge -a claude-code, run npx skills add NeoLabHQ/context-engineering-kit --skill judge -a claude-code again, then check ~/.claude/skills/judge/SKILL.md.
What does judge do?
The skill extracts work from the current conversation, asks a meta-judge to define review criteria, and sends those criteria to a judge sub-agent working in a separate context. It returns a report without applying changes automatically.
Why does judge use two review stages?
The first stage creates criteria for the specific artifact and review focus. The second stage evaluates the work against those criteria and supports scores with evidence from files and lines.