eval-sweep

Runs adaptive variant sweeps on atomic skills with statistical verdicts and provenance-checked scoring.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/ensj/skill-eval-framework --skill eval-sweep-ensj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval-sweep
Source: https://github.com/ensj/skill-eval-framework/tree/main/.claude/skills/eval-sweep
Command: npx skills add https://github.com/ensj/skill-eval-framework --skill eval-sweep-ensj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining whether one prompt variant of a skill actually outperforms another requires more than a few ad-hoc runs; this Skill runs a rigorous Layer-1 variant sweep that scores variants across cases and seed batches until a statistical rule decides a real winner, tie, or inconclusive outcome. ## Core Features & Use Cases - Adaptive seed rounds: Automatically adds seed batches until a precision-width rule decides, capped by n_max, so you stop spending budget once the answer is statistically clear. - Four-state verdicts: Produces winner, tie, inconclusive_saturated, or underpowered outcomes with bootstrap confidence intervals, so you know whether to ship, harden the eval, or raise the budget. - Provenance-gated scoring: Reconciles relayed scores against disk via a reconcile CLI before writing any winner.json or ledger rows, preventing corrupted results from being recorded. - Use Case: You have three prompt variants of a claim-verification skill and want to know which to ship. Run the sweep to get a leaderboard, a blinded LLM-judge comparison, and a durable winner.json only if the difference is statistically real. ## Quick Start Run an eval sweep on the claim-verify skill with default settings and show me the verdict.

Frequently Asked Questions about eval-sweep

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

FAQPage Schema
How do I run an A/B test on prompt variants?▼

Run the eval-sweep skill against the skill's directory containing variants/*.md files and evals/ cases. It scores each variant across seed batches adaptively and declares a winner only when the bootstrap confidence interval excludes zero.

How to measure which prompt variant performs best statistically?▼

Use a variant sweep with adaptive seed rounds and sequential alpha-spending. The sweep keeps adding seed batches until a precision-width rule decides, producing a four-state verdict: winner, tie, inconclusive_saturated, or underpowered.

What does an inconclusive_saturated verdict mean in an eval sweep?▼

It means zero discriminating cases exist because all cases hit the score ceiling or floor, so the eval cannot distinguish variants. The fix is to harden the eval cases and re-run the sweep rather than picking a variant.

Why does the eval sweep fail at the reconcile step?▼

The reconcile CLI exits 1 when relayed scores cannot be reproduced from disk, indicating a provenance mismatch. In that case no winner.json or ledger rows are written; inspect the mismatch list and re-run after fixing the underlying scoring issue.

When should I raise n_max or the token budget in a sweep?▼

Raise them when the verdict comes back underpowered, meaning the budget or n_max was exhausted before the statistical rule could decide. A larger budget lets the adaptive loop add enough seed batches to reach a conclusive outcome.