new-experiment
Skill25 starsChanged 2 months agoMITView on GitHub
Use when starting a new experiment or creating a variant of an existing `expNNx` run. Triggers on "new experiment", "新实验", "scaffold exp", "set up experiment", "create experiment".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Tresjs/trestheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Tresjs/tres★ 3.8ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-skillSkill
- project-skillSkill
- analyze-experimentSkill
- commit-changelogSkill
- init-projectSkill
- monitorSkill
- read-paperSkill
- survey-literatureSkill
- todoSkill
- update-docsSkill
- update-knowhowSkill
- update-project-skillSkill
- visualizeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use the bundled scaffold interface so experiment naming, files, summary rows, and pipeline state stay consistent.
- Very specific: line 26
Never reuse an existing experiment directory.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
New Experiment
Use the bundled scaffold interface so experiment naming, files, summary rows, and pipeline state stay consistent.
- Establish a one-line motivation and optional parent. Infer the next ID unless the user supplied one.
Resolve
<plugin-root>and preview:python3 <plugin-root>/scripts/new_experiment.py plan \ --motivation "<motivation>" [--parent expNNx] [--exp-id expNNx]- Confirm only if the proposed ID or parent is ambiguous. Rerun with
apply, thencheckusing the returned experiment ID. - Report the new paths and exact launch command. Monitoring remains a separate one-shot workflow.
Never reuse an existing experiment directory. A parent config may be copied,
but code and results are not. Generated run.py refuses a live run until its
experiment body is implemented.
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.