model-eval-design
Skill0 starsChanged 13 days agoMITView on GitHub
Build an evaluation plan that measures a model capability rather than a single attractive example. Use when comparing base and fine-tuned models, reasoning systems, prompts, or agent workflows.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-skill-auditSkill
- api-contract-checkSkill
- build-rescueSkill
- change-narrativeSkill
- context-handoffSkill
- data-quality-gateSkill
- dataset-workshopSkill
- dependency-careSkill
- docs-syncSkill
- experiment-ledgerSkill
- failure-forensicsSkill
- model-diff-reviewSkill
- multi-agent-crosscheckSkill
- parallel-task-designSkill
- performance-proofSkill
- release-readinessSkill
- repo-scoutSkill
- research-evidence-mapSkill
- review-lensSkill
- safe-migrationSkill
- security-surfaceSkill
- spec-firstSkill
- sql-integrity-checkSkill
- test-driven-changeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 11
Create a locked evaluation set with explicit inclusion rules, source provenance, and a clear split from training and prompt-tuning examples.
- Distinctive: line 15
Use deterministic execution where possible.
- Distinctive: line 17
Keep the test set fixed for final comparison.
- Distinctive: line 23
Do not claim a broad capability from a tiny or unrepresentative benchmark.
- Distinctive: line 24
Do not treat model self-judgment as an unbiased ground truth without validation.
- Distinctive: line 25
If scoring rules or test samples changed, mark results as not directly comparable.
≈ “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
Model Evaluation Design
Procedure
- Define the capability and failure modes in plain language. Make success measurable and relevant to actual users.
- Create a locked evaluation set with explicit inclusion rules, source provenance, and a clear split from training and prompt-tuning examples.
- Establish a baseline using the same inference settings, tokenizer/template, context length, tool permissions, and retry policy.
- Select metrics that match the task: exact match, normalized answer accuracy, structured-output validity, calibration, pass@k, latency, tool-use success, or human rubric scores. Define normalization carefully.
- Include easy, typical, boundary, adversarial, out-of-domain, and refusal/safety cases where relevant.
- Use deterministic execution where possible. For stochastic models, specify sampling settings and repeat counts; report variability rather than cherry-picking runs.
- Inspect error categories and examples, not only an aggregate score. Check whether gains are concentrated in one slice or come from leaking expected answers.
- Keep the test set fixed for final comparison. Use a separate development set for iteration.
Report
Dataset/version, sample size, metric definitions, baseline, candidate, per-slice results, confidence/variance, qualitative error analysis, cost/latency, and limitations.
Boundaries
- Do not claim a broad capability from a tiny or unrepresentative benchmark.
- Do not treat model self-judgment as an unbiased ground truth without validation.
- If scoring rules or test samples changed, mark results as not directly comparable.
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.

