AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Judge Panel

skill-tylerjnewman-skills-judge-panel · by TylerJNewman

Build and calibrate a multi-judge evaluator, then prove it agrees with held-out human labels before trusting it as a JUDGE. Use when an optimization target needs human-like judgment, when promoting an amber candidate toward a loop, or when another skill needs a trusted scoring panel.

No reviews yet
0 installs
24 views
0.0% view→install

Install

$ agentstack add skill-tylerjnewman-skills-judge-panel

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-tylerjnewman-skills-judge-panel)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Judge Panel? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

A panel is a JUDGE only after it agrees with human labels above a stated threshold. Until then it is a vibe with a quorum — three judges sharing one blind spot still vote wrong together. The conserved quantity is agreement: a measured false-negative and false-positive rate against ground truth, not the confidence of the votes.

The payoff: a calibrated panel converts an amber target — one blocked only because scoring needs judgment — into a loop-able one. This is the promotion mechanism, and it is reusable for any eval, not just autoresearch.

Procedure

  1. Write the rubric. Decompose the judgment into binary or low-cardinality sub-criteria, each with a pass/fail rule a stranger could apply. Binary failure modes beat a 1–10 score; a number that means something different to each judge cannot be aggregated.

Done when: every sub-criterion has an explicit pass/fail rule.

  1. Assemble the panel. At least three judges scoring independently, varied by prompt or model so their errors are not identical. State the aggregation rule: majority for throughput, minimum when a false pass is the costly error (anything safety- or compliance-adjacent), a quantile in between.

Done when: panel size, judge diversity, and aggregation rule are named.

  1. Calibrate against held-out human labels. Score a labeled held-out set the panel has never seen. Measure agreement: the false-negative rate (panel fails what humans pass) starves the loop; the false-positive rate (panel passes what humans fail) feeds reward hacking. The panel passes only if both clear threshold.

Done when: FN and FP rates are measured against ground truth and compared to a stated threshold.

  1. Seal the set and freeze the panel. Hold the calibration set out of every optimizer forever. Then freeze what was measured: model, prompt, rubric, temperature, fixtures, parser. An agreement receipt is only valid for the exact panel that earned it — change any of these and the receipt expires; recalibrate. State the correlated-error risk — where all judges likely share a weakness — and route it to the contract's guard metric.

Done when: the held-out set is sealed, the panel is frozen, and the shared blind spot is named.

  1. Return the verdict. ADMIT — the panel is a trusted JUDGE; hand its scoring command to frame-target. Or REJECT — agreement is below threshold; keep human and do not loop.

Done when: the verdict carries its agreement receipt.

Output contract

Rubric:        
Panel:         
Aggregation:   majority | minimum | quantile-
Agreement:     FN  / FP  vs human held-out
Threshold:     
Frozen:        
Blind spot:    
Verdict:       ADMIT (scoring command:  → frame-loop JUDGE) | REJECT (keep human)

A rejected panel is a successful result: it found that the target is not yet loop-able and stopped you from optimizing a number no one validated.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.