design-resumable-model-evaluation
Skill7 starsChanged 10 months agoMITView on GitHub
Designs strict model benchmarks that persist per-case evidence, resume without repeating completed work, separate first-attempt behavior from remediation, and stop early only when failure is mathematically certain. Use for slow, costly, or interruptible evaluations.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apple-cktool-jsSkill
- apple-cktoolSkill
- audit-training-experimentSkill
- awkSkill
- close-out-ml-experimentSkill
- compare-models-blindlySkill
- conventional-commitsSkill
- gogopowermanagerSkill
- ios-design-reviewSkill
- mikrotik-routerosSkill
- obsidian-dailySkill
- orbstack-cliSkill
- package-private-ml-artifactsSkill
- prepare-training-corpusSkill
- proxmox-adminSkill
- review-ios-ui-apple-higSkill
- review-training-data-qualitySkill
- run-hugging-face-training-smokeSkill
- sedSkill
- select-and-verify-best-checkpointSkill
- send-to-minionSkill
- swift-reviewSkill
- technical-writerSkill
- tmuxinatorSkill
- topydoSkill
- unhobble-agent-contextSkill
- validate-structured-model-outputSkill
- write-a-promptSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 12
Create a unique revision for every combination of corpus membership, model, prompt/instructions, schema, decoder settings, validator, run …
- Distinctive: line 14
Write the case manifest before inference.
- Distinctive: line 18
Use an append-only result stream or atomically replace a small state file after every case/run.
- Distinctive: line 25
start/end timestamps and latency.
- Distinctive: line 34
Keep required run counts and thresholds unchanged.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design Resumable Model Evaluation
Make interruption cheap and evidence comparable.
Freeze an evaluation revision
Create a unique revision for every combination of corpus membership, model, prompt/instructions, schema, decoder settings, validator, run count, and thresholds. Hash this configuration into the state file. Never seed a new revision from incompatible results.
Write the case manifest before inference. Select cases from stable metadata, not previous outcomes.
Persist atomically
Use an append-only result stream or atomically replace a small state file after every case/run. Store:
- case and run IDs;
- frozen configuration hash;
- raw and normalized output;
- parse, identifier, semantic, execution, and safety gate results;
- abstention and generation-failure status;
- start/end timestamps and latency;
- interruption and retry metadata.
On resume, validate the configuration hash, scan completed keys, and execute only missing (case, run) pairs. Deduplicate safely if a crash occurred after writing output but before updating summary state.
Preserve benchmark semantics
Evaluate first-attempt output with exactly one generation when that is the product question. Do not call production remediation, repair malformed JSON, or deterministically choose a fallback. Exercise remediation in a separate test and metric series.
Keep required run counts and thresholds unchanged. A resumable evaluator improves execution efficiency, not acceptance criteria.
Stop only on safe math
For a minimum rate t over N required trials, fail early only when even winning every remaining trial cannot reach the required successes:
successes + remaining < ceil(t * N)
For maximum-failure gates, stop only once the allowed failure count is irreversibly exceeded. Apply the same reasoning separately to each gate and subgroup. Do not early-pass unless all required trials are complete.
Report
Report completed and required runs, completed fixtures/cases, failures, abstentions, gate numerators and denominators, distribution/diversity gates, p50/p95 latency, interruptions, resumptions, and exact automated gate results. State which human, device, energy, usefulness, or product gates remain untested.
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.

