autoresearch

Iterate on a mission using evaluator-driven pass/fail JSON until max-runtime ends.

Updated May 20, 2026
One-click install
npx skills add https://github.com/xdkp/oh-my-claudecode --skill autoresearch-xdkp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoresearch
Source: https://github.com/xdkp/oh-my-claudecode/tree/main/skills/autoresearch
Command: npx skills add https://github.com/xdkp/oh-my-claudecode --skill autoresearch-xdkp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autoresearch solves the problem of getting reliable, step-by-step improvement for one mission without losing control over evaluation quality or run duration.

Core Features & Use Cases

  • Stateful single-mission improvement loop: Runs one mission at a time, repeatedly applying experiment cycles until an explicit stop condition is met.
  • Strict evaluator contract & durable artifacts: Requires evaluator output as JSON including a boolean pass (and optional numeric score), and persists iteration-by-iteration logs and decisions under .omc/autoresearch/<mission-slug>/.
  • Bounded runtime with predictable stopping: Stops primarily on max-runtime, while also supporting explicit terminal conditions and cancellation, so runs don’t drift indefinitely.
  • Use Case: When you have a prepared mission and evaluator from /deep-interview --autoresearch, use this skill to continuously refine outputs based on pass/fail evaluation and keep a human-readable decision log.

Quick Start

In your Claude Code session, run /deep-interview --autoresearch first, then activate autoresearch with your mission so it begins iterating and writing evaluation JSON plus markdown decision logs.

Frequently Asked Questions about autoresearch

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

FAQPage Schema
How do I run a stateful improvement loop for a single mission without it running indefinitely?

To run a stateful improvement loop safely, you need a bounded workflow with strict stop rules. This skill executes a single-mission loop that stops only on explicit terminal conditions like max-runtime, preventing indefinite drift while persisting iteration logs.

What format does the evaluator output need to be for an automated research loop?

The evaluator output must be structured JSON containing a required boolean `pass` field and an optional numeric `score`. This strict contract allows the loop to programmatically determine pass/fail conditions and persist machine-readable evaluations for later analysis.

How do I set up mission and evaluator configurations before starting an iterative improvement workflow?

You must first run the `/deep-interview --autoresearch` command to prepare your mission and evaluator setup. Once configured, you can activate the improvement loop to continuously refine outputs based on the pass/fail evaluation contract.

Where are iteration logs and evaluation decisions stored during an automated research run?

Iteration logs and evaluation decisions are persisted as durable artifacts under the `.omc/autoresearch/<mission-slug>/` directory. This stores both machine-readable evaluation JSON and human-readable markdown decision logs for later analysis.

Can I use a single-mission improvement loop for multiple missions at the same time?

No, this workflow runs one mission at a time to ensure reliable, step-by-step improvement without losing control over evaluation quality. It applies experiment cycles to a single mission until an explicit stop condition is met.

Why do I need strict stop rules and max-runtime bounding for iterative research workflows?

Strict stop rules and max-runtime bounding prevent automated research loops from drifting indefinitely. Bounded runtime ensures predictable stopping while still supporting explicit terminal conditions and cancellation when needed.