run-experiment
This skill sets up and executes Python-based experiments within a managed environment.
Identity proven by GitHub's verified organisation badge (imbue-ai)
- Agents
- Claude Code
- License
- AGPL-3.0 (copyleft)
- Pin
- a2ee48cpinned Oct 9, 2026
- Context cost
- about 910 tokenswhen the skill loads
- GitHub stars
- 36on imbue-ai/catalyst
- Scripts
- None found
What it does
“Set up and run a single experiment. Experiments can be arbitrary Python scripts. All experiment execution must go through this skill.”
Generated summary from the skill's own text
This skill sets up and executes Python-based experiments within a managed environment. The agent creates self-contained experiment folders with a script and documentation, then runs them through a wrapper that captures outputs and assigns unique experiment IDs for later retrieval.
When to use it
- Testing hypotheses or validating theories with Python scripts
- Running data analysis or machine learning experiments
- Generating plots and numerical results for comparison
- Executing long-running computational tasks that need tracking
When not to
- Running experiments that require command-line arguments or environment variables
- Executing scripts directly without the provided wrapper
- Working with experiments that depend on temporary or caller-specific files
Install
These commands install from the publisher's repository and need no account.
skills CLI
npx skills add imbue-ai/catalyst --skill run-experimentInstalls from the repository's default branch, which may have changed since the commit we checked.
GitHub CLI 2.90 or later
gh skill install imbue-ai/catalyst run-experiment@a2ee48c34741df5d4549d97b22aa44589d9eaa6aInstalls the commit we checked (a2ee48c).
Copy by hand
Download the folder at a2ee48c and put it in .claude/skills/run-experiment for Claude Code and in .agents/skills/run-experiment for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.
Copy for your agent
A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.
Prompt
Install the agent skill "run-experiment" by Imbue. Source, pinned to commit a2ee48c34741df5d4549d97b22aa44589d9eaa6a: https://github.com/imbue-ai/catalyst/tree/a2ee48c34741df5d4549d97b22aa44589d9eaa6a/src/claude_skills/skills/run-experiment 1. Download that folder at exactly this commit. Do not use the default branch. 2. Copy every file unchanged, keeping the folder structure, into .claude/skills/run-experiment/ for Claude Code and .agents/skills/run-experiment/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist. 3. Do not edit the files, and do not run any script in the folder unless I ask you to. 4. When you are done, list the files you copied and where you put them. Listing and checks: https://www.agentnative.dev/skills/imbue/run-experiment
SKILL.md at the pin
--- 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 1. Create a new folder within your output directory for this experiment (e.g. `mkdir <OUTPUT_DIR>/experiment-<title>`). 2. 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. 3. 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. 4. 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. 5. Execute the script through the following wrapper, passing the experiment folder and the parent theory ID if you have it: ```bash 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: 1. 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! 2. 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? 3. 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.
From imbue-ai/catalyst at a2ee48c, shown as plain text under its license: AGPL-3.0 (copyleft). The license text is in LICENSE.
View SKILL.md on GitHub at a2ee48cFiles
- SKILL.md3.8 KB · 52506740fa24
1 file, 3.8 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.
Skill folder on GitHub at a2ee48cMore from Imbue
architect
Generates an architecture document for a feature by reading the existing spec, analyzing the codebase deeply, and conducting guided Q&A with the user to…
Claude Code · about 4K tokens · pinned 7 days ago
build
This skill executes a multi-step implementation plan by working through task files sequentially.
Claude Code · about 1.1K tokens · pinned 7 days ago
build-sculptor-extension
Build or modify Sculptor extensions, which are runtime ES modules that add panels, overlays, widgets, home views, or settings UI to the Sculptor frontend.
Contains scripts
Claude Code, Codex, Cursor +3 · about 3.3K tokens · pinned 7 days ago
fix-bug
Fixes bugs using test-driven development with an interactive or autonomous workflow.
Claude Code · about 9.8K tokens · pinned 7 days ago
handoff
This skill hands off ongoing work to a fresh agent, either in the same workspace or a new isolated workspace, while preserving context through a synthesized…
Claude Code · about 1.1K tokens · pinned 7 days ago
help
This skill fetches the latest Sculptor documentation from GitHub and answers user questions about how to use Sculptor's features, including workspaces…
Claude Code · about 880 tokens · pinned 7 days ago
Related in Coding workflow
final-release-review
Audits Python SDK release candidates or plans against the previous release, comparing diffs for regressions, API changes, and version compatibility.
by OpenAIOfficial publisher
Contains scripts
Claude Code, Codex, Cursor +3 · about 5.4K tokens · pinned 7 days ago
n8n-code-nodes-official
This skill guides agents to use n8n Code nodes correctly as a last resort.
by n8nOfficial publisher
Claude Code, Codex, Cursor +4 · about 2.9K tokens · pinned 7 days ago
migrating-airflow-2-to-3
This skill guides agents through migrating Apache Airflow 2.x DAG code to Airflow 3.x, handling breaking changes in imports, operators, context variables, and…
by AstronomerOfficial publisher
Claude Code · about 2.1K tokens · pinned 7 days ago
managing-python-dependencies
This skill ensures the agent manages Python dependencies correctly by detecting the project's existing dependency manager and using the appropriate tool.
by GoogleOfficial publisher
Claude Code, Codex, Cursor +4 · about 740 tokens · pinned 7 days ago
practice-registry
This skill checks Scala, Python, TypeScript, JavaScript, and Rust code against company-specific coding practices before generation, during editing, and before…
by WriterOfficial publisher
Claude Code, Codex, Cursor +4 · about 410 tokens · pinned 7 days ago
python-project
Scaffolds production-grade Python projects with uv package management, pyproject.toml, src layout, Ruff linting, pytest testing, and optional CLI, API…
by NebiusOfficial publisher
Contains scripts
Claude Code, Codex, Cursor +3 · about 3.4K tokens · pinned 7 days ago
Open roles at Imbue
No open roles at Imbue on the Agent Native jobs board right now.
Browse the jobs board