[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JK9RG4SWXQR017ZM4JBTJR":3,"skill-same:01M6JK9RG4SWXQR017ZM4JBTJR":74},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":6,"updatedAt":60,"install":61,"resources":73},"01M6JK9RG4SWXQR017ZM4JBTJR","gate-check",null,"Validate readiness to advance between development phases. Produces a PASS\u002FCONCERNS\u002FFAIL verdict with specific blockers and required artifacts.","LongLeo287\u002FOmniClaw","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M6JK75GQ78TSP1ZPXNKK3MCH",9,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fbrain\u002Fknowledge\u002Frepositories\u002Fclaude_code_game_studios\u002F.claude\u002Fskills\u002Fgate_check\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"check","gate check","gate","read","validate","true","with","verdict","readiness","systems","development","write","release","design","technical","grep","advance","polish","Bash","artifacts","2026-11-10 10:12:30",false,"---\nname: gate-check\ndescription: \"Validate readiness to advance between development phases. Produces a PASS\u002FCONCERNS\u002FFAIL verdict with specific blockers and required artifacts.\"\nargument-hint: \"[target-phase: systems-design | technical-setup | pre-production | production | polish | release]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Bash, Write\n---\n\n# Phase Gate Validation\n\nThis skill validates whether the project is ready to advance to the next development\nphase. It checks for required artifacts, quality standards, and blockers.\n\n**Distinct from `\u002Fproject-stage-detect`**: That skill is diagnostic (\"where are we?\").\nThis skill is prescriptive (\"are we ready to advance?\" with a formal verdict).\n\n## Production Stages (7)\n\nThe project progresses through these stages:\n\n1. **Concept** — Brainstorming, game concept document\n2. **Systems Design** — Mapping systems, writing GDDs\n3. **Technical Setup** — Engine config, architecture decisions\n4. **Pre-Production** — Prototyping, vertical slice validation\n5. **Production** — Feature development (Epic\u002FFeature\u002FTask tracking active)\n6. **Polish** — Performance, playtesting, bug fixing\n7. **Release** — Launch prep, certification\n\n**When a gate passes**, write the new stage name to `production\u002Fstage.txt`\n(single line, e.g. `Production`). This updates the status line immediately.\n\n---\n\n## 1. Parse Arguments\n\n- **With argument**: `\u002Fgate-check production` — validate readiness for that specific phase\n- **No argument**: Auto-detect current stage using the same heuristics as\n  `\u002Fproject-stage-detect`, then validate the NEXT phase transition\n\n---\n\n## 2. Phase Gate Definitions\n\n### Gate: Concept → Systems Design\n\n**Required Artifacts:**\n- [ ] `design\u002Fgdd\u002Fgame-concept.md` exists and has content\n- [ ] Game pillars defined (in concept doc or `design\u002Fgdd\u002Fgame-pillars.md`)\n\n**Quality Checks:**\n- [ ] Game concept has been reviewed (`\u002Fdesign-review` verdict not MAJOR REVISION NEEDED)\n- [ ] Core loop is described and understood\n- [ ] Target audience is identified\n\n---\n\n### Gate: Systems Design → Technical Setup\n\n**Required Artifacts:**\n- [ ] Systems index exists at `design\u002Fgdd\u002Fsystems-index.md` with at least MVP systems enumerated\n- [ ] At least 1 GDD in `design\u002Fgdd\u002F` (beyond game-concept.md and systems-index.md)\n\n**Quality Checks:**\n- [ ] GDD(s) pass design review (8 required sections present)\n- [ ] System dependencies are mapped in the systems index\n- [ ] MVP priority tier is defined\n\n---\n\n### Gate: Technical Setup → Pre-Production\n\n**Required Artifacts:**\n- [ ] Engine chosen (CLAUDE.md Technology Stack is not `[CHOOSE]`)\n- [ ] Technical preferences configured (`.claude\u002Fdocs\u002Ftechnical-preferences.md` populated)\n- [ ] At least 1 Architecture Decision Record in `docs\u002Farchitecture\u002F`\n- [ ] Engine reference docs exist in `docs\u002Fengine-reference\u002F`\n\n**Quality Checks:**\n- [ ] Architecture decisions cover core systems (rendering, input, state management)\n- [ ] Technical preferences have naming conventions and performance budgets set\n\n---\n\n### Gate: Pre-Production → Production\n\n**Required Artifacts:**\n- [ ] At least 1 prototype in `prototypes\u002F` with a README\n- [ ] First sprint plan exists in `production\u002Fsprints\u002F`\n- [ ] All MVP-tier GDDs from systems index are complete\n\n**Quality Checks:**\n- [ ] Prototype validates the core loop hypothesis\n- [ ] Sprint plan references real work items from GDDs\n- [ ] Vertical slice scope is defined\n\n---\n\n### Gate: Production → Polish\n\n**Required Artifacts:**\n- [ ] `src\u002F` has active code organized into subsystems\n- [ ] All core mechanics from GDD are implemented (cross-reference `design\u002Fgdd\u002F` with `src\u002F`)\n- [ ] Main gameplay path is playable end-to-end\n- [ ] Test files exist in `tests\u002F`\n- [ ] At least 1 playtest report (or `\u002Fplaytest-report` has been run)\n\n**Quality Checks:**\n- [ ] Tests are passing (run test suite via Bash)\n- [ ] No critical\u002Fblocker bugs in any bug tracker or known issues\n- [ ] Core loop plays as designed (compare to GDD acceptance criteria)\n- [ ] Performance is within budget (check technical-preferences.md targets)\n\n---\n\n### Gate: Polish → Release\n\n**Required Artifacts:**\n- [ ] All features from milestone plan are implemented\n- [ ] Content is complete (all levels, assets, dialogue referenced in design docs exist)\n- [ ] Localization strings are externalized (no hardcoded player-facing text in `src\u002F`)\n- [ ] QA test plan exists\n- [ ] Balance data has been reviewed (`\u002Fbalance-check` run)\n- [ ] Release checklist completed (`\u002Frelease-checklist` or `\u002Flaunch-checklist` run)\n- [ ] Store metadata prepared (if applicable)\n- [ ] Changelog \u002F patch notes drafted\n\n**Quality Checks:**\n- [ ] Full QA pass signed off by `qa-lead`\n- [ ] All tests passing\n- [ ] Performance targets met across all target platforms\n- [ ] No known critical, high, or medium-severity bugs\n- [ ] Accessibility basics covered (remapping, text scaling if applicable)\n- [ ] Localization verified for all target languages\n- [ ] Legal requirements met (EULA, privacy policy, age ratings if applicable)\n- [ ] Build compiles and packages cleanly\n\n---\n\n## 3. Run the Gate Check\n\nFor each item in the target gate:\n\n### Artifact Checks\n- Use `Glob` and `Read` to verify files exist and have meaningful content\n- Don't just check existence — verify the file has real content (not just a template header)\n- For code checks, verify directory structure and file counts\n\n### Quality Checks\n- For test checks: Run the test suite via `Bash` if a test runner is configured\n- For design review checks: `Read` the GDD and check for the 8 required sections\n- For performance checks: `Read` technical-preferences.md and compare against any\n  profiling data in `tests\u002Fperformance\u002F` or recent `\u002Fperf-profile` output\n- For localization checks: `Grep` for hardcoded strings in `src\u002F`\n\n### Cross-Reference Checks\n- Compare `design\u002Fgdd\u002F` documents against `src\u002F` implementations\n- Check that every system referenced in architecture docs has corresponding code\n- Verify sprint plans reference real work items\n\n---\n\n## 4. Collaborative Assessment\n\nFor items that can't be automatically verified, **ask the user**:\n\n- \"I can't automatically verify that the core loop plays well. Has it been playtested?\"\n- \"No playtest report found. Has informal testing been done?\"\n- \"Performance profiling data isn't available. Would you like to run `\u002Fperf-profile`?\"\n\n**Never assume PASS for unverifiable items.** Mark them as MANUAL CHECK NEEDED.\n\n---\n\n## 5. Output the Verdict\n\n```\n## Gate Check: [Current Phase] → [Target Phase]\n\n**Date**: [date]\n**Checked by**: gate-check skill\n\n### Required Artifacts: [X\u002FY present]\n- [x] design\u002Fgdd\u002Fgame-concept.md — exists, 2.4KB\n- [ ] docs\u002Farchitecture\u002F — MISSING (no ADRs found)\n- [x] production\u002Fsprints\u002F — exists, 1 sprint plan\n\n### Quality Checks: [X\u002FY passing]\n- [x] GDD has 8\u002F8 required sections\n- [ ] Tests — FAILED (3 failures in tests\u002Funit\u002F)\n- [?] Core loop playtested — MANUAL CHECK NEEDED\n\n### Blockers\n1. **No Architecture Decision Records** — Run `\u002Farchitecture-decision` to create one\n   covering core system architecture before entering production.\n2. **3 test failures** — Fix failing tests in tests\u002Funit\u002F before advancing.\n\n### Recommendations\n- [Priority actions to resolve blockers]\n- [Optional improvements that aren't blocking]\n\n### Verdict: [PASS \u002F CONCERNS \u002F FAIL]\n- **PASS**: All required artifacts present, all quality checks passing\n- **CONCERNS**: Minor gaps exist but can be addressed during the next phase\n- **FAIL**: Critical blockers must be resolved before advancing\n```\n\n---\n\n## 6. Update Stage on PASS\n\nWhen the verdict is **PASS** and the user confirms they want to advance:\n\n1. Write the new stage name to `production\u002Fstage.txt` (single line, no trailing newline)\n2. This immediately updates the status line for all future sessions\n\nExample: if passing the \"Pre-Production → Production\" gate:\n```bash\necho -n \"Production\" > production\u002Fstage.txt\n```\n\n**Always ask before writing**: \"Gate passed. May I update `production\u002Fstage.txt` to 'Production'?\"\n\n---\n\n## 7. Follow-Up Actions\n\nBased on the verdict, suggest specific next steps:\n\n- **No game concept?** → `\u002Fbrainstorm` to create one\n- **No systems index?** → `\u002Fmap-systems` to decompose the concept into systems\n- **Missing design docs?** → `\u002Freverse-document` or delegate to `game-designer`\n- **Missing ADRs?** → `\u002Farchitecture-decision`\n- **Tests failing?** → delegate to `lead-programmer` or `qa-tester`\n- **No playtest data?** → `\u002Fplaytest-report`\n- **Performance unknown?** → `\u002Fperf-profile`\n- **Not localized?** → `\u002Flocalize`\n- **Ready for release?** → `\u002Flaunch-checklist`\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle:\n\n1. **Scan first**: Check all artifacts and quality gates\n2. **Ask about unknowns**: Don't assume PASS for things you can't verify\n3. **Present findings**: Show the full checklist with status\n4. **User decides**: The verdict is a recommendation — the user makes the final call\n5. **Get approval**: \"May I write this gate check report to production\u002Fgate-checks\u002F?\"\n\n**Never** block a user from advancing — the verdict is advisory. Document the risks\nand let the user decide whether to proceed despite concerns.\n","# Phase Gate Validation\n\nThis skill validates whether the project is ready to advance to the next development\nphase. It checks for required artifacts, quality standards, and blockers.\n\n**Distinct from `\u002Fproject-stage-detect`**: That skill is diagnostic (\"where are we?\").\nThis skill is prescriptive (\"are we ready to advance?\" with a formal verdict).\n\n## Production Stages (7)\n\nThe project progresses through these stages:\n\n1. **Concept** — Brainstorming, game concept document\n2. **Systems Design** — Mapping systems, writing GDDs\n3. **Technical Setup** — Engine config, architecture decisions\n4. **Pre-Production** — Prototyping, vertical slice validation\n5. **Production** — Feature development (Epic\u002FFeature\u002FTask tracking active)\n6. **Polish** — Performance, playtesting, bug fixing\n7. **Release** — Launch prep, certification\n\n**When a gate passes**, write the new stage name to `production\u002Fstage.txt`\n(single line, e.g. `Production`). This updates the status line immediately.\n\n---\n\n## 1. Parse Arguments\n\n- **With argument**: `\u002Fgate-check production` — validate readiness for that specific phase\n- **No argument**: Auto-detect current stage using the same heuristics as\n  `\u002Fproject-stage-detect`, then validate the NEXT phase transition\n\n---\n\n## 2. Phase Gate Definitions\n\n### Gate: Concept → Systems Design\n\n**Required Artifacts:**\n- [ ] `design\u002Fgdd\u002Fgame-concept.md` exists and has content\n- [ ] Game pillars defined (in concept doc or `design\u002Fgdd\u002Fgame-pillars.md`)\n\n**Quality Checks:**\n- [ ] Game concept has been reviewed (`\u002Fdesign-review` verdict not MAJOR REVISION NEEDED)\n- [ ] Core loop is described and understood\n- [ ] Target audience is identified\n\n---\n\n### Gate: Systems Design → Technical Setup\n\n**Required Artifacts:**\n- [ ] Systems index exists at `design\u002Fgdd\u002Fsystems-index.md` with at least MVP systems enumerated\n- [ ] At least 1 GDD in `design\u002Fgdd\u002F` (beyond game-concept.md and systems-index.md)\n\n**Quality Checks:**\n- [ ] GDD(s) pass design review (8 required sections present)\n- [ ] System dependencies are mapped in the systems index\n- [ ] MVP priority tier is defined\n\n---\n\n### Gate: Technical Setup → Pre-Production\n\n**Required Artifacts:**\n- [ ] Engine chosen (CLAUDE.md Technology Stack is not `[CHOOSE]`)\n- [ ] Technical preferences configured (`.claude\u002Fdocs\u002Ftechnical-preferences.md` populated)\n- [ ] At least 1 Architecture Decision Record in `docs\u002Farchitecture\u002F`\n- [ ] Engine reference docs exist in `docs\u002Fengine-reference\u002F`\n\n**Quality Checks:**\n- [ ] Architecture decisions cover core systems (rendering, input, state management)\n- [ ] Technical preferences have naming conventions and performance budgets set\n\n---\n\n### Gate: Pre-Production → Production\n\n**Required Artifacts:**\n- [ ] At least 1 prototype in `prototypes\u002F` with a README\n- [ ] First sprint plan exists in `production\u002Fsprints\u002F`\n- [ ] All MVP-tier GDDs from systems index are complete\n\n**Quality Checks:**\n- [ ] Prototype validates the core loop hypothesis\n- [ ] Sprint plan references real work items from GDDs\n- [ ] Vertical slice scope is defined\n\n---\n\n### Gate: Production → Polish\n\n**Required Artifacts:**\n- [ ] `src\u002F` has active code organized into subsystems\n- [ ] All core mechanics from GDD are implemented (cross-reference `design\u002Fgdd\u002F` with `src\u002F`)\n- [ ] Main gameplay path is playable end-to-end\n- [ ] Test files exist in `tests\u002F`\n- [ ] At least 1 playtest report (or `\u002Fplaytest-report` has been run)\n\n**Quality Checks:**\n- [ ] Tests are passing (run test suite via Bash)\n- [ ] No critical\u002Fblocker bugs in any bug tracker or known issues\n- [ ] Core loop plays as designed (compare to GDD acceptance criteria)\n- [ ] Performance is within budget (check technical-preferences.md targets)\n\n---\n\n### Gate: Polish → Release\n\n**Required Artifacts:**\n- [ ] All features from milestone plan are implemented\n- [ ] Content is complete (all levels, assets, dialogue referenced in design docs exist)\n- [ ] Localization strings are externalized (no hardcoded player-facing text in `src\u002F`)\n- [ ] QA test plan exists\n- [ ] Balance data has been reviewed (`\u002Fbalance-check` run)\n- [ ] Release checklist completed (`\u002Frelease-checklist` or `\u002Flaunch-checklist` run)\n- [ ] Store metadata prepared (if applicable)\n- [ ] Changelog \u002F patch notes drafted\n\n**Quality Checks:**\n- [ ] Full QA pass signed off by `qa-lead`\n- [ ] All tests passing\n- [ ] Performance targets met across all target platforms\n- [ ] No known critical, high, or medium-severity bugs\n- [ ] Accessibility basics covered (remapping, text scaling if applicable)\n- [ ] Localization verified for all target languages\n- [ ] Legal requirements met (EULA, privacy policy, age ratings if applicable)\n- [ ] Build compiles and packages cleanly\n\n---\n\n## 3. Run the Gate Check\n\nFor each item in the target gate:\n\n### Artifact Checks\n- Use `Glob` and `Read` to verify files exist and have meaningful content\n- Don't just check existence — verify the file has real content (not just a template header)\n- For code checks, verify directory structure and file counts\n\n### Quality Checks\n- For test checks: Run the test suite via `Bash` if a test runner is configured\n- For design review checks: `Read` the GDD and check for the 8 required sections\n- For performance checks: `Read` technical-preferences.md and compare against any\n  profiling data in `tests\u002Fperformance\u002F` or recent `\u002Fperf-profile` output\n- For localization checks: `Grep` for hardcoded strings in `src\u002F`\n\n### Cross-Reference Checks\n- Compare `design\u002Fgdd\u002F` documents against `src\u002F` implementations\n- Check that every system referenced in architecture docs has corresponding code\n- Verify sprint plans reference real work items\n\n---\n\n## 4. Collaborative Assessment\n\nFor items that can't be automatically verified, **ask the user**:\n\n- \"I can't automatically verify that the core loop plays well. Has it been playtested?\"\n- \"No playtest report found. Has informal testing been done?\"\n- \"Performance profiling data isn't available. Would you like to run `\u002Fperf-profile`?\"\n\n**Never assume PASS for unverifiable items.** Mark them as MANUAL CHECK NEEDED.\n\n---\n\n## 5. Output the Verdict\n\n```\n## Gate Check: [Current Phase] → [Target Phase]\n\n**Date**: [date]\n**Checked by**: gate-check skill\n\n### Required Artifacts: [X\u002FY present]\n- [x] design\u002Fgdd\u002Fgame-concept.md — exists, 2.4KB\n- [ ] docs\u002Farchitecture\u002F — MISSING (no ADRs found)\n- [x] production\u002Fsprints\u002F — exists, 1 sprint plan\n\n### Quality Checks: [X\u002FY passing]\n- [x] GDD has 8\u002F8 required sections\n- [ ] Tests — FAILED (3 failures in tests\u002Funit\u002F)\n- [?] Core loop playtested — MANUAL CHECK NEEDED\n\n### Blockers\n1. **No Architecture Decision Records** — Run `\u002Farchitecture-decision` to create one\n   covering core system architecture before entering production.\n2. **3 test failures** — Fix failing tests in tests\u002Funit\u002F before advancing.\n\n### Recommendations\n- [Priority actions to resolve blockers]\n- [Optional improvements that aren't blocking]\n\n### Verdict: [PASS \u002F CONCERNS \u002F FAIL]\n- **PASS**: All required artifacts present, all quality checks passing\n- **CONCERNS**: Minor gaps exist but can be addressed during the next phase\n- **FAIL**: Critical blockers must be resolved before advancing\n```\n\n---\n\n## 6. Update Stage on PASS\n\nWhen the verdict is **PASS** and the user confirms they want to advance:\n\n1. Write the new stage name to `production\u002Fstage.txt` (single line, no trailing newline)\n2. This immediately updates the status line for all future sessions\n\nExample: if passing the \"Pre-Production → Production\" gate:\n```bash\necho -n \"Production\" > production\u002Fstage.txt\n```\n\n**Always ask before writing**: \"Gate passed. May I update `production\u002Fstage.txt` to 'Production'?\"\n\n---\n\n## 7. Follow-Up Actions\n\nBased on the verdict, suggest specific next steps:\n\n- **No game concept?** → `\u002Fbrainstorm` to create one\n- **No systems index?** → `\u002Fmap-systems` to decompose the concept into systems\n- **Missing design docs?** → `\u002Freverse-document` or delegate to `game-designer`\n- **Missing ADRs?** → `\u002Farchitecture-decision`\n- **Tests failing?** → delegate to `lead-programmer` or `qa-tester`\n- **No playtest data?** → `\u002Fplaytest-report`\n- **Performance unknown?** → `\u002Fperf-profile`\n- **Not localized?** → `\u002Flocalize`\n- **Ready for release?** → `\u002Flaunch-checklist`\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle:\n\n1. **Scan first**: Check all artifacts and quality gates\n2. **Ask about unknowns**: Don't assume PASS for things you can't verify\n3. **Present findings**: Show the full checklist with status\n4. **User decides**: The verdict is a recommendation — the user makes the final call\n5. **Get approval**: \"May I write this gate check report to production\u002Fgate-checks\u002F?\"\n\n**Never** block a user from advancing — the verdict is advisory. Document the risks\nand let the user decide whether to proceed despite concerns.\n",{"name":5,"description":7,"allowed-tools":49,"argument-hint":50,"user-invocable":51},"Read, Glob, Grep, Bash, Write","[target-phase: systems-design | technical-setup | pre-production | production | polish | release]",true,"main","c173cdffe08e788a99b91928a831b476b8434838","brain\u002Fknowledge\u002Frepositories\u002Fclaude_code_game_studios\u002F.claude\u002Fskills\u002Fgate_check",0,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw","https:\u002F\u002Fportfolio-longleo.vercel.app\u002Flabs\u002Fomniclaw.html","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-09-30 00:58:05",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":51},[63,66,69],{"tool":64,"command":65},"npx","npx skills add LongLeo287\u002FOmniClaw --skill gate-check",{"tool":67,"command":68},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill gate-check",{"tool":70,"command":71},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill gate-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fbrain\u002Fknowledge\u002Frepositories\u002Fclaude_code_game_studios\u002F.claude\u002Fskills\u002Fgate_check\u002FSKILL.md",[],[75,113,134,162,177,204],{"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":93,"publishedAt":44},"01M6JR0KQP4MHT32TN40D9CBFX","UI-UX Pro Max","Advanced UI\u002FUX analysis and generation skills with data-driven patterns. Python scripts (core.py, search.py) for systematic UI pattern extraction, design system generation, and component search from curated data sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fui_ux_pro_max\u002FSKILL.md",[81,82,85,90],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000033","数据分析师",[94,95,96,97,98,99,37,100,101,102,103,104,105,106,107,108,109,110,111,112],"ux","ui","ui ux pro max","max","pro","ui ux","component","search","analysis","team","rd","ui-ux","active","systematic","scripts","pattern extraction","sources","advanced","data-driven",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":44},"01M6JR0EF5AEQHP2FSTB57H05P","shadcn-ui","Expert guidance for integrating and building applications with shadcn\u002Fui components, including component discovery, installation, customization, and best practices.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fshadcn_ui\u002FSKILL.md",[119],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[121,95,122,123,100,124,125,126,127,103,128,129,130,106,131,132,30,133],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","for",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":44},"01M6JR08F51BEN17RHFYX65WVE","zustand_store_ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand_store_ts\u002FSKILL.md",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,30,160,161],"zustand store ts","zustand","store","typescript","microsoft","react","create","state management","state","react state management","management","global","use","patterns","separation","middleware","action","implementing",{"skillNo":163,"name":145,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":44},"01M6JR00TDMVAFFCZXZ04AN7Q7","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand\u002FSKILL.md",[],[145,34,151,168,152,169,170,154,171,156,172,173,174,146,30,175,176,160,161],"code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":187,"publishedAt":44},"01M6JQZSWV4KWJP112G6XHEP44","youtube_summarizer","Automatically fetch YouTube video transcripts, generate structured summaries, and send full transcripts to messaging platforms. Detects YouTube URLs and provides metadata, key insights, and downloadable transcripts.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_summarizer\u002FSKILL.md",[183,186],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},[188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203],"youtube","youtube summarizer","summarizer","generate","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":44},"01M6JQZN3QJB6B77JGKJD62DQT","youtube_clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_clipper\u002FSKILL.md",[],[188,211,212,194,42,213,214,215,216,217,27,35,218,219,220,221,222],"clipper","youtube clipper","下载","视频","生成","关键词","翻译","clip","总结","工具","文案","sonnet"]