[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7869EB4C3MZZDAQG4AXK3ZT":3,"skill-same:01M7869EB4C3MZZDAQG4AXK3ZT":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7869EB4C3MZZDAQG4AXK3ZT","autoresearch",null,"[OMX] Stateful validator-gated research loop with native-hook persistence","Tenon-Net\u002FTenonAdmin","Tenon-Net","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F301772982?v=4","01M7865ABCRD19RRSN8D1HAH72","Tenon.Net","01M7865ACHBZC7NJ54M5S7MCDV",45,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fautoresearch\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: autoresearch\ndescription: \"[OMX] Stateful validator-gated research loop with native-hook persistence\"\n---\n\n# Autoresearch\n\nAutoresearch is the skill-first replacement for the deprecated `omx autoresearch` command.\nIt keeps the useful measured-research loop, but it now runs as a native-hook stateful workflow instead of a direct CLI or tmux launch surface.\n\n## Boundary with planning research\n\nUse `$autoresearch` when the research output itself is a bounded deliverable that must pass an explicit validator. Do not recommend it for ordinary pre-planning docs lookup or general best-practice checks; use `$best-practice-research` for that. If `$autoresearch` is intentionally run before architecture planning, its approved artifact should feed evidence into `$ralplan`; it should not become a final architecture\u002Fcomponent unless the user explicitly asks for ongoing research automation.\n\n## Use when\n- You want a Ralph-ish persistent research loop\n- The task should keep nudging until explicit validation evidence exists\n- You want init-time choice between script validation and prompt+architect validation\n\n## Do not use when\n- You want the old `omx autoresearch` command surface (hard-deprecated)\n- You want detached tmux or split-pane launch parity\n- You have not decided the validation regime yet\n\n## Core contract\n1. **Init chooses validation mode.** Pick exactly one:\n   - `mission-validator-script`\n   - `prompt-architect-artifact`\n2. **Persist mode state** in `.omx\u002Fstate\u002F...\u002Fautoresearch-state.json` including:\n   - `validation_mode`\n   - `completion_artifact_path`\n   - `mission_validator_command` **or** `validator_prompt`\n   - optional `output_artifact_path`\n3. **Completion is artifact-gated.** The loop does not stop because the model says “done”, because a stop hook fired once, or because several turns were no-ops.\n4. **Direct CLI launch is gone.** Use `$deep-interview --autoresearch` for intake and `$autoresearch` for execution.\n\n## Completion artifact contract\n\n### `mission-validator-script`\nThe completion artifact must exist and record a passing validator result, for example:\n\n```json\n{\n  \"status\": \"passed\",\n  \"passed\": true,\n  \"summary\": \"metric improved beyond baseline\"\n}\n```\n\n### `prompt-architect-artifact`\nThe completion artifact must include both an architect approval verdict and an output artifact path, for example:\n\n```json\n{\n  \"validator_prompt\": \"Review the research output against the mission.\",\n  \"architect_review\": { \"verdict\": \"approved\" },\n  \"output_artifact_path\": \".omx\u002Fspecs\u002Fautoresearch-demo\u002Freport.md\"\n}\n```\n\n## Recommended flow\n1. Run `$deep-interview --autoresearch` to clarify mission + evaluator.\n2. Materialize `.omx\u002Fspecs\u002Fautoresearch-{slug}\u002Fmission.md`, `sandbox.md`, and `result.json`.\n3. Start `$autoresearch` with the chosen validation mode stored in mode state.\n4. Let stop-hook \u002F auto-nudge continue until the completion artifact satisfies the chosen validation mode.\n5. Finish only after the validator artifact is complete.\n\n## Migration note\n- `omx autoresearch` is hard-deprecated.\n- No direct CLI launch.\n- No tmux split-pane launch.\n- No noop-count completion gate.\n","# Autoresearch\n\nAutoresearch is the skill-first replacement for the deprecated `omx autoresearch` command.\nIt keeps the useful measured-research loop, but it now runs as a native-hook stateful workflow instead of a direct CLI or tmux launch surface.\n\n## Boundary with planning research\n\nUse `$autoresearch` when the research output itself is a bounded deliverable that must pass an explicit validator. Do not recommend it for ordinary pre-planning docs lookup or general best-practice checks; use `$best-practice-research` for that. If `$autoresearch` is intentionally run before architecture planning, its approved artifact should feed evidence into `$ralplan`; it should not become a final architecture\u002Fcomponent unless the user explicitly asks for ongoing research automation.\n\n## Use when\n- You want a Ralph-ish persistent research loop\n- The task should keep nudging until explicit validation evidence exists\n- You want init-time choice between script validation and prompt+architect validation\n\n## Do not use when\n- You want the old `omx autoresearch` command surface (hard-deprecated)\n- You want detached tmux or split-pane launch parity\n- You have not decided the validation regime yet\n\n## Core contract\n1. **Init chooses validation mode.** Pick exactly one:\n   - `mission-validator-script`\n   - `prompt-architect-artifact`\n2. **Persist mode state** in `.omx\u002Fstate\u002F...\u002Fautoresearch-state.json` including:\n   - `validation_mode`\n   - `completion_artifact_path`\n   - `mission_validator_command` **or** `validator_prompt`\n   - optional `output_artifact_path`\n3. **Completion is artifact-gated.** The loop does not stop because the model says “done”, because a stop hook fired once, or because several turns were no-ops.\n4. **Direct CLI launch is gone.** Use `$deep-interview --autoresearch` for intake and `$autoresearch` for execution.\n\n## Completion artifact contract\n\n### `mission-validator-script`\nThe completion artifact must exist and record a passing validator result, for example:\n\n```json\n{\n  \"status\": \"passed\",\n  \"passed\": true,\n  \"summary\": \"metric improved beyond baseline\"\n}\n```\n\n### `prompt-architect-artifact`\nThe completion artifact must include both an architect approval verdict and an output artifact path, for example:\n\n```json\n{\n  \"validator_prompt\": \"Review the research output against the mission.\",\n  \"architect_review\": { \"verdict\": \"approved\" },\n  \"output_artifact_path\": \".omx\u002Fspecs\u002Fautoresearch-demo\u002Freport.md\"\n}\n```\n\n## Recommended flow\n1. Run `$deep-interview --autoresearch` to clarify mission + evaluator.\n2. Materialize `.omx\u002Fspecs\u002Fautoresearch-{slug}\u002Fmission.md`, `sandbox.md`, and `result.json`.\n3. Start `$autoresearch` with the chosen validation mode stored in mode state.\n4. Let stop-hook \u002F auto-nudge continue until the completion artifact satisfies the chosen validation mode.\n5. Finish only after the validator artifact is complete.\n\n## Migration note\n- `omx autoresearch` is hard-deprecated.\n- No direct CLI launch.\n- No tmux split-pane launch.\n- No noop-count completion gate.\n",{"name":5,"description":7},"main","8b5d641d390d190c08d259be0020dbd054165620",".codex\u002Fskills\u002Fautoresearch",12,"https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin","https:\u002F\u002Ftenon.52moyu.net","https:\u002F\u002Fgithub.com\u002FTenon-Net","2026-10-23 20:22:32",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Tenon-Net\u002FTenonAdmin --skill autoresearch",{"tool":38,"command":39},"bunx","bunx skills add Tenon-Net\u002FTenonAdmin --skill autoresearch",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Tenon-Net\u002FTenonAdmin --skill autoresearch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fautoresearch\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M786B2SWRDH5STXY78PY11GP","worker","[OMX] Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams","https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fworker\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M786AZ5RN9PM7DYVNEHR2F35","wiki","[OMX] Persistent markdown project wiki stored under repository omx_wiki with keyword search and lifecycle capture","https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fwiki\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M786AX120YXVKVS1C45EMJV7","visual-ralph","[OMX] Implement or restyle frontend UI against a generated image, static reference, or live URL through measured capture-and-compare iteration.","https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fvisual-ralph\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M786ASC8R32D99RMEQM4E0J4","ultraqa","[OMX] Adversarial dynamic e2e QA workflow - generate hostile scenarios, test, verify, fix, report, and clean up","https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fultraqa\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M786AQ39T8WD85J8BSCCN646","ultragoal","[OMX] Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.","https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fultragoal\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M786AMVDKJEKND0BAQY74WZJ","team","[OMX] N coordinated agents on shared task list using tmux-based orchestration","https:\u002F\u002Fgithub.com\u002FTenon-Net\u002FTenonAdmin\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fteam\u002FSKILL.md",[],[]]