eval-driven-development

Gate prompt and model changes using offline evaluation suites with pass-rate signals.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill eval-driven-development-jacob-balslev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-driven-development
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/eval-driven-development
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill eval-driven-development-jacob-balslev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of shipping LLM-integrated systems without reliable, representative measurement of quality, so teams can’t confidently tell whether changes truly improve outcomes versus just improving scores on a small set of examples.

Core Features & Use Cases

  • Eval-first iteration discipline: run an offline eval suite and use aggregated pass-rate (and related metrics) to gate prompt, model, retrieval, scaffolding, and tooling changes.
  • Correct treatment of stochastic judgment: supports programmatic, model-graded, human-graded, and hybrid evaluation mechanisms while accounting for statistical (not binary) results.
  • Anti-Goodhart safeguards: designs for regression budgets, held-out sets, calibration, and multi-metric reporting to reduce overfitting to the eval target.
  • Benchmark grounding without false authority: cites public benchmarks (e.g., MMLU, HumanEval, BIG-bench, GAIA, MT-Bench) for context and selection, while emphasizing system-specific eval suites for gating.

Quick Start

Use eval-driven-development to design and apply an offline evaluation suite that determines whether a proposed prompt or model change should be merged based on a predefined regression budget.

Frequently Asked Questions about eval-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use offline evals to gate LLM prompt changes?

Gate LLM prompt changes by running an offline eval suite that measures aggregated pass-rates against a representative dataset, ensuring proposed iterations meet a predefined regression budget before merging. This approach applies to prompt, model, retrieval, and scaffolding changes.

What is a regression budget in LLM evaluation?

A regression budget in LLM evaluation defines the acceptable threshold of metric drop when iterating on stochastic model outputs. It works with held-out sets and multi-metric reporting to prevent overfitting and mitigate Goodharting during prompt or model updates.

How do model-graded evaluations work for stochastic LLM outputs?

Model-graded evaluations use a language model to judge stochastic LLM outputs against defined criteria, functioning as one of several judgment mechanisms including programmatic, human-graded, and hybrid approaches to account for statistical rather than binary results.

When should I use human calibration in offline LLM evaluation suites?

Use human calibration in offline LLM evaluation suites when validating automated or model-graded judgment mechanisms, ensuring the aggregated pass-rate signals accurately reflect system quality and reducing the risk of Goodharting through periodic refresh cycles.

Can I use public benchmarks like MMLU or HumanEval to gate LLM system changes?

Public benchmarks like MMLU, HumanEval, BIG-bench, GAIA, and MT-Bench provide context and selection grounding, but system-specific offline eval suites with representative datasets and regression budgets are required to reliably gate changes for your LLM-integrated system.

What are the best ways to prevent Goodharting when iterating on LLM systems?

Prevent Goodharting when iterating on LLM systems by applying anti-Goodhart safeguards: maintain held-out datasets, enforce regression budgets, implement calibration cycles, and use multi-metric reporting to avoid overfitting to the evaluation target.