Individual skill

llm-as-judge-evaluation

Evaluate LLM outputs using frontier models as judges. Use for pairwise model comparison, quality scoring with custom rubrics, and automated evaluation pipelines. Covers position bias mitigation, statistical significance, and generating preference data for DPO/RLHF.

backend/cli/skills/llm-tools/llm-as-judge-evaluation/SKILL.md

Read pinned source

Source commit a08e0ad0ad3d6448123039ee4659163eb2e35d99

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
4,352
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# LLM-as-Judge Evaluation

## When to Use This Skill

Use LLM-as-Judge evaluation when you need to:
- **Compare a fine-tuned model vs frontier** — Does the student beat the teacher on your task?
- **Quality gates before deployment** — Automated go/no-go on model releases
- **Continuous evaluation** — Monitor production model quality over time
- **Generate preference data** — Create (chosen, rejected) pairs for DPO/RLHF training
- **Evaluate without ground truth** — When exact answers don't exist (creative, open-ended tasks)

### When NOT to Use
- Tasks with verifiable answers (math, code execution) — use exact match or unit tests
- Extremely simple classification — use accuracy/F1 directly