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
- robertn702/reasoning-routertheir own version, first seen Nov 16, 2026
- stellar-experimental/stellar-raventheir own version, first seen Nov 15, 2026
- PyLops/pylops-agent-skillstheir own version, first seen Nov 1, 2026
- google/skills_lint.darttheir own version, first seen Oct 30, 2026
- lycorp-jp/sim-usetheir own version, first seen Oct 21, 2026
- on-par/software-factorytheir own version, first seen Oct 20, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- lycorp-jp/sim-use★ 1.5ksame name
- Azure/azure-sdk-tools★ 134same name
- BariBariGood/manzanas★ 22same name
- stellar-experimental/stellar-raven★ 17same name
- google/skills_lint.dart★ 8same name
- on-par/software-factory★ 6same name
- robertn702/reasoning-router★ 4same name
- PyLops/pylops-agent-skills★ 1same name
- rmatx/multi-agent-cs-crew★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository162 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- website/AGENTS.mdAGENTS.md
- .cursor/rules/align-grid.mdcCursor rule
- .cursor/rules/assess-impact.mdcCursor rule
- .cursor/rules/audit-code.mdcCursor rule
- .cursor/rules/audit-plan.mdcCursor rule
- .cursor/rules/build-epic.mdcCursor rule
- .cursor/rules/change-request.mdcCursor rule
- .cursor/rules/commit-message.mdcCursor rule
- .cursor/rules/compose-workflow.mdcCursor rule
- .cursor/rules/craft-skill.mdcCursor rule
- .cursor/rules/deepen-architecture.mdcCursor rule
- .cursor/rules/define-language.mdcCursor rule
- .cursor/rules/define-success.mdcCursor rule
- .cursor/rules/delegate-task.mdcCursor rule
- .cursor/rules/deploy.mdcCursor rule
- .cursor/rules/design-interface.mdcCursor rule
- .cursor/rules/develop-tdd.mdcCursor rule
- .cursor/rules/diagnose-root.mdcCursor rule
- .cursor/rules/diagnose-stall.mdcCursor rule
- .cursor/rules/dispatch-agents.mdcCursor rule
- .cursor/rules/edit-document.mdcCursor rule
- .cursor/rules/elaborate-spec.mdcCursor rule
- .cursor/rules/enforce-first.mdcCursor rule
- .cursor/rules/evolve-skill.mdcCursor rule
- .cursor/rules/execute-plan.mdcCursor rule
- .cursor/rules/extract-design.mdcCursor rule
- .cursor/rules/find-way.mdcCursor rule
- .cursor/rules/fix-bug.mdcCursor rule
- .cursor/rules/gate-trace.mdcCursor rule
- .cursor/rules/generate-allure-report.mdcCursor rule
- .cursor/rules/grill-me.mdcCursor rule
- .cursor/rules/grill-with-docs.mdcCursor rule
- .cursor/rules/guard-git.mdcCursor rule
- .cursor/rules/harden-vps.mdcCursor rule
- .cursor/rules/hook-commits.mdcCursor rule
- .cursor/rules/inspect-quality.mdcCursor rule
- .cursor/rules/investigate-bug.mdcCursor rule
- .cursor/rules/kickoff-branch.mdcCursor rule
- .cursor/rules/maintain-wiki.mdcCursor rule
- .cursor/rules/map-codebase.mdcCursor rule
- .cursor/rules/migrate-spec.mdcCursor rule
- .cursor/rules/model-domain.mdcCursor rule
- .cursor/rules/orchestrate-project.mdcCursor rule
- .cursor/rules/organize-workspace.mdcCursor rule
- .cursor/rules/plan-refactor.mdcCursor rule
- .cursor/rules/plan-release.mdcCursor rule
- .cursor/rules/plan-tests.mdcCursor rule
- .cursor/rules/plan-work.mdcCursor rule
- .cursor/rules/publish-package.mdcCursor rule
- .cursor/rules/quick-fix.mdcCursor rule
- .cursor/rules/release-branch.mdcCursor rule
- .cursor/rules/request-review.mdcCursor rule
- .cursor/rules/research-first.mdcCursor rule
- .cursor/rules/reset-baseline.mdcCursor rule
- .cursor/rules/respond-review.mdcCursor rule
- .cursor/rules/run-benchmark.mdcCursor rule
- .cursor/rules/run-evals.mdcCursor rule
- .cursor/rules/run-planning.mdcCursor rule
- The first 60 shown.
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
- Distinctive: line 30
Run evals; log results table with pass@k (e.g.
“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.
Files
Run Evals
HARD GATE — Define evals before implementation. Code graders = runnable
verify:commands; model graders = explicit rubric with pass/fail criteria.
Process
- Name the capability under test (one sentence).
- Write
specs/EVALS-<feature>.mdwith:- Capability evals (does it do the job?)
- Regression evals (did we break anything?)
- Assign grader type per eval:
code(shell verify) ormodel(rubric). Assign strictness tier per eval (graduated promotion — e45s37):
Tier Meaning Promotion rule EXPERIMENTALNew eval, may flake Not gating USUALLY_PASSESStable in dev; ≥2/3 recent runs pass Blocks BUILD only when combined with ALWAYS_PASSES suite ALWAYS_PASSESZero tolerance; required for release Any single failure blocks BUILD and merge Promote:
EXPERIMENTAL → USUALLY_PASSESafter 3 consecutive passes;USUALLY_PASSES → ALWAYS_PASSESafter 5 consecutive passes with zero flakes documented inspecs/state.yaml.- Run evals; log results table with pass@k (e.g. 3/3 runs) and tier per eval.
- Block BUILD phase until all
ALWAYS_PASSESevals pass at agreed k.USUALLY_PASSESfailures warn;EXPERIMENTALfailures 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 -->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
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.

