eval-harness

Defines and runs eval-driven development checks with pass/fail criteria and pass@k metrics.

Updated May 7, 2026
One-click install
npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill eval-harness-mirzadham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval-harness
Source: https://github.com/mirzadham/trainingroombookingsystem2/tree/main/.agent/.agents/skills/eval-harness
Command: npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill eval-harness-mirzadham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding sessions often lack objective success criteria, making it hard to know whether a change actually works or silently broke existing behavior. This Skill provides a formal evaluation framework that treats evals as unit tests for AI development, so every task has measurable pass/fail outcomes. ## Core Features & Use Cases - Capability and Regression Evals: Define what Claude should newly accomplish and verify existing functionality still passes after changes. - Multiple Grader Types: Use deterministic code-based graders (grep, npm test, build checks), model-based graders for open-ended outputs, or flag items for human review. - Reliability Metrics: Track pass@k and pass^k metrics to measure agent reliability across attempts and model versions. - Use Case: Before adding authentication to an app, define evals for registration, login, and session handling, implement the feature, then run the evals and generate a report showing 5/5 capability evals passed with pass@3 at 100%. ## Quick Start Ask the agent to define an eval-driven development checklist with pass/fail criteria for the feature you are about to implement.

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 sessions?▼

Define capability and regression evals before writing any code, listing concrete pass/fail criteria for the feature. Then implement the code, run the evals, and generate a report tracking pass@k metrics for each criterion.

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

pass@k measures whether at least one of k attempts succeeds, useful for general reliability targets like pass@3 above 90%. pass^k requires all k trials to succeed, a stricter bar used for critical regression paths.

How do I write a code-based grader for agent output?▼

Use deterministic shell checks such as grep for expected patterns, running npm test on relevant test paths, or verifying the build succeeds. Each check echoes PASS or FAIL, giving reproducible results without model judgment.

When should I use a human grader instead of automated evals?▼

Use human review for security-sensitive changes, high-risk refactors, or open-ended outputs where correctness is subjective. The framework flags these with a risk level of LOW, MEDIUM, or HIGH and never fully automates security checks.

Where are eval definitions and results stored?▼

Evals live in the project under .claude/evals/ as Markdown definition files, run history logs, and a baseline.json for regression baselines. They are versioned alongside the code as first-class artifacts.