agentleFS
robusta-devrobusta-dev/holmesgpt/.claude/skills/benchmark-judge/SKILL.md

benchmark-judge

Skill3.7k starsChanged 8 months agoApache-2.0View on GitHub

This skill should be used when the user asks to "benchmark the judge", "compare LLM judges", "pick a new classifier model", "replace the eval judge", or wants to know how accurate, fast and cheap a candidate CLASSIFIER_MODEL is on real eval outputs.

  • Reads credentials

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Disputed cases: read each prompt (EXPECTED ELEMENTS and OUTPUT) and decide A (all elements present) or B yourself, following the prompt's …

    line 28
  2. Very specific:

    Write every verdict to a labels file, {"<case id>": "A" | "B"}, with the case ids from disputed.json / cases.json.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Benchmarking LLM Judges

Goal: pick the eval judge (CLASSIFIER_MODEL) that is most correct, then fastest and cheapest. Every judge, including the current gpt-4.1, can be wrong, so ground truth comes from consensus plus your own adjudication, never from one judge.

Step 1: Replay a benchmark's judge prompts

Pick the latest benchmark with the most iterations from docs/development/evaluations/history/ (its Braintrust links name the ci-benchmark-<run_id> experiment).

# Judges are model_list names, e.g. the CI secret MODEL_LIST_YAML
export MODEL_LIST_FILE_LOCATION=/path/to/model_list.yaml
poetry run python .claude/skills/benchmark-judge/benchmark_judge.py <run_id> \
  --judges haiku-5.5-medium,gpt-6.1-sol-medium,deepseek-v4-pro,opus-5.5-medium

The script sends each candidate the exact prompt the CI judge received (stored on the scorer span in Braintrust), and records the CI verdict as gpt-4.1-ci. Results go to /tmp/benchmark-judge/<run_id>/<judge>.jsonl; reruns only replay missing or failed prompts. Requires BRAINTRUST_API_KEY.

Step 2: Build the ground truth

A case where every judge agrees is taken as truth; the rest are written to disputed.json.

  • Disputed cases: read each prompt (EXPECTED ELEMENTS and OUTPUT) and decide A (all elements present) or B yourself, following the prompt's rules. Do not side with the majority or with gpt-4.1-ci; the judges' reasons are hints, not evidence.
  • Unanimous cases: also review every unanimous B and a random sample of 20 unanimous A, since all judges can share a mistake.

Write every verdict to a labels file, {"<case id>": "A" | "B"}, with the case ids from disputed.json / cases.json.

Step 3: Report

poetry run python .claude/skills/benchmark-judge/benchmark_judge.py <run_id> --labels labels.json

Present the accuracy, cost and latency tables (same shape as the benchmark reports) and recommend a judge: lowest FP + FN first (a false pass hides a real regression, so weigh FP above FN), then p95 latency and total cost. Quote one disputed case each judge got wrong to show the failure mode.

To switch judges, set CLASSIFIER_MODEL (vars.CLASSIFIER_MODEL in .github/workflows/eval-regression.yaml). The classifier calls the OpenAI SDK directly, so the new judge needs an OpenAI-compatible endpoint (see tests/llm/utils/classifiers.py).

Download now (ZIP)

Trending

Steady talk.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 2 mentionsMar 2026: 3 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the robusta-dev/holmesgpt repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about robusta-dev/holmesgpt

The biggest 5 of 55 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 55

Talked about on GitHub, Hacker News and Bluesky (55 times).

On GitHub · 50

45 more on GitHub
  • Other versions1 project uses a version of this.

    Word for word · 1

    1. HolmesGPT/holmesgpt★ 3.7k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.