autoresearch

Orchestrates autonomous ML research projects using a two-loop experiment and synthesis architecture.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/Its-Atharva-Gupta/forge-researcher --skill autoresearch-its-atharva-gupta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoresearch
Source: https://github.com/Its-Atharva-Gupta/forge-researcher/tree/main/skills/autoresearch
Command: npx skills add https://github.com/Its-Atharva-Gupta/forge-researcher --skill autoresearch-its-atharva-gupta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires semanticscholar, arxiv, and includes references (resource) components.

What problem does it solve? Running an open-ended ML research project requires constant hypothesis management, experiment tracking, literature review, and synthesis — work that stalls when a human cannot supervise continuously. This Skill turns an AI agent into an autonomous research project manager that keeps experiments running, records results, and steers direction without waiting for human input. ## Core Features & Use Cases - Two-Loop Research Engine: An inner loop runs rapid experiments against locked protocols and measurable metrics, while an outer loop periodically synthesizes results into findings.md and decides whether to deepen, broaden, pivot, or conclude. - Structured Research Workspace: Initializes research-state.yaml, research-log.md, findings.md, literature/, experiments/, and to_human/ directories so state survives across sessions and agent restarts. - Continuous Operation: Sets up a mandatory 20-minute continuity loop via Claude Code /loop or an OpenClaw cron job so research never idles between cycles. - Domain Skill Routing: Delegates execution to specialized skills for data processing, training, evaluation, interpretability, and paper writing (NeurIPS/ICML/ICLR LaTeX templates). - Use Case: Give the agent a question like "does cosine warmup improve small-model convergence", and it will survey literature, form hypotheses, run experiments, plot the optimization trajectory, generate progress reports, and draft a paper when the evidence supports a contribution. ## Quick Start Ask the agent to start an autonomous research project on your research question and let it bootstrap the workspace, set up the continuity loop, and begin running experiments.

Frequently Asked Questions about autoresearch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run autonomous ML research experiments with an AI agent?

Invoke the autoresearch skill with a research question. It bootstraps a workspace with state files, searches literature via Semantic Scholar, arXiv, and CrossRef, forms testable hypotheses, then runs a two-loop cycle of experiments and synthesis without requiring human approval.

What is the two-loop architecture in autonomous research?

The inner loop runs rapid experiments against locked protocols with measurable metrics. The outer loop periodically reviews accumulated results, updates findings.md, generates new hypotheses, and decides whether to deepen, broaden, pivot, or conclude the research.

How does the agent keep running between sessions?

The skill mandates setting up a continuity mechanism first: a /loop 20m command in Claude Code or a cron job via cron.add in OpenClaw. Each tick re-reads research-state.yaml and findings.md to restore context and continue work.

Can autoresearch work without a GPU?

Yes. The skill instructs the agent to adapt to available compute, scaling experiments down to CPU when no GPU exists. Analysis, interpretability, and small model training tasks run on CPU rather than blocking on hardware.

When should I use autoresearch instead of individual domain skills?

Use autoresearch for open-ended questions needing iterative experimentation and synthesis beyond a single metric. Use individual domain skills directly for one-off tasks like training a single model, running one evaluation, or writing a paper.

Why does the skill require committing protocols to git before experiments?

Committing the protocol before running creates temporal proof that the plan existed before results, acting as lightweight pre-registration. This separates confirmatory results from exploratory findings and prevents unconscious metric gaming.