eval-driven-dev

Define and run capability and regression evals to measure AI workflow quality.

Updated May 22, 2026
One-click install
npx skills add https://github.com/kitfunso/claude-config --skill eval-driven-dev-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval-driven-dev
Source: https://github.com/kitfunso/claude-config/tree/main/skills/eval-driven-dev
Command: npx skills add https://github.com/kitfunso/claude-config --skill eval-driven-dev-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI features, agent pipelines, and prompts are hard to verify objectively, so teams ship changes without knowing whether quality improved or regressed. This Skill provides a structured method to define success criteria before implementation and measure pass rates after. ## Core Features & Use Cases - Capability Evals: Define objectively verifiable success criteria for new AI features before writing any code. - Regression Evals: Track existing behavior as PASS/FAIL checks to detect breakage from changes. - Grader Selection: Choose between code-based, model-based, or human-based grading depending on output determinism. - Use Case: When tuning a prompt for an agent pipeline, define a capability eval with three verifiable criteria, implement the change, then have a separate grading context score pass@3 against the 90% target before reporting results. ## Quick Start Define a capability eval with three objective success criteria for my new prompt, then grade the results in a separate context.

Frequently Asked Questions about eval-driven-dev

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

FAQPage Schema
How do I write evals for AI prompts and agent pipelines?▼

Define a capability eval before coding by listing objectively verifiable success criteria, then implement the feature and run the evals to collect pass rates. Iterate on failures and report final pass rates with the change.

What is the difference between capability evals and regression evals?▼

Capability evals verify that a new feature works against defined success criteria. Regression evals check that existing behavior still passes after a change, tracking prior tests as PASS or FAIL.

When should I use code-based vs model-based grading for AI evals?▼

Use code-based grading for deterministic outputs via grep patterns, test runs, build checks, or file existence. Use model-based grading for open-ended outputs, where a model scores against a rubric in a separate context.

What do pass@k and pass^k metrics mean in AI evaluation?▼

pass@k measures whether at least one of k attempts succeeds, with a target of pass@3 above 90%. pass^k requires all k trials to succeed, setting a higher bar for critical paths.

Why should the grader be separate from the implementer in eval workflows?▼

Author bias causes implementers to rate their own work too favorably. Grading in a separate context or subagent produces more objective scores against the rubric.