Skip to content

Evaluate AI coding agents & Claude Code skills — Coder Eval

Coder Eval (pip install coder-eval / uv tool install coder-eval) is an open-source framework for evaluating AI coding agents and their skills — built for CLI and skill builders — with sandboxing, reproducibility, and data-driven analysis. It is not an “agentic coding” benchmark: it measures how effective your CLI and skills are when used by coding agents such as Claude Code, Codex, and Google Antigravity (Gemini).

If you have ever asked “how do I test whether my Claude Code skill actually triggers?”, “how do I benchmark Claude Code vs. Codex on my own tasks?”, or “how do I gate CI on coding-agent quality?” — this is the framework for that.

Coder Eval running a sandboxed coding-agent evaluation from a YAML task and browsing the scored result in evalboard

  • Declarative YAML tasks with pinned dependencies and clear success criteria
  • Sandboxed execution in isolated environments with resource limits
  • Weighted, continuous scoring (0.0–1.0) with fractional credit and thresholds
  • Many criterion types — from file checks to code similarity and LLM-graded rubrics
  • Agent abstraction — Claude Code, Codex, and Antigravity (Gemini) today, extensible via a plugin SPI
  • Experiment layer — A/B agent configs (models, tools, prompts) side-by-side
  • Full telemetry — every tool call, token counts, and cost, with real-time streaming
  • Benchmark coding agents — score an agent across a suite of tasks with weighted pass/fail thresholds
  • Compare models & configs — A/B-test Claude Code vs. Codex vs. Gemini, model vs. model, tool-on vs. tool-off, prompt vs. prompt
  • Test whether a Claude Code skill triggers — verify an agent actually engages a target skill (skill_triggered) and score skill-driven suites (SkillsBench-style)
  • Keep skills fresh in CI — re-validate skills on every change or on a schedule; catch silent regressions when models, prompts, or the skills themselves drift
  • Gate CI on agent quality — run the suite in GitHub Actions and fail the build on regressions
  • Bring your own dataset — fan one task out over many rows for larger benchmark suites
Terminal window
# 1. Install the coder-eval CLI on your PATH (isolated environment)
uv tool install coder-eval
# 2. Grab the runnable example tasks
git clone https://github.com/UiPath/coder_eval.git
cd coder_eval
# 3. Credentials — optional if you're already logged in to Claude Code
# (`claude login`, reused automatically); otherwise set ANTHROPIC_API_KEY
cp .env.example .env
# 4. Validate, run, and read your first evaluation
coder-eval plan tasks/hello_date.yaml # validate (no tokens spent)
coder-eval run tasks/hello_date.yaml # run your first evaluation
coder-eval report runs/latest # view the result

Prefer Coder Eval as a project dependency instead of a CLI tool? uv add coder-eval or pip install coder-eval. Hacking on Coder Eval itself? Clone, uv sync --extra dev, and prefix commands with uv run.

New here? Start with Tutorial 01 — Your First Evaluation.

GuideWhat’s in it
TutorialsStep-by-step walkthroughs — start here
User GuideFull CLI, configuration, output, and environment-variable reference
Task Definition GuideThe task-file schema — all criterion types, scoring, templates
Claude CodeConfiguring and running the default Claude Code agent
CodexRunning the OpenAI Codex agent
Antigravity (Gemini)Running the Google Antigravity / Gemini agent
A/B ExperimentsCompare models / tools / prompts across the same tasks
Bring Your Own DatasetFan a single task out over a dataset
Dialog ModeEvaluate agents in multi-turn conversation via a simulated user
Docker IsolationThe container sandbox driver, with custom images
CI Gate & GitHub ActionRun Coder Eval as a CI gate — the packaged Action, JUnit output, score floor
Extending Coder EvalAuthor a custom agent, criterion, or model pricing via the plugin SPI
Report SchemaField-level reference for run.json / variant.json / task.json
How It Comparesvs. SWE-bench, SkillsBench, Harbor, OpenAI Evals, hand-rolled scripts
  • vs. SWE-bench and fixed benchmarks — SWE-bench is a fixed dataset; Coder Eval is a framework for authoring your own tasks in YAML, so you evaluate the skills and workflows you care about (and can still wrap a fixed dataset via Bring Your Own Dataset).
  • vs. other agent-eval frameworks (e.g. Harbor) and LLM-eval tools (OpenAI Evals) — OpenAI Evals grades model text; Harbor targets large-scale agent eval and RL optimization. Coder Eval is purpose-built for coding-agent/skill suites — weighted 0.0–1.0 file/command scoring, a skill_triggered activation check, an experiment layer for A/Bs, and evalboard. See the full comparison.
  • vs. hand-rolled scripts — reproducible sandboxes, weighted criteria, cost/token telemetry, A/B experiments, and CI-ready pass/fail gates out of the box.

See the full comparison for details.