experiment
You are the Experiment Agent for NanoResearch. This command combines the Setup, Coding, and Execution stages. You will generate runnable experiment code and execute it.
Install / Use
npx skills add OpenRaiser/NanoResearchInstalls into whichever agent you are using.
Claude Commands
Claude Code slash commands
Quality Score
Category
Education & ResearchSupported Platforms
Tags
Our assessment of experiment
experiment scores 82/100 on our quality scale, 364th of 421 Education & Research skills we index.
Its Claude Commands is 4.1 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.
With 1,369 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so experiment is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
experiment compared with similar skills
All 4 of these similar skills score higher than experiment; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| experiment (this skill)by OpenRaiser | 82 | 1.4k | 3mo ago | Claude Commands |
| claude-memby thedotmack | 100 | 117.6k | today | CLAUDE.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 92.8k | 1d ago | CLAUDE.md |
Frequently asked questions
- How do I install experiment?
- Run
npx skills add OpenRaiser/NanoResearch. The install tabs above show the steps for each supported agent. - Which AI agents does experiment work with?
- It is written for Claude Code, as a Claude Commands file. Other agents that read the same format can often use it too.
- Is experiment safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is experiment still maintained?
- The repository was last updated about 3 months ago, so experiment is actively maintained.
Skill content
View source on GitHubExperiment — Setup + Code Generation + Execution
You are the Experiment Agent for NanoResearch. This command combines the Setup, Coding, and Execution stages. You will generate runnable experiment code and execute it.
Input
$ARGUMENTS — workspace path (optional). If not provided, use the most recent workspace under ~/.nanoresearch/workspace/research/.
Prerequisites
Read:
{workspace}/papers/ideation_output.json{workspace}/plans/experiment_blueprint.json
If the blueprint doesn't exist, tell the user to run /project:planning first.
Process
Phase 1: Setup (update manifest: setup → running)
-
Environment setup: Create a Python environment for the experiment:
cd {workspace}/experiment python -m venv .venv source .venv/bin/activate -
Dependency analysis: Based on the blueprint, determine required packages:
- Deep learning framework (torch/tensorflow/jax)
- Data processing (pandas, numpy, scikit-learn)
- Domain-specific libraries
- Evaluation libraries
-
Write
requirements.txtto{workspace}/experiment/requirements.txt -
Install dependencies:
pip install -r requirements.txt -
Dataset preparation: Download or prepare datasets specified in the blueprint.
- Use WebSearch to find download links if needed
- Write download/preprocessing scripts
Update manifest: setup → completed.
Write {workspace}/plans/setup_output.json with environment details.
Phase 2: Coding (update manifest: coding → running)
Generate the experiment code in {workspace}/experiment/:
-
config.py— Experiment configuration (hyperparameters, paths, dataset config) -
data.py— Data loading and preprocessing:- Dataset class(es) for each dataset in the blueprint
- Train/val/test split handling
- Data augmentation if applicable
-
model.py— Model implementations:- Proposed method
- Each baseline method
- Shared components (encoder, decoder, etc.)
-
train.py— Training loop:- Argument parsing
- Model instantiation
- Training loop with logging
- Validation at each epoch
- Checkpointing best model
- Support for SLURM execution
-
evaluate.py— Evaluation:- Load trained model
- Run on test set
- Compute all metrics from blueprint
- Save results to JSON
-
run_all.sh— Shell script to run all experiments:- Proposed method
- Each baseline
- Each ablation variant
-
run_all.slurm— SLURM job script:#!/bin/bash #SBATCH --job-name=nanoresearch #SBATCH --time=30-00:00:00 #SBATCH --gres=gpu:1 #SBATCH --output={workspace}/logs/experiment_%j.log
Update manifest: coding → completed.
Write {workspace}/plans/coding_output.json listing generated files.
Phase 3: Execution (update manifest: execution → running)
-
Pre-flight check: Verify all generated files exist and are syntactically valid:
python -c "import ast; ast.parse(open('train.py').read())" -
Submit experiment:
- Check GPU availability with
sinfo - If SLURM is available:
sbatch run_all.slurm - If local:
bash run_all.sh
- Check GPU availability with
-
Monitor execution:
- Check job status periodically with
squeue - Read log files for progress
- Report any errors to the user
- Check job status periodically with
-
Collect results:
- Read all result JSON files from
experiment/results/ - Compile into a summary
- Read all result JSON files from
-
If execution fails:
- Read error logs
- Attempt to diagnose and fix the issue
- Re-run (up to 3 attempts)
- If still failing, report the error clearly
Update manifest: execution → completed.
Write {workspace}/plans/execution_output.json with results summary.
Output Files
{workspace}/plans/setup_output.json— Environment details{workspace}/plans/coding_output.json— Generated file list{workspace}/plans/execution_output.json— Results summary{workspace}/experiment/— All generated code{workspace}/experiment/results/— Raw experiment results{workspace}/logs/— Execution logs
Tell the user the results summary and suggest running /project:analysis next.
Related Skills
claude-mem
117.6kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Understand-Anything
92.8kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
