agentleFS
danielvm-gitdanielvm-git/bigpowers/skills/run-evals/SKILL.md

run-evals

Skill292 starsChanged 11 days agoMITView on GitHub

Eval-Driven Development — define capability and regression evals before building; code graders use verify commands, model graders use explicit rubrics; log pass@k. Use before develop-tdd on new features, or when measuring agent capability over runs.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run evals; log results table with pass@k (e.g.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run Evals

HARD GATE — Define evals before implementation. Code graders = runnable verify: commands; model graders = explicit rubric with pass/fail criteria.

Process

  1. Name the capability under test (one sentence).
  2. Write specs/EVALS-<feature>.md with:
    • Capability evals (does it do the job?)
    • Regression evals (did we break anything?)
  3. Assign grader type per eval: code (shell verify) or model (rubric).
  4. Assign strictness tier per eval (graduated promotion — e45s37):

    TierMeaningPromotion rule
    EXPERIMENTALNew eval, may flakeNot gating
    USUALLY_PASSESStable in dev; ≥2/3 recent runs passBlocks BUILD only when combined with ALWAYS_PASSES suite
    ALWAYS_PASSESZero tolerance; required for releaseAny single failure blocks BUILD and merge

    Promote: EXPERIMENTAL → USUALLY_PASSES after 3 consecutive passes; USUALLY_PASSES → ALWAYS_PASSES after 5 consecutive passes with zero flakes documented in specs/state.yaml.

  5. Run evals; log results table with pass@k (e.g. 3/3 runs) and tier per eval.
  6. Block BUILD phase until all ALWAYS_PASSES evals pass at agreed k. USUALLY_PASSES failures warn; EXPERIMENTAL failures log only.

Artefact

specs/verifications/eNNsYY-eval-report.md — see REFERENCE.md for template. Eval reports are stored alongside verification evidence in specs/verifications/, keyed by story ID for traceability.

Verify

→ verify: test -d specs/benchmarks && test -f specs/benchmarks/SCHEMA.md

<!-- story: e02s01 -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.