| name | run-experiment |
| description | Set up and run a single experiment. Experiments can be arbitrary Python scripts. All experiment execution must go through this skill. |
| user-invocable | false |
Experiment setup & execution steps
- Create a new folder within your output directory for this experiment (e.g.
mkdir <OUTPUT_DIR>/experiment-<title>).
- Write a single, self-contained Python script called
script.py that runs the experiment into the experiment folder.
- The script should hard-code all parameters inside of it. It must not rely on any command-line arguments or environment variables.
- It should write all outputs (plots, csvs, logs, etc.) under its current working directory. (The wrapper will
cd into the experiment folder before executing the script).
- It is fine for the script to import and/or delegate to shared libraries and scripts that exist in the workspace, but it should not rely on any other files that only exist in the caller's temp folder, context folder, or output folder.
- Also write a
description.md file in the experiment folder. The description.md must contain a complete description of what the experiment tests, its hard-coded parameter values (if any), and what outputs it produces.
- Determine the context you're running the experiment in: Do you know the theory ID (e.g.
T_20260416_150000_a1b2c3) that this experiment is motivated by (fine if not)? You should also have been given an AGENT_TYPE.
- Execute the script through the following wrapper, passing the experiment folder and the parent theory ID if you have it:
uv run python <SKILL_BASE_DIR>/scripts/run_experiment.py --experiment_folder <EXPERIMENT_FOLDER_PATH> --agent_type <AGENT_TYPE> [--parent_theory <T_ID>]
By default, the run_experiment.py wrapper will only store results for experiments that execute successfully. To store results for failed experiments as well, add the --store_failures flag.
6. The wrapper will execute the script with CWD set to EXPERIMENT_FOLDER_PATH, passing through its stdout and stderr. It will additionally capture all experiment outputs and persist them to a database for record keeping. It will finish its output by printing a unique experiment ID (e.g. X_20260416_150000_a1b2c3) that can be used to retrieve the results later.
Some experiments may take a long time to complete (up to a few hours). Please allow enough time for the experiment to finish before assuming that it has failed.
NEVER execute your script.py directly or through any other wrapper. Always use the run_experiment.py wrapper as described above.
Experiment best practices
- Have the experiment generate plots and visualizations of the data in addition to numerical output. Inspect the visualizations to gain a better intuition when analyzing the experiment's results and to check for any potential issues with the experiment setup. The plots may also provide useful illustrations to include in your report or theory.
- It is VERY IMPORTANT to analyze experiment results rigorously by following these steps:
- After every experiment, take a moment to critically review its results. Ask: What other interpretations could there be for the results besides the hypothesis that I'm trying to support? Could I run another experiment to rule out other factors and interpretations? Avoid confirmation bias!
- Also ask: Now that I've seen the result, was the experiment set up perfectly right to provide maximum clarity? Or would I, in retrospect, prefer to re-run it with different parameters or visualizations to get an even clearer result?
- Running experiments is relatively cheap, so take the time to get them right rather than rushing to conclusions. Feel free to re-run the experiment with some adjustments until the results are 100% clear and conclusive.
