eval-harness

Define and run eval-driven development tests measuring Claude Code task reliability with pass@k metrics.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Femad-6/my-skills --skill eval-harness-femad-6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-harness
Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/eval-harness
Command: npx skills add https://github.com/Femad-6/my-skills --skill eval-harness-femad-6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding lacks objective quality gates, making it hard to know whether an agent's output actually works or whether a prompt change broke existing behavior. This Skill provides a formal evaluation framework that treats evals as unit tests for AI development, so you can define pass/fail criteria before coding and measure reliability with pass@k metrics. ## Core Features & Use Cases - Capability and Regression Evals: Define structured eval templates that verify new functionality works and existing behavior stays intact across changes. - Multiple Grader Types: Use deterministic code graders (grep, test runners, builds), model-based LLM-as-judge rubrics, or human review flags for security-sensitive changes. - Reliability Metrics: Track pass@1, pass@3, and pass^3 metrics with recommended thresholds (pass@3 >= 0.90 for capability, pass^3 = 1.00 for release-critical paths). - Use Case: Before adding authentication to your app, define capability evals (user registration, login, session persistence) and regression evals (public routes still work), then run evals after implementation and generate a report showing 5/5 capability and 3/3 regression passes. ## Quick Start Ask the agent to define an eval for a feature you are about to build, including capability evals, regression evals, and pass@k success thresholds stored under .claude/evals/.

Frequently Asked Questions about eval-harness

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

FAQPage Schema
How do I set up eval-driven development for AI coding agents?

Define capability and regression evals before writing code, specifying success criteria for each. Store definitions in .claude/evals/<feature>.md, implement the feature, then run the evals and generate a report with pass@k metrics.

What is the difference between pass@k and pass^k metrics?

pass@k measures whether at least one of k attempts succeeds, indicating practical reliability under retries. pass^k requires all k attempts to succeed, making it a stricter stability test suited for release-critical regression paths.

When should I use a code grader versus a model grader?

Use code graders for deterministic checks like grep patterns, test runs, and build success since they are reproducible. Use model graders (LLM-as-judge) for open-ended quality assessments like code structure and edge-case handling, and human graders for security-sensitive changes.

What pass rate thresholds should AI agent evals meet before release?

The recommended thresholds are pass@3 >= 0.90 for capability evals and pass^3 = 1.00 for regression evals on release-critical paths. These ensure new features work reliably under retries while existing behavior never breaks.

What are common eval anti-patterns to avoid?

Avoid overfitting prompts to known eval examples, measuring only happy-path outputs, ignoring cost and latency drift, and allowing flaky graders in release gates. Keep evals fast and version them alongside code as first-class artifacts.