autoresearch
Skill1 starsChanged 7 months agoMITView on GitHub
Use when setting up or running iterative autonomous experimentation — define a target file, success metric, and iteration budget, then let the agent loop through changes and keep only improvements. Inspired by Karpathy's autoresearch ratchet loop pattern.
100 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- WdBlink/autoresearch-papertheir own version, first seen Nov 8, 2026
- OpenLAIR/dr-clawtheir own version, first seen Nov 8, 2026
- taixuann/development-spacetheir own version, first seen Nov 8, 2026
- TidalPaladin/skillstheir own version, first seen Nov 8, 2026
- usecompai/compound-operations-modeltheir own version, first seen Nov 8, 2026
Used with
Projects with it also use aeon-update, auto-workflow and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
aaronjmarsSkillaeon-update
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
Also in 4 projects that use this
aaronjmarsSkillauto-workflow
Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.
Also in 4 projects that use this
- +10 more from aaronjmars
Other versions100 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 100
- github/awesome-copilot★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- AgriciDaniel/claude-obsidian★ 16ksame name
- Orchestra-Research/AI-research-SKILLs★ 13ksame name
- zechenzhangAGI/AI-research-SKILLs★ 13ksame name
- Orchestra-Research/AI-Research-SKILLs★ 12ksame name
- advaitpaliwal/feynman★ 10ksame name
- companion-inc/feynman★ 10ksame name
90 more not listed
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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- chrome-devtoolsSkill
- experiment-runnerSkill
- playwright-browserSkill
- pr-reviewSkill
- save-knowledgeSkill
- skill-creatorSkill
- sp-plan-discoverySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 96 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Create program.md in the project root.
- Very specific: line 63
After the loop ends, read experiments.md and summarize:
“Common” is measured: kept by at least 6 in 10 of the 96 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
autoresearch
Orchestrate an autonomous experimentation session. You define the goal and metric; the loop does the rest.
Step 1 — Define Parameters
Answer these four questions with the user before writing anything:
- Target file — What single file will the agent modify each iteration?
(e.g.,
src/model.py,config/prompt.txt,src/algorithm.js) - Success metric — How is improvement measured? Must return a single numeric value. (e.g., accuracy %, test pass count, latency ms, benchmark score)
- Time budget — How long is one experiment allowed to run? (e.g., 30s, 5min, 30min)
- Max iterations — Total attempts before stopping. (e.g., 20, 50, 100)
Step 2 — Write program.md
Create program.md in the project root. This is the instruction file the loop executes each iteration:
# Experiment Program
**Target:** path/to/target/file
**Metric:** [description of what to measure — must produce a single number]
**Baseline:** [current metric value before any changes — measure this first]
**Time per experiment:** Xs / Xmin
**Max iterations:** N
**Stop condition:** metric > X, or max iterations reached
## Hypothesis Space
[Ordered list of approaches to try — agent works through these in priority order]
1. [Most promising approach]
2. [Second approach]
3. [Third approach]
## Constraints
[What must NOT change across experiments]
- Do not modify test files
- API surface must remain backward compatible
- [Add domain-specific constraints]Measure the baseline BEFORE starting the loop. Record it in program.md.
Step 3 — Delegate to experiment-runner
Once program.md is approved by the user, hand off to experiment-runner to execute the loop.
Provide experiment-runner with:
- Path to
program.md - Path to
scripts/measure.sh(the metric script — must be adapted for this domain) - Confirmation that the git working tree is clean
Step 4 — Summarize Results
After the loop ends, read experiments.md and summarize:
- Total iterations run
- Experiments kept (metric delta per experiment, commit hash)
- Experiments marked "positive but inconsistent" (why consistency failed)
- Final baseline vs initial baseline (total improvement)
- Recommended next steps
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.

