[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D32MHZSZWBKPYFRVJECXPM":3,"skill-same:01M7D32MHZSZWBKPYFRVJECXPM":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7D32MHZSZWBKPYFRVJECXPM","best-practice-research",null,"[OMX] Bounded best-practice research wrapper using official\u002Fupstream evidence first","Pibomeister\u002Fagent-kit","Pibomeister","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11633791?v=4","01M7D2NBHEKARMHN9MPV2J80XD","Eduardo Picazo","01M7D2NBJ3Z33SGSYCZ0KBD5DE",0,"MIT","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fprovenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fbest-practice-research\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: best-practice-research\ndescription: \"[OMX] Bounded best-practice research wrapper using official\u002Fupstream evidence first\"\nargument-hint: \"\u003Ctechnology|decision|practice question>\"\n---\n\n# Best-Practice Research\n\nUse this skill when a task depends on current external best practices, version-aware guidance, standards, official recommendations, or upstream behavior. This is a workflow wrapper: it routes evidence gathering and synthesis; it is not a new research authority and it does not replace `researcher`.\n\n## Purpose\n\nProduce a cited, reusable best-practice answer or handoff that separates current external evidence from repo-local facts and dependency-selection decisions. For pre-planning investigation, this is the ordinary first research wrapper: gather official\u002Fupstream evidence, then hand it to `$ralplan` or the caller as planning input. Do not present `$best-practice-research` as a final architecture component or as a validator-gated research loop.\n\n## Terminal By Default\n\nThis skill is terminal and read-only by default. It gathers evidence and produces a cited recommendation with a handoff, then stops. Do not write or edit files, create or amend commits, run mutating commands, or otherwise modify repository state under this skill — even when the question has clear implementation implications. When implementation is warranted, stop and hand off rather than continuing: name `$ralplan` for planning and `$ultragoal`, `$team`, or `executor` for execution, and resume only after the user explicitly switches to that workflow.\n\n## Activate When\n\n- The user asks for best practices, recommended approach, current guidance, official recommendations, standards, or version-aware external behavior.\n- `$ralplan`, `$deep-interview`, `$team`, or another workflow needs current external evidence before planning or execution can be correct.\n- The task involves an already chosen technology and needs authoritative usage guidance, migration notes, API behavior, lifecycle rules, or current safety guidance.\n\n## Do Not Activate When\n\n- The answer is fully repo-local; use `explore` for codebase facts.\n- The main question is whether to adopt, replace, upgrade, or compare dependencies; use `dependency-expert`.\n- The user only needs implementation against already-grounded requirements; execute directly, or use `$team` when coordinated parallel work is warranted.\n- The task can be answered from stable local project conventions without current external lookup.\n\n## Specialist Routing\n\n1. Use `explore` first for brownfield facts: current code usage, local constraints, versions, config, and integration points.\n2. Use `researcher` for official\u002Fupstream docs, release notes, standards, migration guides, source-backed examples, and current best-practice evidence for an already chosen technology.\n3. Use `dependency-expert` only for adoption\u002Fupgrade\u002Freplacement\u002Fcomparison decisions.\n4. Return to the caller with explicit evidence, uncertainty, and any implementation handoff constraints.\n\n## Source-Quality Rules\n\n- Prefer official documentation, upstream source, release notes, changelogs, standards, and maintainer guidance.\n- Include source URLs for material claims.\n- State date\u002Fversion context for current best-practice claims.\n- Label third-party summaries as supplemental; do not use them before official\u002Fupstream sources.\n- Flag stale, conflicting, undocumented, or version-mismatched evidence.\n- Do not over-fetch: gather the smallest evidence set that can support the decision.\n\n## Workflow\n\n1. Classify the question: conceptual best practice, implementation guidance, migration\u002Fversion guidance, standards\u002Fcompliance guidance, or mixed local + external guidance.\n2. Gather repo-local facts with `explore` when local usage or constraints affect the answer.\n3. Gather external evidence with `researcher` when current or version-aware practice affects correctness.\n4. Synthesize a concise answer with source quality, version\u002Fdate context, caveats, and an implementation or planning handoff.\n5. Stop when the answer is grounded enough for the caller; otherwise report the exact blocker or specialist handoff needed.\n\n## Output Contract\n\n```md\n## Best-Practice Research: \u003Cquestion>\n\n### Direct Recommendation\n\u003Cactionable guidance or decision support>\n\n### Evidence Used\n- Official\u002Fupstream: \u003Csource URL> — \u003Cwhat it establishes>\n- Supplemental, if any: \u003Csource URL> — \u003Cwhy it is secondary>\n\n### Version \u002F Date Context\n\u003Cversions, dates, release channels, or unknowns>\n\n### Repo-Local Context\n\u003Cfacts from explore, or \"not needed\">\n\n### Boundaries \u002F Non-goals\n\u003Cwhat this research does not decide>\n\n### Handoff\n\u003Cplanning\u002Fexecution\u002Ftest implications; name the next workflow — `$ralplan` for planning, `$ultragoal`\u002F`$team`\u002F`executor` for execution — and note that this skill stops here unless the user explicitly switches workflows>\n```\n\n## Stop Rules\n\n- Stop after a source-backed recommendation is reusable by the caller.\n- Stop and route upward if the task becomes dependency comparison, broad architecture, or implementation.\n- Do not continue researching when remaining work would only polish wording rather than change the recommendation.\n- This skill never implements. After delivering the recommendation and handoff, stop; do not modify repo files or repo state. Resume only when the user explicitly switches to a planning or implementation workflow named in the handoff.\n\nTask: {{ARGUMENTS}}\n","# Best-Practice Research\n\nUse this skill when a task depends on current external best practices, version-aware guidance, standards, official recommendations, or upstream behavior. This is a workflow wrapper: it routes evidence gathering and synthesis; it is not a new research authority and it does not replace `researcher`.\n\n## Purpose\n\nProduce a cited, reusable best-practice answer or handoff that separates current external evidence from repo-local facts and dependency-selection decisions. For pre-planning investigation, this is the ordinary first research wrapper: gather official\u002Fupstream evidence, then hand it to `$ralplan` or the caller as planning input. Do not present `$best-practice-research` as a final architecture component or as a validator-gated research loop.\n\n## Terminal By Default\n\nThis skill is terminal and read-only by default. It gathers evidence and produces a cited recommendation with a handoff, then stops. Do not write or edit files, create or amend commits, run mutating commands, or otherwise modify repository state under this skill — even when the question has clear implementation implications. When implementation is warranted, stop and hand off rather than continuing: name `$ralplan` for planning and `$ultragoal`, `$team`, or `executor` for execution, and resume only after the user explicitly switches to that workflow.\n\n## Activate When\n\n- The user asks for best practices, recommended approach, current guidance, official recommendations, standards, or version-aware external behavior.\n- `$ralplan`, `$deep-interview`, `$team`, or another workflow needs current external evidence before planning or execution can be correct.\n- The task involves an already chosen technology and needs authoritative usage guidance, migration notes, API behavior, lifecycle rules, or current safety guidance.\n\n## Do Not Activate When\n\n- The answer is fully repo-local; use `explore` for codebase facts.\n- The main question is whether to adopt, replace, upgrade, or compare dependencies; use `dependency-expert`.\n- The user only needs implementation against already-grounded requirements; execute directly, or use `$team` when coordinated parallel work is warranted.\n- The task can be answered from stable local project conventions without current external lookup.\n\n## Specialist Routing\n\n1. Use `explore` first for brownfield facts: current code usage, local constraints, versions, config, and integration points.\n2. Use `researcher` for official\u002Fupstream docs, release notes, standards, migration guides, source-backed examples, and current best-practice evidence for an already chosen technology.\n3. Use `dependency-expert` only for adoption\u002Fupgrade\u002Freplacement\u002Fcomparison decisions.\n4. Return to the caller with explicit evidence, uncertainty, and any implementation handoff constraints.\n\n## Source-Quality Rules\n\n- Prefer official documentation, upstream source, release notes, changelogs, standards, and maintainer guidance.\n- Include source URLs for material claims.\n- State date\u002Fversion context for current best-practice claims.\n- Label third-party summaries as supplemental; do not use them before official\u002Fupstream sources.\n- Flag stale, conflicting, undocumented, or version-mismatched evidence.\n- Do not over-fetch: gather the smallest evidence set that can support the decision.\n\n## Workflow\n\n1. Classify the question: conceptual best practice, implementation guidance, migration\u002Fversion guidance, standards\u002Fcompliance guidance, or mixed local + external guidance.\n2. Gather repo-local facts with `explore` when local usage or constraints affect the answer.\n3. Gather external evidence with `researcher` when current or version-aware practice affects correctness.\n4. Synthesize a concise answer with source quality, version\u002Fdate context, caveats, and an implementation or planning handoff.\n5. Stop when the answer is grounded enough for the caller; otherwise report the exact blocker or specialist handoff needed.\n\n## Output Contract\n\n```md\n## Best-Practice Research: \u003Cquestion>\n\n### Direct Recommendation\n\u003Cactionable guidance or decision support>\n\n### Evidence Used\n- Official\u002Fupstream: \u003Csource URL> — \u003Cwhat it establishes>\n- Supplemental, if any: \u003Csource URL> — \u003Cwhy it is secondary>\n\n### Version \u002F Date Context\n\u003Cversions, dates, release channels, or unknowns>\n\n### Repo-Local Context\n\u003Cfacts from explore, or \"not needed\">\n\n### Boundaries \u002F Non-goals\n\u003Cwhat this research does not decide>\n\n### Handoff\n\u003Cplanning\u002Fexecution\u002Ftest implications; name the next workflow — `$ralplan` for planning, `$ultragoal`\u002F`$team`\u002F`executor` for execution — and note that this skill stops here unless the user explicitly switches workflows>\n```\n\n## Stop Rules\n\n- Stop after a source-backed recommendation is reusable by the caller.\n- Stop and route upward if the task becomes dependency comparison, broad architecture, or implementation.\n- Do not continue researching when remaining work would only polish wording rather than change the recommendation.\n- This skill never implements. After delivering the recommendation and handoff, stop; do not modify repo files or repo state. Resume only when the user explicitly switches to a planning or implementation workflow named in the handoff.\n\nTask: {{ARGUMENTS}}\n",{"name":5,"description":7,"argument-hint":24},"\u003Ctechnology|decision|practice question>","main","e0232821c4abbcd4338d6018c20fb70f1b74336b","provenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fbest-practice-research",3,"https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit","https:\u002F\u002Fgithub.com\u002FPibomeister","www.eduardopicazoenriquez.com","2026-11-15 00:56:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Pibomeister\u002Fagent-kit --skill best-practice-research",{"tool":39,"command":40},"bunx","bunx skills add Pibomeister\u002Fagent-kit --skill best-practice-research",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Pibomeister\u002Fagent-kit --skill best-practice-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fprovenance\u002Fdonor-snapshots\u002Fomx@cb955b0d5bec\u002Fskills\u002Fbest-practice-research\u002FSKILL.md",true,[],[48,55,60,65,70,75],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7D3JZP2026RGY6XX1MC3NQQ","alpha","Human-started command: it runs only when the human's message begins with `\u002Fak:alpha`. On any other request do not load or follow it; tell the human to type that command. Runs the alpha workflow when a human asks for it.","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid\u002Fminimal\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":56,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7D3JA593Q3RBYJXKVZ37Y2K","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F25-article-tier-outside-vocabulary\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":61,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7D3HQDDAZTAPGWCPGDPNVBQ","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F24-article-without-triggers\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":66,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D3HK074TK3ZWK1ZZNQVPB0","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F23-enforced-by-without-predicate\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":71,"name":50,"nameZh":6,"description":51,"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},"01M7D3HGHQM5C5TBSXBCE2WFHW","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F22-article-without-source-span\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":76,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D3HDV6HMK2ZHRM0P368KNT","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F21-fragment-redeclares-id\u002Fskills\u002Falpha\u002FSKILL.md",[],[]]