[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EKTF2SRN4PAF55PJ3BMBBA":3,"skill-same:01M6EKTF2SRN4PAF55PJ3BMBBA":86},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6EKTF2SRN4PAF55PJ3BMBBA","architecture-navigator",null,"Understand and navigate the DevPrep AI 7-folder architecture. Use this skill when asked about code organization, where to place new features, what modules exist, or when starting development tasks that need architecture context. Auto-triggers on keywords like \"where should\", \"add module\", \"architecture\", \"structure\", \"organize\", \"place code\", \"what modules\".","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fariegoldkin\u002Farchitecture-navigator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"architecture navigator","navigator","architecture","organization","understand","add","add module","module","triggers","structure","organize","modules","auto","use","context","code","development","tasks","2026-11-10 10:12:30",false,"---\nname: architecture-navigator\ndescription: Understand and navigate the DevPrep AI 7-folder architecture. Use this skill when asked about code organization, where to place new features, what modules exist, or when starting development tasks that need architecture context. Auto-triggers on keywords like \"where should\", \"add module\", \"architecture\", \"structure\", \"organize\", \"place code\", \"what modules\".\n---\n\n# Architecture Navigator\n\n## Overview\n\nProvide instant architecture intelligence for the DevPrep AI codebase. Generate architecture maps, answer placement questions (\"where should X go?\"), and validate code organization against the 7-folder structure. This skill eliminates the need to manually read architecture documentation at conversation start.\n\n## Core Capabilities\n\n### 1. Architecture Scanning\n\nWhen starting a development conversation or when explicitly requested, scan the codebase to generate a real-time architecture map.\n\n**How to scan:**\n\n```bash\n# Run the architecture scanner from project root\nbash .\u002F.claude\u002Fskills\u002Farchitecture-navigator\u002Fscripts\u002Fscan_architecture.sh\n```\n\nThe scanner will output:\n- **7-Folder Structure**: modules\u002F, shared\u002F, lib\u002F, store\u002F, types\u002F, styles\u002F, app\u002F\n- **Module List**: All feature modules with file counts\n- **Key Locations**: API layer, state management, UI components\n- **Quick Stats**: Total files, module count, component count\n\n**When to scan:**\n- At the start of development conversations about architecture\n- When asked \"what modules exist?\" or \"what's the structure?\"\n- Before suggesting where new code should go\n- When validating architecture compliance\n\n**Output format:** Compact markdown summary (~50-100 lines) showing the current architecture state.\n\n---\n\n### 2. Interactive Placement Queries\n\nAnswer \"where should X go?\" questions using the 7-folder placement rules.\n\n**Decision tree:**\n\n1. **Is it a route\u002Fpage?** → `app\u002F` (but keep minimal, import from modules\u002F)\n2. **Is it feature-specific?** → `modules\u002F{feature}\u002F`\n3. **Is it reusable UI\u002Flogic?** → `shared\u002F`\n4. **Is it external integration?** → `lib\u002F`\n5. **Is it global state?** → `store\u002F`\n6. **Is it a shared type?** → `types\u002F`\n7. **Is it pure styling?** → `styles\u002F`\n\n**Example queries and responses:**\n\n| User Query | Response |\n|------------|----------|\n| \"Where should social login go?\" | `modules\u002Fauth\u002F` - Feature-specific authentication logic |\n| \"Where should I add payment processing?\" | `modules\u002Fpayments\u002F` - New feature module for payment domain logic |\n| \"Where do reusable buttons go?\" | `shared\u002Fcomponents\u002Fui\u002FButton.tsx` - Reusable UI component |\n| \"Where's the Claude AI integration?\" | `lib\u002Fclaude\u002F` - External service integration |\n| \"Where should shopping cart state go?\" | `store\u002FcartStore.ts` - Global state management |\n| \"Where do API types go?\" | `types\u002Fai\u002Fapi.ts` - Shared TypeScript definitions |\n\n**For detailed rules**, reference `references\u002Farchitecture-rules.md` which includes:\n- Complete placement rules for all 7 folders\n- Import direction rules (what can import what)\n- Forbidden patterns (circular dependencies, wrong imports)\n- Decision tree for complex placement questions\n- Common examples and edge cases\n\n---\n\n### 3. Module Discovery\n\nList existing modules and explain their purpose when asked.\n\n**How to discover modules:**\n\n```bash\n# Quick module list\nls -1 frontend\u002Fsrc\u002Fmodules\u002F\n\n# With file counts\nfind frontend\u002Fsrc\u002Fmodules\u002F -mindepth 1 -maxdepth 1 -type d -exec sh -c 'echo -n \"{}:\" && find \"{}\" -name \"*.ts*\" | wc -l' \\;\n```\n\n**Common questions:**\n- \"What modules exist?\" → Run module discovery\n- \"Where does authentication live?\" → Check modules\u002F for auth-related folders\n- \"What features are implemented?\" → Scan modules\u002F directory\n\n---\n\n### 4. Architecture Validation\n\nValidate that code follows the 7-folder structure rules.\n\n**What to check:**\n- ✅ Routes in `app\u002F` are minimal (just imports)\n- ✅ Business logic is in `modules\u002F`, not `app\u002F`\n- ✅ Shared components are in `shared\u002F`, not duplicated\n- ✅ External integrations are in `lib\u002F`\n- ✅ Global state is in `store\u002F`\n- ✅ Imports follow allowed directions (see architecture-rules.md)\n\n**Validation commands:**\n\n```bash\n# Check for business logic in app\u002F (should be minimal)\ngrep -r \"useState\\|useEffect\\|async function\" frontend\u002Fsrc\u002Fapp\u002F\n\n# Check for cross-module imports (forbidden)\ngrep -r \"from.*modules\u002F\" frontend\u002Fsrc\u002Fmodules\u002F\n\n# Check for modules importing from shared (allowed)\ngrep -r \"from.*shared\u002F\" frontend\u002Fsrc\u002Fmodules\u002F\n```\n\n---\n\n## Workflow: Using This Skill\n\n### Scenario 1: Conversation Start\n\nWhen a development conversation begins, proactively scan the architecture:\n\n1. Run `scripts\u002Fscan_architecture.sh` to generate current architecture map\n2. Present the map concisely (don't overwhelm with details)\n3. Use this context for subsequent placement questions\n\n### Scenario 2: Placement Questions\n\nWhen asked \"where should X go?\":\n\n1. Identify the nature of the code (feature, reusable, integration, etc.)\n2. Apply the decision tree from `references\u002Farchitecture-rules.md`\n3. Provide specific path recommendation\n4. Explain WHY (which rule applies)\n\n**Example:**\n\n```\nUser: \"Where should I add OAuth authentication?\"\n\nResponse:\nOAuth authentication should go in `modules\u002Fauth\u002Foauth\u002F`:\n- It's feature-specific (authentication domain)\n- It belongs in modules\u002F (not reusable across other features)\n- Structure: modules\u002Fauth\u002Foauth\u002FGoogleAuth.tsx, OAuthProvider.tsx, etc.\n\nThe OAuth client setup (SDK wrapper) should go in `lib\u002Foauth\u002Fclient.ts` (external integration).\n```\n\n### Scenario 3: New Feature Module\n\nWhen creating a new feature module:\n\n1. Confirm it's truly a feature (domain-specific, not cross-cutting)\n2. Create structure: `modules\u002F{feature-name}\u002F`\n3. Recommend typical structure:\n   ```\n   modules\u002F{feature}\u002F\n   ├── components\u002F     - Feature-specific UI\n   ├── hooks\u002F          - Feature-specific hooks\n   ├── utils\u002F          - Feature-specific utilities\n   └── types.ts        - Feature-specific types (if not shared)\n   ```\n4. Remind about import rules (can import from shared\u002F, lib\u002F, store\u002F, types\u002F)\n\n---\n\n## Auto-Trigger Keywords\n\nThis skill automatically activates when these phrases are detected:\n\n- \"where should\"\n- \"add module\"\n- \"architecture\"\n- \"structure\"\n- \"organize\"\n- \"place code\"\n- \"what modules\"\n- \"where does [X] live\"\n- \"where's the API\"\n- \"folder structure\"\n\n**Manual invocation:** Use `\u002Farchitecture` or explicitly request \"scan the architecture\".\n\n---\n\n## Resources\n\n### scripts\u002Fscan_architecture.sh\n\nFast bash script that scans the 7-folder structure and generates a markdown architecture map. Outputs module list, key locations, and quick stats.\n\n**Usage:**\n```bash\nbash scripts\u002Fscan_architecture.sh [project-root]\n```\n\n**Output:** Compact markdown summary (~50-100 lines) suitable for loading into context.\n\n### references\u002Farchitecture-rules.md\n\nComprehensive placement rules for the 7-folder architecture. Reference this document when:\n- Answering complex placement questions\n- Validating architecture compliance\n- Explaining import direction rules\n- Handling edge cases or ambiguous scenarios\n\n**Key sections:**\n- 7-Folder structure overview\n- Detailed placement rules for each folder\n- Import direction rules (what can import what)\n- Forbidden patterns\n- Decision tree for placement\n- Common examples table\n\n---\n\n## Best Practices\n\n1. **Start with scanning**: Generate architecture map at conversation start for context\n2. **Be specific**: Always provide exact paths, not just folder names\n3. **Explain reasoning**: Don't just say \"put it in modules\u002F\", explain WHY\n4. **Reference rules**: Point to `architecture-rules.md` for detailed justification\n5. **Validate imports**: Check that suggested placements respect import direction rules\n6. **Detect drift**: Flag when actual code structure deviates from documented architecture\n7. **Keep it concise**: Architecture maps should be scannable (~50-100 lines)\n\n---\n\n## Example Usage\n\n**User**: \"I want to add a notification system that shows toast messages across the app.\"\n\n**Response**:\n\nLet me scan the current architecture first:\n\n```bash\nbash .\u002F.claude\u002Fskills\u002Farchitecture-navigator\u002Fscripts\u002Fscan_architecture.sh\n```\n\n[Architecture map output]\n\nFor a global notification system with toast messages:\n\n1. **Toast UI Component** → `shared\u002Fcomponents\u002FToast.tsx` (reusable UI)\n2. **Notification State** → `store\u002FuiStore.ts` (global state for managing active toasts)\n3. **Toast Hook** → `shared\u002Fhooks\u002FuseToast.ts` (convenient API: `useToast().show()`)\n\n**Reasoning:**\n- Toast component is reusable across all features → shared\u002F\n- Notification state is global (not feature-specific) → store\u002F\n- Hook provides ergonomic API and is reusable → shared\u002F\n\n**Import flow:**\n- Features call `useToast()` from `shared\u002Fhooks\u002F`\n- Hook accesses `store\u002FuiStore.ts`\n- Hook renders `shared\u002Fcomponents\u002FToast.tsx`\n\nThis follows the architecture rules: modules\u002F → shared\u002F → store\u002F (allowed import direction).\n","# Architecture Navigator\n\n## Overview\n\nProvide instant architecture intelligence for the DevPrep AI codebase. Generate architecture maps, answer placement questions (\"where should X go?\"), and validate code organization against the 7-folder structure. This skill eliminates the need to manually read architecture documentation at conversation start.\n\n## Core Capabilities\n\n### 1. Architecture Scanning\n\nWhen starting a development conversation or when explicitly requested, scan the codebase to generate a real-time architecture map.\n\n**How to scan:**\n\n```bash\n# Run the architecture scanner from project root\nbash .\u002F.claude\u002Fskills\u002Farchitecture-navigator\u002Fscripts\u002Fscan_architecture.sh\n```\n\nThe scanner will output:\n- **7-Folder Structure**: modules\u002F, shared\u002F, lib\u002F, store\u002F, types\u002F, styles\u002F, app\u002F\n- **Module List**: All feature modules with file counts\n- **Key Locations**: API layer, state management, UI components\n- **Quick Stats**: Total files, module count, component count\n\n**When to scan:**\n- At the start of development conversations about architecture\n- When asked \"what modules exist?\" or \"what's the structure?\"\n- Before suggesting where new code should go\n- When validating architecture compliance\n\n**Output format:** Compact markdown summary (~50-100 lines) showing the current architecture state.\n\n---\n\n### 2. Interactive Placement Queries\n\nAnswer \"where should X go?\" questions using the 7-folder placement rules.\n\n**Decision tree:**\n\n1. **Is it a route\u002Fpage?** → `app\u002F` (but keep minimal, import from modules\u002F)\n2. **Is it feature-specific?** → `modules\u002F{feature}\u002F`\n3. **Is it reusable UI\u002Flogic?** → `shared\u002F`\n4. **Is it external integration?** → `lib\u002F`\n5. **Is it global state?** → `store\u002F`\n6. **Is it a shared type?** → `types\u002F`\n7. **Is it pure styling?** → `styles\u002F`\n\n**Example queries and responses:**\n\n| User Query | Response |\n|------------|----------|\n| \"Where should social login go?\" | `modules\u002Fauth\u002F` - Feature-specific authentication logic |\n| \"Where should I add payment processing?\" | `modules\u002Fpayments\u002F` - New feature module for payment domain logic |\n| \"Where do reusable buttons go?\" | `shared\u002Fcomponents\u002Fui\u002FButton.tsx` - Reusable UI component |\n| \"Where's the Claude AI integration?\" | `lib\u002Fclaude\u002F` - External service integration |\n| \"Where should shopping cart state go?\" | `store\u002FcartStore.ts` - Global state management |\n| \"Where do API types go?\" | `types\u002Fai\u002Fapi.ts` - Shared TypeScript definitions |\n\n**For detailed rules**, reference `references\u002Farchitecture-rules.md` which includes:\n- Complete placement rules for all 7 folders\n- Import direction rules (what can import what)\n- Forbidden patterns (circular dependencies, wrong imports)\n- Decision tree for complex placement questions\n- Common examples and edge cases\n\n---\n\n### 3. Module Discovery\n\nList existing modules and explain their purpose when asked.\n\n**How to discover modules:**\n\n```bash\n# Quick module list\nls -1 frontend\u002Fsrc\u002Fmodules\u002F\n\n# With file counts\nfind frontend\u002Fsrc\u002Fmodules\u002F -mindepth 1 -maxdepth 1 -type d -exec sh -c 'echo -n \"{}:\" && find \"{}\" -name \"*.ts*\" | wc -l' \\;\n```\n\n**Common questions:**\n- \"What modules exist?\" → Run module discovery\n- \"Where does authentication live?\" → Check modules\u002F for auth-related folders\n- \"What features are implemented?\" → Scan modules\u002F directory\n\n---\n\n### 4. Architecture Validation\n\nValidate that code follows the 7-folder structure rules.\n\n**What to check:**\n- ✅ Routes in `app\u002F` are minimal (just imports)\n- ✅ Business logic is in `modules\u002F`, not `app\u002F`\n- ✅ Shared components are in `shared\u002F`, not duplicated\n- ✅ External integrations are in `lib\u002F`\n- ✅ Global state is in `store\u002F`\n- ✅ Imports follow allowed directions (see architecture-rules.md)\n\n**Validation commands:**\n\n```bash\n# Check for business logic in app\u002F (should be minimal)\ngrep -r \"useState\\|useEffect\\|async function\" frontend\u002Fsrc\u002Fapp\u002F\n\n# Check for cross-module imports (forbidden)\ngrep -r \"from.*modules\u002F\" frontend\u002Fsrc\u002Fmodules\u002F\n\n# Check for modules importing from shared (allowed)\ngrep -r \"from.*shared\u002F\" frontend\u002Fsrc\u002Fmodules\u002F\n```\n\n---\n\n## Workflow: Using This Skill\n\n### Scenario 1: Conversation Start\n\nWhen a development conversation begins, proactively scan the architecture:\n\n1. Run `scripts\u002Fscan_architecture.sh` to generate current architecture map\n2. Present the map concisely (don't overwhelm with details)\n3. Use this context for subsequent placement questions\n\n### Scenario 2: Placement Questions\n\nWhen asked \"where should X go?\":\n\n1. Identify the nature of the code (feature, reusable, integration, etc.)\n2. Apply the decision tree from `references\u002Farchitecture-rules.md`\n3. Provide specific path recommendation\n4. Explain WHY (which rule applies)\n\n**Example:**\n\n```\nUser: \"Where should I add OAuth authentication?\"\n\nResponse:\nOAuth authentication should go in `modules\u002Fauth\u002Foauth\u002F`:\n- It's feature-specific (authentication domain)\n- It belongs in modules\u002F (not reusable across other features)\n- Structure: modules\u002Fauth\u002Foauth\u002FGoogleAuth.tsx, OAuthProvider.tsx, etc.\n\nThe OAuth client setup (SDK wrapper) should go in `lib\u002Foauth\u002Fclient.ts` (external integration).\n```\n\n### Scenario 3: New Feature Module\n\nWhen creating a new feature module:\n\n1. Confirm it's truly a feature (domain-specific, not cross-cutting)\n2. Create structure: `modules\u002F{feature-name}\u002F`\n3. Recommend typical structure:\n   ```\n   modules\u002F{feature}\u002F\n   ├── components\u002F     - Feature-specific UI\n   ├── hooks\u002F          - Feature-specific hooks\n   ├── utils\u002F          - Feature-specific utilities\n   └── types.ts        - Feature-specific types (if not shared)\n   ```\n4. Remind about import rules (can import from shared\u002F, lib\u002F, store\u002F, types\u002F)\n\n---\n\n## Auto-Trigger Keywords\n\nThis skill automatically activates when these phrases are detected:\n\n- \"where should\"\n- \"add module\"\n- \"architecture\"\n- \"structure\"\n- \"organize\"\n- \"place code\"\n- \"what modules\"\n- \"where does [X] live\"\n- \"where's the API\"\n- \"folder structure\"\n\n**Manual invocation:** Use `\u002Farchitecture` or explicitly request \"scan the architecture\".\n\n---\n\n## Resources\n\n### scripts\u002Fscan_architecture.sh\n\nFast bash script that scans the 7-folder structure and generates a markdown architecture map. Outputs module list, key locations, and quick stats.\n\n**Usage:**\n```bash\nbash scripts\u002Fscan_architecture.sh [project-root]\n```\n\n**Output:** Compact markdown summary (~50-100 lines) suitable for loading into context.\n\n### references\u002Farchitecture-rules.md\n\nComprehensive placement rules for the 7-folder architecture. Reference this document when:\n- Answering complex placement questions\n- Validating architecture compliance\n- Explaining import direction rules\n- Handling edge cases or ambiguous scenarios\n\n**Key sections:**\n- 7-Folder structure overview\n- Detailed placement rules for each folder\n- Import direction rules (what can import what)\n- Forbidden patterns\n- Decision tree for placement\n- Common examples table\n\n---\n\n## Best Practices\n\n1. **Start with scanning**: Generate architecture map at conversation start for context\n2. **Be specific**: Always provide exact paths, not just folder names\n3. **Explain reasoning**: Don't just say \"put it in modules\u002F\", explain WHY\n4. **Reference rules**: Point to `architecture-rules.md` for detailed justification\n5. **Validate imports**: Check that suggested placements respect import direction rules\n6. **Detect drift**: Flag when actual code structure deviates from documented architecture\n7. **Keep it concise**: Architecture maps should be scannable (~50-100 lines)\n\n---\n\n## Example Usage\n\n**User**: \"I want to add a notification system that shows toast messages across the app.\"\n\n**Response**:\n\nLet me scan the current architecture first:\n\n```bash\nbash .\u002F.claude\u002Fskills\u002Farchitecture-navigator\u002Fscripts\u002Fscan_architecture.sh\n```\n\n[Architecture map output]\n\nFor a global notification system with toast messages:\n\n1. **Toast UI Component** → `shared\u002Fcomponents\u002FToast.tsx` (reusable UI)\n2. **Notification State** → `store\u002FuiStore.ts` (global state for managing active toasts)\n3. **Toast Hook** → `shared\u002Fhooks\u002FuseToast.ts` (convenient API: `useToast().show()`)\n\n**Reasoning:**\n- Toast component is reusable across all features → shared\u002F\n- Notification state is global (not feature-specific) → store\u002F\n- Hook provides ergonomic API and is reusable → shared\u002F\n\n**Import flow:**\n- Features call `useToast()` from `shared\u002Fhooks\u002F`\n- Hook accesses `store\u002FuiStore.ts`\n- Hook renders `shared\u002Fcomponents\u002FToast.tsx`\n\nThis follows the architecture rules: modules\u002F → shared\u002F → store\u002F (allowed import direction).\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fariegoldkin\u002Farchitecture-navigator",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill architecture-navigator",{"tool":62,"command":63},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill architecture-navigator",{"tool":65,"command":66},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill architecture-navigator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fariegoldkin\u002Farchitecture-navigator\u002FSKILL.md",true,[70,76,82],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Farchitecture-rules.md","REFERENCE","参考文档",8334,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fariegoldkin\u002Farchitecture-navigator\u002Freferences\u002Farchitecture-rules.md",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fscan_architecture.sh","SCRIPT","脚本",2915,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fariegoldkin\u002Farchitecture-navigator\u002Fscripts\u002Fscan_architecture.sh",{"path":83,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":84,"sourceHtmlUrl":85},"skill-report.json",9519,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fariegoldkin\u002Farchitecture-navigator\u002Fskill-report.json",[87,97,107,116,122,129],{"skillNo":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":93,"publishedAt":42},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[92],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[94,95,96],"model","model hierarchy","model hierarchy skill",{"skillNo":98,"name":99,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":42},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[102],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[104,105,106],"MCP","zoom","zoom mcp",{"skillNo":108,"name":109,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":42},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[113,114,115,105],"sdk","zoom apps sdk","apps",{"skillNo":117,"name":118,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":42},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[118],{"skillNo":123,"name":124,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":42},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[127],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[124],{"skillNo":130,"name":131,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":42},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[131]]