[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72WD6VHSSX47TG8R7SPM3B0":3,"skill-same:01M72WD6VHSSX47TG8R7SPM3B0":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72WD6VHSSX47TG8R7SPM3B0","autosota-research-loop",null,"Use when operating research-os from a natural-language research goal through evidence-backed selection, redline-audited reproduction, parallel branch optimization, and skill distillation.","jomify\u002Fresearch-os","jomify","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F173770076?v=4","01M72WD51Y6FCTREJMPQ1H8DFA","01M72WD5308T4CHC2DB45JEK3F",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjomify\u002Fresearch-os\u002Fblob\u002Fmain\u002Fskills\u002Fautosota-research-loop\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: autosota-research-loop\ndescription: Use when operating research-os from a natural-language research goal through evidence-backed selection, redline-audited reproduction, parallel branch optimization, and skill distillation.\n---\n\n# AutoSOTA Research Loop\n\nUse this skill when the task is to turn a research request into a controlled `research-os` execution loop instead of an ad hoc paper chase or one-off experiment.\n\n## When To Use\n\n- The user starts from a natural-language research objective.\n- The task needs paper, code, dataset, and benchmark selection backed by recorded evidence.\n- The work must recover a comparable baseline before optimization.\n- The plan needs parallel branch exploration under explicit redline guardrails.\n\n## Required Operator Sequence\n\n1. Start with `research-os intake \"\u003Cgoal>\"` to convert the free-form request into a structured brief.\n2. Build the evidence ledger and use it for evidence-backed selection of papers, repos, datasets, and benchmark constraints.\n3. Create the bundle from the intake record only after the sources, feasibility, and reproducibility signals are attached.\n4. Recover the baseline before proposing branch modifications or claiming any optimization path is valid.\n5. Run a redline audit on the reproduction plan and again on every optimization candidate.\n6. Generate parallel branches from the cleared baseline, preserving parent branch, idea source, patch state, run configuration, and keep-or-reject status.\n7. Rank branch outcomes by metric, stability, cost, and comparability confidence before selecting survivors.\n8. Distill repeated wins and stable repair patterns into notes or follow-on skills only after the evidence is recorded.\n\n## Guardrails\n\n- Never skip `research-os intake`; the loop starts from structured intake, not from improvised commands.\n- Never treat secondary summaries as enough when a primary paper, repo, dataset page, or benchmark source is available.\n- Never optimize before a baseline exists and is reproducible on the selected runner.\n- Never allow a branch to proceed without redline review of metric, dataset, split, script, and constraint integrity.\n- Never report gains from non-comparable settings as if they were baseline-equivalent improvements.\n- Never let parallel branches explode without a branch budget and survivor selection rule.\n\n## Branch Discipline\n\n- Parallel branches are search instruments, not excuses to run untracked experiments.\n- Each branch should represent one bounded idea family or a clearly stated transfer hypothesis.\n- Reject branches that are expensive, fragile, or redline-unsafe even if they show short-term metric movement.\n","# AutoSOTA Research Loop\n\nUse this skill when the task is to turn a research request into a controlled `research-os` execution loop instead of an ad hoc paper chase or one-off experiment.\n\n## When To Use\n\n- The user starts from a natural-language research objective.\n- The task needs paper, code, dataset, and benchmark selection backed by recorded evidence.\n- The work must recover a comparable baseline before optimization.\n- The plan needs parallel branch exploration under explicit redline guardrails.\n\n## Required Operator Sequence\n\n1. Start with `research-os intake \"\u003Cgoal>\"` to convert the free-form request into a structured brief.\n2. Build the evidence ledger and use it for evidence-backed selection of papers, repos, datasets, and benchmark constraints.\n3. Create the bundle from the intake record only after the sources, feasibility, and reproducibility signals are attached.\n4. Recover the baseline before proposing branch modifications or claiming any optimization path is valid.\n5. Run a redline audit on the reproduction plan and again on every optimization candidate.\n6. Generate parallel branches from the cleared baseline, preserving parent branch, idea source, patch state, run configuration, and keep-or-reject status.\n7. Rank branch outcomes by metric, stability, cost, and comparability confidence before selecting survivors.\n8. Distill repeated wins and stable repair patterns into notes or follow-on skills only after the evidence is recorded.\n\n## Guardrails\n\n- Never skip `research-os intake`; the loop starts from structured intake, not from improvised commands.\n- Never treat secondary summaries as enough when a primary paper, repo, dataset page, or benchmark source is available.\n- Never optimize before a baseline exists and is reproducible on the selected runner.\n- Never allow a branch to proceed without redline review of metric, dataset, split, script, and constraint integrity.\n- Never report gains from non-comparable settings as if they were baseline-equivalent improvements.\n- Never let parallel branches explode without a branch budget and survivor selection rule.\n\n## Branch Discipline\n\n- Parallel branches are search instruments, not excuses to run untracked experiments.\n- Each branch should represent one bounded idea family or a clearly stated transfer hypothesis.\n- Reject branches that are expensive, fragile, or redline-unsafe even if they show short-term metric movement.\n",{"name":5,"description":7},"main","0a5db58fe6d3f0e23f96b5e8077356d4c415c0d2","skills\u002Fautosota-research-loop",0,"https:\u002F\u002Fgithub.com\u002Fjomify\u002Fresearch-os","https:\u002F\u002Fgithub.com\u002Fjomify","2026-06-19 15:38:44",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add jomify\u002Fresearch-os --skill autosota-research-loop",{"tool":36,"command":37},"bunx","bunx skills add jomify\u002Fresearch-os --skill autosota-research-loop",{"tool":39,"command":40},"pnpm","pnpm dlx skills add jomify\u002Fresearch-os --skill autosota-research-loop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjomify\u002Fresearch-os\u002Fblob\u002Fmain\u002Fskills\u002Fautosota-research-loop\u002FSKILL.md",true,[],[]]