Individual skill

autoresearch

Runs a hill-climbing study over many training or analysis runs with the study and experiments tools, one metric and direction, a baseline, ideas ranked by expected value, exactly one run per idea, kill criteria and a budget, verdicts with analysis and lessons, and a conclusion. Use for autoresearch, hyperparameter or ablation sweeps left to run, "make this metric better", or any loop of experiments the user wants driven for hours. For a single reproduction use reproduce; for designing the study's hypotheses first use hypotheses.

backend/cli/skills/core/autoresearch/SKILL.md

Read pinned source

Source commit a08e0ad0ad3d6448123039ee4659163eb2e35d99

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
4,354
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Autoresearch

A study turns "make this metric better" into a loop that runs for hours or days without
losing the thread. You own the science: which ideas to try, how to implement them, what a
result means. OpenScience owns the clock: it tracks every metric the script logs, notices
when a run ends, kills runs that break the study's criteria, keeps the budget, renders the
ledger, and wakes this session with a "Study update" whenever there is news.

## Before the study

1. Agree the objective with the user: one metric, its direction, the budget, the compute
   target, how many runs may be live at once, and the kill criteria. The budget is a spend
   decision and belongs to this study alone: never carry one over from an earlier study or
   an earlier instruction in the session. If the request names no budget, ask once, with a