Back to Skills

autoresearch

Autonomous iterative experimentation loop for any programming task. Guides the user through defining goals, measurable metrics, and scope constraints, then runs an autonomous loop of code changes, testing, measuring, and keeping/discarding results. Inspired by Karpathy's autoresearch. USE FOR: autonomous improvement, iterative optimization, experiment loop, auto research, performance tuning, automated experimentation, hill climbing, try things automatically, optimize code, run experiments, auton

33,817stars4,135forksUpdated 5/26/2026

Security Assessment

Safe(100/100)
Security Score100/100

About autoresearch

Autoresearch is an autonomous iterative experimentation skill designed for programming tasks that have a measurable outcome. Instead of performing one-off code changes, the skill establishes a structured optimization loop where the user defines a goal, specifies how success is measured, and sets clear scope and constraint boundaries. Once configured, the agent repeatedly modifies code, runs experiments, measures results, and determines whether to keep or revert changes. The process is inspired by Karpathy's autoresearch concept and extends it beyond machine learning workflows to general software engineering and performance optimization tasks.

The skill emphasizes disciplined experimentation and reproducibility. Before any experimentation begins, it guides the user through an interactive setup phase to define optimization goals, metric commands, extraction methods, editable file scopes, and operational constraints. During execution, the system establishes a baseline measurement, commits every experiment attempt to git for safe rollback, records experiment results in a TSV log, and automatically reverts changes that do not improve the selected metric. The workflow is designed to run autonomously after setup, ensuring continuous experimentation without requiring repeated user confirmation.

This skill is intended for developers, performance engineers, and technical teams working on optimization-focused programming tasks. Typical use cases include improving execution speed, reducing memory usage, optimizing benchmark scores, decreasing build times, increasing throughput, and refining automated test outcomes. It is best suited for projects already managed with git and environments where terminal access is available. The skill is not intended for simple bug fixes, code reviews, or tasks that lack a measurable metric.

FAQ

What kinds of programming tasks is autoresearch designed for?

Autoresearch is designed for programming tasks with measurable outcomes, such as performance optimization, benchmark improvements, reducing memory usage, improving test pass rates, or decreasing build times.

Does the project need to use git?

Yes. The skill requires the project to be a git repository because each experiment attempt is committed and reverted when necessary.

Can the skill run without a defined metric?

No. A measurable metric is required before experimentation begins. The user must provide a command to run, a method to extract the metric, and whether higher or lower values are better.

Does autoresearch modify any file in the repository?

No. The user must explicitly define which files or directories are in scope for modification and which are off limits.

Can autoresearch install dependencies or change the environment automatically?

No. The skill does not install new dependencies or make environment changes unless the user explicitly approves them.

Install autoresearch

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill