autoresearch

GitHub

支持单任务迭代优化的技能,通过评估器驱动实验循环,持久化记录决策日志与评估结果,并在达到最大运行时间或终止条件时停止。

skills/autoresearch/SKILL.md Yeachan-Heo/oh-my-claudecode

Trigger Scenarios

需要基于评估器的单任务持续迭代优化 需要通过 Claude Code cron 定期执行自动研究任务

Install

npx skills add Yeachan-Heo/oh-my-claudecode --skill autoresearch -g -y
More Options

Use without installing

npx skills use Yeachan-Heo/oh-my-claudecode@autoresearch

指定 Agent (Claude Code)

npx skills add Yeachan-Heo/oh-my-claudecode --skill autoresearch -a claude-code -g -y

安装 repo 全部 skill

npx skills add Yeachan-Heo/oh-my-claudecode --all -g -y

预览 repo 内 skill

npx skills add Yeachan-Heo/oh-my-claudecode --list

SKILL.md

Frontmatter
{
    "name": "autoresearch",
    "level": 4,
    "description": "Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior",
    "argument-hint": "[--mission-dir <path>] [--max-runtime <duration>] [--cron <spec>] [--resume <run-id>]"
}
Autoresearch is a stateful skill for bounded, evaluator-driven iterative improvement. It owns one mission at a time, keeps iterating through non-passing results, records each evaluation and decision as durable artifacts, and stops only when an explicit max-runtime ceiling or another explicit terminal condition is reached.

<Use_When>

  • You already have a mission and evaluator from /deep-interview --autoresearch
  • You want persistent single-mission improvement with strict evaluation
  • You need durable experiment logs under .omc/autoresearch/
  • You want a supported path for periodic reruns via Claude Code native cron </Use_When>

<Do_Not_Use_When>

  • You need evaluator generation at runtime — use /deep-interview --autoresearch first
  • You need multiple missions orchestrated together — v1 forbids that
  • You want the deprecated omc autoresearch CLI flow — it is no longer authoritative </Do_Not_Use_When>
- Single-mission only in v1 - Mission setup/evaluator generation stays in `deep-interview --autoresearch` - Evaluator output must be structured JSON with required boolean `pass` and optional numeric `score` - Non-passing iterations do **not** stop the run - Stop conditions are explicit and bounded, with max-runtime as the primary strict stop hook

<Required_Artifacts> Canonical persistent storage lives under .omc/autoresearch/<mission-slug>/ and/or .omc/logs/autoresearch/<run-id>/.

Minimum required artifacts:

  • mission spec
  • evaluator script or command reference
  • per-iteration evaluation JSON
  • markdown decision logs

Recommended canonical shape:

.omc/autoresearch/<mission-slug>/
  mission.md
  evaluator.json
  runs/<run-id>/
    evaluations/
      iteration-0001.json
      iteration-0002.json
    decision-log.md

Reuse existing runtime artifacts when available rather than duplicating them unnecessarily. </Required_Artifacts>

1. Confirm a single mission exists and evaluator setup is already available. 2. Ensure mode/state is active for `autoresearch` and records: - mission slug/dir - evaluator reference - iteration count - started/updated timestamps - explicit max-runtime or deadline 3. On every iteration: - run exactly one experiment/change cycle - run the evaluator - persist machine-readable evaluation JSON - append a human-readable markdown decision log entry - continue even when evaluation does not pass 4. Stop when: - max-runtime ceiling is reached - user explicitly cancels - another explicit terminal condition is recorded by the runtime

<Cron_Integration> Claude Code native cron is a supported integration point for periodic mission enhancement. In v1, prefer documenting/configuring cron inputs over building a large scheduler UI.

If cron is used:

  • keep one mission per scheduled job
  • preserve the same mission/evaluator contract
  • append new run artifacts rather than overwriting prior experiments </Cron_Integration>

<Execution_Policy>

  • Do not hand execution back to omc autoresearch
  • Do not create multi-mission orchestration
  • Prefer reusing src/autoresearch/* runtime/schema helpers where they already match the stricter contract
  • Keep logs useful to humans, not only machines </Execution_Policy>

Version History

  • 41a4c0f Current 2026-07-25 07:05

Same Skill Collection

skills/ai-slop-cleaner/SKILL.md
skills/ask/SKILL.md
skills/autopilot/SKILL.md
skills/cancel/SKILL.md
skills/ccg/SKILL.md
skills/configure-notifications/SKILL.md
skills/debug/SKILL.md
skills/deep-dive/SKILL.md
skills/deep-interview/SKILL.md
skills/deepinit/SKILL.md
skills/external-context/SKILL.md
skills/hud/SKILL.md
skills/learner/SKILL.md
skills/local-build-reminder/SKILL.md
skills/mcp-setup/SKILL.md
skills/merge-readiness/SKILL.md
skills/omc-doctor/SKILL.md
skills/omc-reference/SKILL.md
skills/omc-setup/SKILL.md
skills/omc-teams/SKILL.md
skills/plan/SKILL.md
skills/project-session-manager/SKILL.md
skills/ralph/SKILL.md
skills/ralplan/SKILL.md
skills/release/SKILL.md
skills/remember/SKILL.md
skills/sciomc/SKILL.md
skills/self-improve/SKILL.md
skills/setup/SKILL.md
skills/skill/SKILL.md
skills/skillify/SKILL.md
skills/team/SKILL.md
skills/trace/SKILL.md
skills/ultragoal/SKILL.md
skills/ultraqa/SKILL.md
skills/ultrawork/SKILL.md
skills/verify/SKILL.md
skills/visual-verdict/SKILL.md
skills/wiki/SKILL.md
skills/writer-memory/SKILL.md

Metadata

Files
0
Version
5aa678c
Hash
f98736d7
Indexed
2026-07-25 07:05

inicio - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-21 04:06
浙ICP备14020137号-1 $mapa de visitantes$