autoresearch

Runs a validator-gated research loop with persisted state until a completion artifact passes.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill autoresearch-ogiboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoresearch
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/autoresearch
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill autoresearch-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research tasks often stop prematurely when a model declares itself done without verifiable evidence. This Skill replaces the deprecated omx autoresearch CLI with a stateful, native-hook workflow that keeps iterating until an explicit validator confirms the research deliverable meets its mission criteria. ## Core Features & Use Cases - Validator-Gated Completion: The loop only stops when a completion artifact records a passing result from either a mission validator script or a prompt-plus-architect review. - Persistent Mode State: Validation mode, artifact paths, and validator configuration are stored in .omx/state/.../autoresearch-state.json so the loop survives across turns. - Structured Intake: Pairs with $deep-interview --autoresearch to clarify the mission and evaluator, then materializes mission.md, sandbox.md, and result.json specs. - Use Case: You need a bounded research report that must demonstrably improve a metric beyond baseline. Configure a mission validator script, start the loop, and let auto-nudges continue until the result artifact records a passing verdict. ## Quick Start Run $deep-interview --autoresearch to define the mission and evaluator, then start $autoresearch with your chosen validation mode and let it iterate until the completion artifact passes.

Frequently Asked Questions about autoresearch

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

FAQPage Schema
How do I run an automated research loop with validation?

Start with $deep-interview --autoresearch to clarify the mission and evaluator, materialize the mission, sandbox, and result specs, then launch $autoresearch with a chosen validation mode. The loop nudges itself until the completion artifact records a passing validator result.

What validation modes does autoresearch support?

Two modes are available: mission-validator-script, which requires an artifact recording a passing script result, and prompt-architect-artifact, which requires an architect approval verdict plus an output artifact path. Exactly one mode must be chosen at init.

When should I use autoresearch instead of best-practice-research?

Use autoresearch when the research output is a bounded deliverable that must pass an explicit validator. For ordinary pre-planning documentation lookups or general best-practice checks, use $best-practice-research instead.

Can I still launch autoresearch from the omx CLI or tmux?

No. The omx autoresearch command is hard-deprecated, and direct CLI, tmux, and split-pane launches are removed. The workflow now runs as a native-hook stateful skill with intake through $deep-interview --autoresearch.

Why does the autoresearch loop keep running after the model says it is done?

Completion is artifact-gated, not model-declared. The loop ignores verbal claims of done, single stop-hook fires, and no-op turns; it only finishes when the completion artifact satisfies the chosen validation mode.