Skip to main content
Score agent responses against your own criteria — recipe quality, data pipelines, manufacturing checks, or any custom rubric.
The user runs the agent; the judge scores the final output against your custom criteria and returns a score with reasoning.

How It Works

Quick Start

1

Simple criteria

2

Domain-specific config

3

CLI recipe optimisation


Configuration Options

JudgeCriteriaConfig

JudgeConfig


Custom Optimisation Rules

Register domain-specific fix patterns with add_optimization_rule:

Best Practices

Vague rubrics like “good output” produce inconsistent scores. Use specific, testable dimensions.
Use 8–9 for production-critical checks; 6–7 for exploratory workflows.
Run the judge on good and bad examples before wiring it into optimisation loops.
Break evaluation into dimensions for clearer feedback and targeted fixes.

CLI Eval

Run evaluations from the command line

Evaluator Optimiser

Optimise agents with evaluator feedback loops