experiment-workflow
Skill8 starsChanged 9 days agoMITView on GitHub
Use when designing, running, or comparing a repeatable experiment where a decision question, controlled variables, baselines, measurements, and raw evidence matter. Not for ordinary unit tests or one-off checks.
In this repository17 other files it gives its agents.
- app-controlSkill
- artifactSkill
- clean-systemSkill
- contribution-checklistSkill
- debuggingSkill
- doc-styleSkill
- first-principlesSkill
- latex-authoringSkill
- logoSkill
- multi-agentSkill
- product-designSkill
- project-docsSkill
- reference-driven-productSkill
- specSkill
- tddSkill
- test-auditSkill
- word-farsi-docxSkill
The file
Files
Experiment workflow
One stated question at a time, with enough evidence for someone else to rerun it and judge the conclusion.
- Decision. State the decision the experiment informs and the result that would change it. One precise question; say what it cannot establish.
- Variables. Name the independent variable, outcomes, fixed conditions, baseline and known confounders. Change one variable at a time when you claim a cause; if several must move together, call it a comparison.
- Setup. Record exact inputs, versions, configuration, hardware, seeds and preprocessing; keep them fixed unless one is the variable.
- Measures, set before running. Units, method, pass threshold, repetitions, aggregation, and how failures and outliers count. Use the smallest sample that answers honestly; claim no certainty the design cannot carry.
- Run and keep evidence. Commands, raw outputs, failures and deviations, with baseline and variant side by side.
- Judge. Separate observation from interpretation, compare against the threshold, state uncertainty and the decision the evidence supports. This run is the next one's baseline.
For retrieval or RAG, keep the query set, retrieved passages, ranks, latency, chunking settings and corpus identity. A semantic/keyword/hybrid query suite is one useful stress test, sized to the corpus (about 10 of each type for a medium-to-large one).
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.

