autoresearch

Run iterative improvement loops with JSON evaluation and decision logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of improving a single mission through repeated experimentation while keeping evaluation results consistent, auditable, and bounded by an explicit stopping rule.

Core Features & Use Cases

  • Stateful single-mission improvement loop: Runs iterative experiments for one mission at a time and preserves run history.
  • Strict evaluator contract + JSON evidence: Requires evaluator output to be structured JSON with a required boolean pass field and optional numeric score.
  • Human-readable decision logging: Appends a markdown decision log for each iteration so you can review why changes happened.
  • Hard stop via max-runtime: Stops only when max-runtime (or another explicit termination condition) is reached, rather than silently running forever.
  • Cron-compatible periodic reruns: Supports Kimi CLI cron to schedule recurring runs without overwriting earlier evidence.

Quick Start

Run autoresearch after you obtain a mission and evaluator from deep-interview, and let it persist iterations under .omk/autoresearch/ while enforcing the max-runtime bound.

Frequently Asked Questions about autoresearch

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

FAQPage Schema
How do I run iterative improvement loops with strict evaluator contracts for machine learning experiments?

Iterative improvement requires a strict evaluator contract where each run outputs structured JSON with a boolean pass field and optional score, while appending a human-readable decision log to track why changes occurred. This ensures evaluations remain consistent and auditable across repeated experiment cycles.

What is the best way to persist experiment tracking data and decision logs for stateful agents?

Persisting experiment tracking data involves saving machine-readable evaluation JSON and human-readable markdown decision logs under a dedicated directory. This preserves run history for stateful agents without overwriting earlier evidence during subsequent periodic reruns.

How do I stop an iterative experimentation loop from running indefinitely?

To stop an iterative experimentation loop from running indefinitely, enforce an explicit max-runtime bound or another explicit termination condition. The loop halts only when this threshold is reached rather than silently running forever.

Can I schedule periodic reruns for a stateful single-mission improvement loop using cron?

Yes, you can schedule periodic reruns for a stateful single-mission improvement loop using cron. This compatibility allows recurring executions without overwriting earlier machine-readable JSON evaluation evidence or markdown decision logs.

Does JSON evaluation for iterative experimentation require a specific data structure?

JSON evaluation for iterative experimentation requires a structured output format containing a boolean pass field and an optional numeric score. This strict evaluator contract ensures each iteration is recorded consistently as machine-readable evidence.