[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D9A8GMSDPEVKA1B28SV3VF":3,"skill-same:01M6D9A8GMSDPEVKA1B28SV3VF":101},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6D9A8GMSDPEVKA1B28SV3VF","reconcile-dev-docs",null,"Reconcile development docs by auditing roadmap, todo, history, phase archives, specs, git history, and code reality","GeorgeQLe\u002Fagentic-skills","GeorgeQLe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21134126?v=4","01M6D2JP418S0VGJGF8M93EC3H","George Le","01M6D2JPBAKYD82TA5FS6HKQ3D",1,"MIT","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fdocs-health\u002Fcodex\u002Freconcile-dev-docs\u002Farchive\u002Fv0.2\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"reconcile dev docs","dev","reconcile","docs","page","todo","alignment","roadmap","v0","fix","history","analysis","audit","git","code","development","tasks","2026-11-10 10:12:30",false,"---\nname: reconcile-dev-docs\ndescription: Reconcile development docs by auditing roadmap, todo, history, phase archives, specs, git history, and code reality\ntype: analysis\nversion: v0.2\nrequired_conventions: [alignment-page]\nargument-hint: \"[audit|fix] [tasks|specs|all]\"\n---\n\n# Reconcile Dev Docs\n\nInvoke as `$reconcile-dev-docs`.\n\nAudit or repair development documentation so the roadmap, current work, history, specs, and evidence from git\u002Fcode all tell the same story.\n\n## Process\n\n### 1. Determine Mode and Scope\n\nParse `$ARGUMENTS`:\n\n- **Mode**: `audit` (default, read-only) or `fix` (update development docs only)\n- **Scope**: `all` (default), `tasks`, or `specs`\n\nResolve the canonical development docs:\n\n- `tasks\u002Froadmap.md`\n- `tasks\u002Ftodo.md`\n- `tasks\u002Fmanual-todo.md` (if it exists)\n- `tasks\u002Frecord-todo.md` (if it exists)\n- `tasks\u002Frecurring-todo.md` (if it exists)\n- `tasks\u002Fhistory.md`\n- `tasks\u002Fphases\u002F*.md`\n- `tasks\u002Fideas.md` (if it exists)\n- `specs\u002F*.md` and `specs\u002F*\u002F*.md`\n- `docs\u002Fspecifications\u002F*.md` (fallback specs location)\n\nIf no task docs exist, report that there is nothing to reconcile and recommend `$roadmap` or `$plan-phase` based on available specs.\n\n### 2. Gather Evidence\n\nRead the development docs and collect:\n\n- Roadmap phases, milestone checkboxes, acceptance criteria, manual tasks, record tasks, recurring tasks, and deferred items\n- Current todo phase, checked\u002Funchecked steps, blockers, and review\u002Fresults sections\n- Manual task blockers and `_(blocks: ...)_` \u002F `_(after: ...)_` annotations\n- Record task conditions, non-blocking reasons, evidence paths, and promotion rules\n- Recurring task cadence, last run, next due, evidence paths, and escalation conditions\n- History entries with dates, completed phases\u002Fsteps, commit SHAs, and claimed outcomes\n- Phase archives and their completion summaries\n- Spec titles, statuses, acceptance criteria, and major implementation claims\n\nRead git\u002Fcode evidence:\n\n- `git status --short`\n- `git log --oneline -50`\n- `git log --name-only --since=\u003Clatest relevant doc date>` when timestamps suggest docs may be stale\n- Targeted file existence and `rg` checks for claims marked complete\n\n### 3. Reconcile Rules\n\nClassify findings:\n\n| Severity | Examples |\n|----------|----------|\n| **Error** | Docs contradict each other: roadmap marks a phase done while todo has unchecked required steps; history claims completion but no matching roadmap\u002Ftodo\u002Farchive\u002Fgit evidence exists |\n| **Warning** | Likely drift: recent commits changed areas covered by specs but history\u002Ftodo were not updated; completed phase has no archive; manual blockers remain for completed steps |\n| **Info** | Cleanup opportunities: stale handoff notes, missing links between history entries and commits, specs that should be checked by `$spec-drift` |\n\nUse these specific checks:\n\n- `tasks\u002Ftodo.md` checked steps should be reflected in `tasks\u002Fhistory.md` after shipping.\n- Completed roadmap phases should have corresponding `tasks\u002Fphases\u002Fphase-N.md` archives.\n- The active `tasks\u002Ftodo.md` phase should match the first incomplete roadmap phase.\n- `tasks\u002Fmanual-todo.md` should not contain unchecked blockers for completed todo steps unless the user explicitly overrode them.\n- `tasks\u002Ftodo.md` should not contain condition-gated baseline measurements or future records unless they are current execution work; move clear cases to `tasks\u002Frecord-todo.md`.\n- `tasks\u002Fmanual-todo.md` should not contain non-blocking records unless they require human-only external action tied to a `blocks` or `after` step; move clear cases to `tasks\u002Frecord-todo.md`.\n- `tasks\u002Fmanual-todo.md` should not contain agent-executable work such as repo edits, SDK wiring, generated assets, local commands, tests, audits, or authenticated CLI\u002FAPI operations; move clear cases to `tasks\u002Ftodo.md`.\n- `tasks\u002Frecurring-todo.md` due items should remain advisory unless explicitly promoted into `tasks\u002Ftodo.md`.\n- Recent commits that complete user-facing work should have a matching history entry.\n- Specs whose described areas changed after their last modification date should be flagged for `$spec-drift`.\n- Claimed completed work should have either git evidence, file evidence, test evidence, or an explicit note explaining why evidence is unavailable.\n\n### 4. Fix Mode\n\nIn `fix` mode, apply only unambiguous development-doc changes:\n\n- Append missing factual entries to `tasks\u002Fhistory.md`.\n- Check roadmap milestones only when todo\u002Farchive\u002Fgit evidence all support completion.\n- Create missing `tasks\u002Fphases\u002Fphase-N.md` archives from completed `tasks\u002Ftodo.md` content.\n- Move the next roadmap phase into `tasks\u002Ftodo.md` only when the current phase is clearly complete.\n- Move clearly misclassified non-blocking condition-gated records from `tasks\u002Ftodo.md` or `tasks\u002Fmanual-todo.md` into `tasks\u002Frecord-todo.md`.\n- Move clearly misclassified cadence-based obligations from `tasks\u002Ftodo.md` or `tasks\u002Fmanual-todo.md` into `tasks\u002Frecurring-todo.md`.\n- Move clearly misclassified agent-executable work from `tasks\u002Fmanual-todo.md` into `tasks\u002Ftodo.md` with enough file\u002Fcommand detail for `$exec`.\n- Add unresolved contradictions to `tasks\u002Ftodo.md` under `## Development Docs Reconciliation`.\n- Archive existing `specs\u002F` or `docs\u002Fspecifications\u002F` files before replacing or substantively rewriting them.\n- Write `tasks\u002Freconciliation-report.md` with resolved, deferred, and remaining findings.\n\nAsk before applying any ambiguous change. If already in Plan mode and there are 2-3 concrete choices, prefer `request_user_input`; otherwise ask plainly in chat.\n\n## Output\n\n### Audit Mode\n\n```\n## Dev Docs Reconciliation\n\n### Errors (N)\n- **tasks\u002Ftodo.md** - [problem]. Evidence: [roadmap\u002Fhistory\u002Fgit reference].\n\n### Warnings (N)\n- **specs\u002Ffoo.md** - [problem]. Recommended action: $spec-drift.\n\n### Info (N)\n- **tasks\u002Fhistory.md** - [cleanup opportunity].\n\n### Summary\n- Roadmap\u002Ftodo alignment: [ok|issues]\n- History coverage: [ok|issues]\n- Phase archives: [ok|issues]\n- Spec freshness: [ok|issues]\n- Recommended next action: [specific skill or fix plan]\n```\n\n### Fix Mode\n\nReport the same sections plus:\n\n```\n### Fixed\n- [x] [file] - [change made]\n\n### Deferred\n- [ ] [finding requiring user judgment]\n```\n\n## Constraints\n\n- Read-only by default.\n- In `fix` mode, modify only development docs under `tasks\u002F`, `specs\u002F`, or `docs\u002Fspecifications\u002F`; archive existing spec documents before replacement per the Archive-First Replacement Policy.\n- Do not modify code, research docs, kanban cards, git history, or deployment state.\n- Do not rewrite or delete old `tasks\u002Fhistory.md` entries; append corrections or superseding notes.\n- Do not uncheck completed work automatically. Report unsupported completion claims unless the user approves the correction.\n- Treat `tasks\u002Froadmap.md` as the strategic source of truth, `tasks\u002Ftodo.md` as the active execution contract, `tasks\u002Fmanual-todo.md` as human-only external step-linked work, `tasks\u002Frecord-todo.md` and `tasks\u002Frecurring-todo.md` as advisory surfaces, and `tasks\u002Fhistory.md` as append-only evidence.\n\n## Alignment Page\n\nBy default, this skill reports results inline and writes only its normal durable artifacts (for example `tasks\u002F*.md`, reports, queues, benchmark notes, status docs, or other skill-specific files). Do not build an alignment page automatically. Create `alignment\u002Freconcile-dev-docs-{topic}.html` only when the user explicitly requests an alignment page or when you explicitly identify a concrete clarification\u002Freview need that cannot be handled cleanly inline; when you create one, follow `ALIGNMENT-PAGE.md` in this skill's directory.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","# Reconcile Dev Docs\n\nInvoke as `$reconcile-dev-docs`.\n\nAudit or repair development documentation so the roadmap, current work, history, specs, and evidence from git\u002Fcode all tell the same story.\n\n## Process\n\n### 1. Determine Mode and Scope\n\nParse `$ARGUMENTS`:\n\n- **Mode**: `audit` (default, read-only) or `fix` (update development docs only)\n- **Scope**: `all` (default), `tasks`, or `specs`\n\nResolve the canonical development docs:\n\n- `tasks\u002Froadmap.md`\n- `tasks\u002Ftodo.md`\n- `tasks\u002Fmanual-todo.md` (if it exists)\n- `tasks\u002Frecord-todo.md` (if it exists)\n- `tasks\u002Frecurring-todo.md` (if it exists)\n- `tasks\u002Fhistory.md`\n- `tasks\u002Fphases\u002F*.md`\n- `tasks\u002Fideas.md` (if it exists)\n- `specs\u002F*.md` and `specs\u002F*\u002F*.md`\n- `docs\u002Fspecifications\u002F*.md` (fallback specs location)\n\nIf no task docs exist, report that there is nothing to reconcile and recommend `$roadmap` or `$plan-phase` based on available specs.\n\n### 2. Gather Evidence\n\nRead the development docs and collect:\n\n- Roadmap phases, milestone checkboxes, acceptance criteria, manual tasks, record tasks, recurring tasks, and deferred items\n- Current todo phase, checked\u002Funchecked steps, blockers, and review\u002Fresults sections\n- Manual task blockers and `_(blocks: ...)_` \u002F `_(after: ...)_` annotations\n- Record task conditions, non-blocking reasons, evidence paths, and promotion rules\n- Recurring task cadence, last run, next due, evidence paths, and escalation conditions\n- History entries with dates, completed phases\u002Fsteps, commit SHAs, and claimed outcomes\n- Phase archives and their completion summaries\n- Spec titles, statuses, acceptance criteria, and major implementation claims\n\nRead git\u002Fcode evidence:\n\n- `git status --short`\n- `git log --oneline -50`\n- `git log --name-only --since=\u003Clatest relevant doc date>` when timestamps suggest docs may be stale\n- Targeted file existence and `rg` checks for claims marked complete\n\n### 3. Reconcile Rules\n\nClassify findings:\n\n| Severity | Examples |\n|----------|----------|\n| **Error** | Docs contradict each other: roadmap marks a phase done while todo has unchecked required steps; history claims completion but no matching roadmap\u002Ftodo\u002Farchive\u002Fgit evidence exists |\n| **Warning** | Likely drift: recent commits changed areas covered by specs but history\u002Ftodo were not updated; completed phase has no archive; manual blockers remain for completed steps |\n| **Info** | Cleanup opportunities: stale handoff notes, missing links between history entries and commits, specs that should be checked by `$spec-drift` |\n\nUse these specific checks:\n\n- `tasks\u002Ftodo.md` checked steps should be reflected in `tasks\u002Fhistory.md` after shipping.\n- Completed roadmap phases should have corresponding `tasks\u002Fphases\u002Fphase-N.md` archives.\n- The active `tasks\u002Ftodo.md` phase should match the first incomplete roadmap phase.\n- `tasks\u002Fmanual-todo.md` should not contain unchecked blockers for completed todo steps unless the user explicitly overrode them.\n- `tasks\u002Ftodo.md` should not contain condition-gated baseline measurements or future records unless they are current execution work; move clear cases to `tasks\u002Frecord-todo.md`.\n- `tasks\u002Fmanual-todo.md` should not contain non-blocking records unless they require human-only external action tied to a `blocks` or `after` step; move clear cases to `tasks\u002Frecord-todo.md`.\n- `tasks\u002Fmanual-todo.md` should not contain agent-executable work such as repo edits, SDK wiring, generated assets, local commands, tests, audits, or authenticated CLI\u002FAPI operations; move clear cases to `tasks\u002Ftodo.md`.\n- `tasks\u002Frecurring-todo.md` due items should remain advisory unless explicitly promoted into `tasks\u002Ftodo.md`.\n- Recent commits that complete user-facing work should have a matching history entry.\n- Specs whose described areas changed after their last modification date should be flagged for `$spec-drift`.\n- Claimed completed work should have either git evidence, file evidence, test evidence, or an explicit note explaining why evidence is unavailable.\n\n### 4. Fix Mode\n\nIn `fix` mode, apply only unambiguous development-doc changes:\n\n- Append missing factual entries to `tasks\u002Fhistory.md`.\n- Check roadmap milestones only when todo\u002Farchive\u002Fgit evidence all support completion.\n- Create missing `tasks\u002Fphases\u002Fphase-N.md` archives from completed `tasks\u002Ftodo.md` content.\n- Move the next roadmap phase into `tasks\u002Ftodo.md` only when the current phase is clearly complete.\n- Move clearly misclassified non-blocking condition-gated records from `tasks\u002Ftodo.md` or `tasks\u002Fmanual-todo.md` into `tasks\u002Frecord-todo.md`.\n- Move clearly misclassified cadence-based obligations from `tasks\u002Ftodo.md` or `tasks\u002Fmanual-todo.md` into `tasks\u002Frecurring-todo.md`.\n- Move clearly misclassified agent-executable work from `tasks\u002Fmanual-todo.md` into `tasks\u002Ftodo.md` with enough file\u002Fcommand detail for `$exec`.\n- Add unresolved contradictions to `tasks\u002Ftodo.md` under `## Development Docs Reconciliation`.\n- Archive existing `specs\u002F` or `docs\u002Fspecifications\u002F` files before replacing or substantively rewriting them.\n- Write `tasks\u002Freconciliation-report.md` with resolved, deferred, and remaining findings.\n\nAsk before applying any ambiguous change. If already in Plan mode and there are 2-3 concrete choices, prefer `request_user_input`; otherwise ask plainly in chat.\n\n## Output\n\n### Audit Mode\n\n```\n## Dev Docs Reconciliation\n\n### Errors (N)\n- **tasks\u002Ftodo.md** - [problem]. Evidence: [roadmap\u002Fhistory\u002Fgit reference].\n\n### Warnings (N)\n- **specs\u002Ffoo.md** - [problem]. Recommended action: $spec-drift.\n\n### Info (N)\n- **tasks\u002Fhistory.md** - [cleanup opportunity].\n\n### Summary\n- Roadmap\u002Ftodo alignment: [ok|issues]\n- History coverage: [ok|issues]\n- Phase archives: [ok|issues]\n- Spec freshness: [ok|issues]\n- Recommended next action: [specific skill or fix plan]\n```\n\n### Fix Mode\n\nReport the same sections plus:\n\n```\n### Fixed\n- [x] [file] - [change made]\n\n### Deferred\n- [ ] [finding requiring user judgment]\n```\n\n## Constraints\n\n- Read-only by default.\n- In `fix` mode, modify only development docs under `tasks\u002F`, `specs\u002F`, or `docs\u002Fspecifications\u002F`; archive existing spec documents before replacement per the Archive-First Replacement Policy.\n- Do not modify code, research docs, kanban cards, git history, or deployment state.\n- Do not rewrite or delete old `tasks\u002Fhistory.md` entries; append corrections or superseding notes.\n- Do not uncheck completed work automatically. Report unsupported completion claims unless the user approves the correction.\n- Treat `tasks\u002Froadmap.md` as the strategic source of truth, `tasks\u002Ftodo.md` as the active execution contract, `tasks\u002Fmanual-todo.md` as human-only external step-linked work, `tasks\u002Frecord-todo.md` and `tasks\u002Frecurring-todo.md` as advisory surfaces, and `tasks\u002Fhistory.md` as append-only evidence.\n\n## Alignment Page\n\nBy default, this skill reports results inline and writes only its normal durable artifacts (for example `tasks\u002F*.md`, reports, queues, benchmark notes, status docs, or other skill-specific files). Do not build an alignment page automatically. Create `alignment\u002Freconcile-dev-docs-{topic}.html` only when the user explicitly requests an alignment page or when you explicitly identify a concrete clarification\u002Freview need that cannot be handled cleanly inline; when you create one, follow `ALIGNMENT-PAGE.md` in this skill's directory.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":30,"version":41,"description":7,"argument-hint":42,"required_conventions":43},"v0.2","[audit|fix] [tasks|specs|all]",[44],"alignment-page","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fdocs-health\u002Fcodex\u002Freconcile-dev-docs\u002Farchive\u002Fv0.2",0,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills","https:\u002F\u002Fagentic-skills-blush.vercel.app","https:\u002F\u002Fgithub.com\u002FGeorgeQLe","georgeqle.com","George Le is a futurist and serial tech entrepreneur who wants to work toward a world where humanity is free from robotic tasks.","2026-11-10 04:07:24",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill reconcile-dev-docs",{"tool":61,"command":62},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill reconcile-dev-docs",{"tool":64,"command":65},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill reconcile-dev-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fdocs-health\u002Fcodex\u002Freconcile-dev-docs\u002Farchive\u002Fv0.2\u002FSKILL.md",true,[69,75,79,83,87,91,97],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"agents\u002Fdistillate-compressor.md","REFERENCE","参考文档",4951,"https:\u002F\u002Fgithub.com\u002Ftonygomes-wq\u002Fevo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-distillator\u002Fagents\u002Fdistillate-compressor.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"agents\u002Fround-trip-reconstructor.md",2802,"https:\u002F\u002Fgithub.com\u002Ftonygomes-wq\u002Fevo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-distillator\u002Fagents\u002Fround-trip-reconstructor.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"resources\u002Fcompression-rules.md",2662,"https:\u002F\u002Fgithub.com\u002Ftonygomes-wq\u002Fevo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-distillator\u002Fresources\u002Fcompression-rules.md",{"path":84,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":85,"sourceHtmlUrl":86},"resources\u002Fdistillate-format-reference.md",11942,"https:\u002F\u002Fgithub.com\u002Ftonygomes-wq\u002Fevo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-distillator\u002Fresources\u002Fdistillate-format-reference.md",{"path":88,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":89,"sourceHtmlUrl":90},"resources\u002Fsplitting-strategy.md",3337,"https:\u002F\u002Fgithub.com\u002Ftonygomes-wq\u002Fevo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-distillator\u002Fresources\u002Fsplitting-strategy.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fanalyze_sources.py","SCRIPT","脚本",9912,"https:\u002F\u002Fgithub.com\u002Ftonygomes-wq\u002Fevo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-distillator\u002Fscripts\u002Fanalyze_sources.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Ftests\u002Ftest_analyze_sources.py",7723,"https:\u002F\u002Fgithub.com\u002Ftonygomes-wq\u002Fevo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-distillator\u002Fscripts\u002Ftests\u002Ftest_analyze_sources.py",[102,114,124,136,151,162],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":36},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[109,110,111,112,27,113],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":36},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[121,122,123,113,111,27],"deck install valid","deck","install",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":36},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[131,132,133,113,134,135,111,27],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":147,"publishedAt":36},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[148,149,113,134,27,150,111],"codex missing skill valid","missing","fallback",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":36},"01M6G0N7PC0EKFD40ZWQAXSAQ9","codex-base-skill-fallback-valid","Valid Codex base skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-base-skill-fallback\u002FSKILL.md",[157],{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},[113,134,150,159,160,161,27,111],"base skill","codex base skill fallback valid","base",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":36},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[113,133,132,169,135,27,111],"claude pack guard valid"]