autoresearch
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports continuous agent operation via Claude Code /loop and OpenClaw heartbeat, and produces research presentations and papers. Use when starting a research project, running autonomous experiments, or managing a multi-hypothesis research effort.
npx skills add Orchestra-Research/AI-Research-SKILLs --skill 0-autoresearch-skill --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.
What it does
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture: an inner loop for rapid experiment iterations with clear optimization targets, and an outer loop for synthesis, pattern identification, and steering research direction. Routes to domain-specific skills for execution and supports continuous operation via Claude Code /loop and OpenClaw heartbeat. Produces research presentations and papers.
How it works
The skill envisions managing a full research lifecycle from literature survey to final paper by maintaining structured state (research-state.yaml, findings.md, research-log.md) and executing within a two-loop cycle:
- INNER LOOP: pick a hypothesis, design and run an experiment, measure and record results, learn, and iterate with clear measurable outcomes. Route experiment execution to domain skills as needed (data processing, model training, evaluation, etc.). Maintain records under experiments/{hypothesis-slug}/ with explicit labeling (CONFIRMATORY vs EXPLORATORY).
- OUTER LOOP: review all results since last reflection, cluster results, identify mechanisms, update findings.md, generate new hypotheses, decide direction (DEEPEN, BROADEN, PIVOT, CONCLUDE), and log reflections in research-log.md. Generate progress presentations if meaningful.
- FINALIZE: write the paper via ml-paper-writing and create final presentations for archiving.
The two-loop architecture is practiced with a BOOTSTRAP, INNER LOOP (fast, autonomous), OUTER LOOP (reflective), and FINALIZE stages. The agent can pivot back to literature, brainstorm via 21-research-ideation skills, and route to domain skills like data processing, model training, evaluation, and more as listed under the Route to Domain Skills section.
The agent maintains a running trajectory of experiment outcomes and updates research-state.yaml and findings.md to reflect progress.
When to use it
Use when starting a research project, running autonomous experiments, or managing a multi-hypothesis research effort. The skill emphasizes full autonomy—no user confirmation needed—and frequent human visibility through HTML/PDF progress presentations in to_human/.
What it can touch
- Domain execution is routed to domain-specific SKILLs (e.g., data processing, model training, distributed training, evaluation, inference, interpretability, ML Ops, cloud compute) as referenced in the skill’s guidance.
- It uses the internal artifacts: research-state.yaml, research-log.md, findings.md, literature/, experiments/ directories, and to_human/ for progress reports.
Caveats
- It runs autonomously and instructs ongoing progress reporting; user prompts are not requested for standard progress. License is MIT per the frontmatter. The outer loop’s decision criteria include DEEPEN, BROADEN, PIVOT, and CONCLUDE. The workflow assumes the agent can access and execute domain-specific SKILLs and update central state files accordingly.
# Autoresearch Autonomous research orchestration for AI coding agents. You manage the full research lifecycle — from literature survey to published paper — by maintaining structured state, running a two-loop experiment-synthesis cycle, and routing to domain-specific skills for execution. You are a research project manager, not a domain expert. You orchestrate; the domain skills execute. **This runs fully autonomously.** Do not ask the user for permission or confirmation — use your best judgment and keep moving. Show the human your progress frequently through research presentations (HTML/PDF) so they can see what you're doing and redirect if needed. The human is asleep or busy; your job is to make as much research progress as possible on your own. ## Getting Started Users arrive in different states. Determine which and proceed: | User State | What to Do | |---|---| | Vague idea ("I want to explore X") | Brief discussion to clarify, then bootstrap | | Clear research question | Bootstrap directly | | Existing plan or proposal | Review plan, set up workspace, enter loops | | Resuming (research-state.yaml exists) | Read state, continue from where you left off | If things are clear, don'
- Getting Started
- Initialize Workspace
- The Two-Loop Architecture
- Research is Non-Linear
- Bootstrap: Literature and Hypotheses
- The Inner Loop
- Route to Domain Skills
- Track the Experiment Trajectory
- The Outer Loop
- Deciding Direction
- findings.md Is Your Project Memory
- Agent Continuity (MANDATORY — Set Up First)
- Claude Code
- OpenClaw
What does the autoresearch skill do?
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports continuous agent operation via Claude Code /loop and OpenClaw heartbeat, and produces research presentations and papers. Use when starting a research project, running autonomous experiments, or managing a multi-hypothesis research effort.
How do I install it?
Run `npx skills add Orchestra-Research/AI-Research-SKILLs --skill 0-autoresearch-skill --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 Orchestra-Research/AI-Research-SKILLs, a repository with 11,391 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.
