experiment-controller
Use this skill whenever the user wants to execute experiments based on a finalized method and record results. Triggers include: 'run experiment', 'experiment controller', 'implement experiment', 'run model', 'execute training', 'experiment-controller', 'record results', 'ablation study', or any request to turn METHOD.md into concrete runs and output to EXPERIMENT.md. This skill is the **mandatory interface-layer experiment executor** in NeuroClaw: it searches literature/GitHub for matching experimental setups and codebases, proposes one scheme + repo after user discussion, uses git skills to d
npx skills add BioTender-max/awesome-bio-agent-skills --skill experiment-controller --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Experiment Controller ## Overview This skill implements the **Literature/GitHub Search → Scheme Confirmation → Git Execution → Iterative Logging** process for the NeuroClaw experiment-controller phase. It acts as the Experiment Manager within the multi-agent framework: - Reads the latest **IDEA.md** and **METHOD.md** from the workspace. - Searches recent literature (multi-search-engine, arxiv-search, pubmed-search) and GitHub for reproducible experimental setups and open-source repositories that match the proposed architecture. - Summarizes candidate schemes (hyperparameters, datasets, baselines, training protocols) and proposes the most suitable GitHub repo. - Iteratively discusses with the user to confirm the exact scheme/repo. - After confirmation: uses git-essentials/git-workflows to clone, dependency-planner to install environment, claw-shell to run the experiment (training/inference/ablation). - After every run (or ablation), automatically records: setup details, metrics, logs, observations, and any issues. - Saves everything in **EXPERIMENT.md** (with dated sections for each run). **Research use only** — the output is a complete, reproducible EXPERIMENT.md ready for paper-
- Overview
- Quick Reference (Experiment Flow)
- Harness Engineering Protocol (Mandatory for Reproducibility)
- Phase 1: Task Decomposition
- Phase 2: Agent Initialization
- Phase 3: Execution with Incremental Logging
- Phase 4: Verification and Post-Execution Validation
- Self-Verification Implementation Details
- Installation
- Important Notes & Limitations
- When to Call This Skill
- Complementary / Related Skills
- Reference
Place files in: skills/experiment-controller/
What does the experiment-controller skill do?
Use this skill whenever the user wants to execute experiments based on a finalized method and record results. Triggers include: 'run experiment', 'experiment controller', 'implement experiment', 'run model', 'execute training', 'experiment-controller', 'record results', 'ablation study', or any request to turn METHOD.md into concrete runs and output to EXPERIMENT.md. This skill is the **mandatory interface-layer experiment executor** in NeuroClaw: it searches literature/GitHub for matching experimental setups and codebases, proposes one scheme + repo after user discussion, uses git skills to d
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill experiment-controller --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.