[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EM5NT77ER4510M08SVENAA":3,"skill-same:01M6EM5NT77ER4510M08SVENAA":124},{"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":31,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6EM5NT77ER4510M08SVENAA","repo-docs",null,"This skill should be used when the user asks to \"generate repository documentation\", \"create a README\", \"document API\", \"write architecture docs\", \"add CONTRIBUTING guide\", \"update repo docs\", \"document codebase\", or mentions repository documentation, codebase analysis, or cross-repository integration documentation.","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\u002Fastrabit-cpt\u002Frepo-docs\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"repo docs","repo","docs","analysis","add","document","guide","user","write","README","api","repository","integration","contributing","update","generate","create","documentation","architecture","2026-11-10 10:12:30",false,"---\nname: repo-docs\ndescription: This skill should be used when the user asks to \"generate repository documentation\", \"create a README\", \"document API\", \"write architecture docs\", \"add CONTRIBUTING guide\", \"update repo docs\", \"document codebase\", or mentions repository documentation, codebase analysis, or cross-repository integration documentation.\nversion: 1.0.0\n---\n\n# Repository Documentation\n\nGenerate comprehensive, self-contained documentation for code repositories with awareness of cross-repository integration points and dependencies.\n\n## Purpose\n\nCreate and maintain repository documentation that includes README files, API documentation, contributing guides, and architecture documents. Each generated document is self-contained while explicitly documenting how the repository interacts with other repositories, services, and external dependencies.\n\n## When to Use\n\nTrigger this skill when:\n- User asks to \"generate documentation for this repo\"\n- User mentions \"create\u002Fupdate README\", \"document API\", \"write architecture docs\"\n- User asks about \"how this repo connects to other repos\"\n- User requests \"CONTRIBUTING guide\" or \"setup documentation\"\n- User wants to document integration points with other repositories\n\n## Documentation Workflow\n\n### Phase 1: Repository Analysis\n\nBefore generating documentation, analyze the codebase to understand:\n\n1. **Repository Structure**\n   - Use `Glob` to discover key files: `README.md`, `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`, `pom.xml`, etc.\n   - Identify main source directories (`src\u002F`, `lib\u002F`, `app\u002F`, `internal\u002F`, etc.)\n   - Find configuration files (`.env.example`, `docker\u002F`, `k8s\u002F`, etc.)\n   - Locate existing documentation (`docs\u002F`, `*.md` files)\n\n2. **Cross-Repository Integration Discovery**\n   - Search for imports\u002Frequires referencing other repos (use `Grep` for common patterns)\n   - Look for API client libraries pointing to internal services\n   - Find shared dependencies or monorepo references\n   - Identify external service integrations (databases, APIs, message queues)\n   - Check for `.gitmodules`, `workspace` declarations, or subpackage references\n\n3. **Technology Detection**\n   - Identify primary programming language(s)\n   - Find frameworks and major dependencies\n   - Detect build systems and tooling\n   - Note testing frameworks and CI\u002FCD configuration\n\n### Phase 2: Document Generation\n\nFor each document type, follow the structured templates in `examples\u002F`. Templates contain:\n- Section headers with placeholder content\n- Specific placeholders for integration points\n- Cross-repository dependency sections\n\n**Key Principle:** Every generated document must include an \"Integrations\" or \"Related Repositories\" section that explicitly documents:\n- Which other repositories this repo depends on\n- How this repo is consumed by other repositories\n- External services and dependencies\n- Data flow between repositories\n\n### Phase 3: Existing Document Updates\n\nWhen updating existing documentation:\n1. Read the current document using `Read`\n2. Compare against current codebase state\n3. Identify gaps (missing features, outdated integrations, stale dependencies)\n4. Use `Edit` to update specific sections\n5. Preserve existing voice and formatting where appropriate\n6. Add newly discovered integration points\n\n## Document Types\n\n### README.md\n\nThe primary entry point for the repository. Use `examples\u002FREADME-template.md` as a starting point.\n\nRequired sections:\n- Project title and brief description\n- Integration points with other repositories\n- Quick start \u002F Installation\n- Usage examples\n- API\u002FCLI reference (link to detailed docs if separate)\n- Contributing (link to CONTRIBUTING.md)\n- License\n\n### API Documentation\n\nDocument public APIs, functions, classes, and endpoints. Use `examples\u002FAPI-template.md`.\n\nRequired sections:\n- Overview\n- Authentication\u002FAuthorization\n- Endpoints\u002FFunctions with signatures\n- Request\u002Fresponse examples\n- Error handling\n- Rate limits (if applicable)\n- Integration points with other services\n\n### CONTRIBUTING.md\n\nGuide for contributors. Use `examples\u002FCONTRIBUTING-template.md`.\n\nRequired sections:\n- Prerequisites (other repos to clone, tools to install)\n- Development setup\n- Running tests\n- Code style guidelines\n- Pull request process\n- Related repositories and their roles\n\n### ARCHITECTURE.md\n\nHigh-level design and integration documentation. Use `examples\u002FARCHITECTURE-template.md`.\n\nRequired sections:\n- System overview\n- Component diagram (describe verbally or use Mermaid)\n- Cross-repository architecture\n- Data flow between repositories\n- Design decisions and rationale\n- Scaling considerations\n\n### INTEGRATIONS.md (Optional but Recommended)\n\nDedicated document for cross-repository relationships. Use `examples\u002FINTEGRATIONS-template.md`.\n\nSections:\n- Upstream dependencies (repos\u002Fservices this depends on)\n- Downstream consumers (repos\u002Fservices that depend on this)\n- Sibling repositories (related repos in the same ecosystem)\n- External services\n- Communication protocols between services\n\n## Integration Discovery Guidelines\n\nWhen scanning for integration points, search for:\n\n| Pattern | Indicates |\n|---------|-----------|\n| `from @org\u002F` | Internal package\u002Frepo imports (JS\u002FTS) |\n| `import.*internal` | Internal imports (Python\u002FJava) |\n| `github.com\u002Forg\u002F` | Go module references to other repos |\n| `client.*[Aa]pi` | API clients to other services |\n| `restTemplate` | REST client usage (Java) |\n| `fetch(` or `axios` | HTTP calls to external services |\n| `messaging:` | Spring Cloud\u002FSidecar integrations |\n| `pom.xml` `\u003CartifactId>` | Maven dependencies |\n\nUse `scripts\u002Ffind-integration-points.py` to automate discovery.\n\n## Writing Guidelines\n\n### 1. Be Specific About Integrations\n- Name the repositories explicitly: \"Depends on `user-service` repo for authentication\"\n- Explain the relationship: \"This repo consumes events from `event-bus` via Kafka\"\n- Link to the actual repositories when possible\n\n### 2. Self-Contained Yet Connected\n- Each document should stand alone\n- Cross-reference other documents and repositories explicitly\n- Include enough context for someone new to the broader ecosystem\n\n### 3. Concise and Scannable\n- **Use bullet points** over paragraphs for lists and procedures\n- **Lead with the essential** - put most important information first\n- **Use tables** for reference material (configs, commands, options)\n- **Code over prose** - show examples instead of lengthy explanations\n- **Collapse details** - use collapsible sections or \"expand to read more\" for depth\n- **One concept per section** - avoid mixing multiple topics\n- **Link, don't duplicate** - reference existing docs instead of repeating\n- **Target reading time** - a README should take ~3-5 minutes to scan\n\n### 4. Keep Examples Current\n- Use actual code snippets from the repository\n- Verify commands work before including them\n- Update version numbers and dependency references\n- Keep examples minimal - show only what's needed to understand\n\n### 5. Progressive Detail\n- Lead with high-level overview\n- Link to detailed documentation\n- Provide quick paths to \"just make it work\" and deep dives\n\n## Tools and Utilities\n\n### Scripts\n\nUse scripts in `scripts\u002F` for automation:\n\n- **`find-integration-points.py`** - Scan codebase for references to other repositories\n- **`analyze-repo-structure.py`** - Generate summary of repository structure and dependencies\n\nExecute scripts without reading into context:\n```bash\npython skills\u002Frepo-docs\u002Fscripts\u002Ffind-integration-points.py \u002Fpath\u002Fto\u002Frepo\n```\n\n### References\n\nConsult `references\u002F` for detailed guidance:\n- **`references\u002Fbest-practices.md`** - Repository documentation standards\n- **`references\u002Fintegration-patterns.md`** - Common integration patterns and how to document them\n- **`references\u002Ftech-detection.md`** - Technology detection patterns\n\n## Additional Resources\n\n### Reference Files\n\nFor detailed guidance beyond this core workflow:\n- **`references\u002Fbest-practices.md`** - Industry standards for repository documentation\n- **`references\u002Fintegration-patterns.md`** - Documenting microservices, monorepos, and distributed systems\n- **`references\u002Ftech-detection.md`** - Patterns for identifying technologies and frameworks\n\n### Example Templates\n\nTemplates in `examples\u002F` provide starting points:\n- **`examples\u002FREADME-template.md`** - Standard README structure with integrations section\n- **`examples\u002FAPI-template.md`** - API documentation template\n- **`examples\u002FCONTRIBUTING-template.md`** - Contributor guide template\n- **`examples\u002FARCHITECTURE-template.md`** - Architecture documentation template\n- **`examples\u002FINTEGRATIONS-template.md`** - Dedicated integrations document\n\n### Scripts\n\nUtilities in `scripts\u002F`:\n- **`scripts\u002Ffind-integration-points.py`** - Automated integration discovery\n- **`scripts\u002Fanalyze-repo-structure.py`** - Repository structure analysis\n\n## Quality Checklist\n\nBefore finalizing documentation, verify:\n\n- [ ] All cross-repository dependencies are documented\n- [ ] Integration points are explicitly named and described\n- [ ] Quick start instructions actually work\n- [ ] Code examples are from the actual codebase\n- [ ] Links to other repos are included where applicable\n- [ ] External service dependencies are listed\n- [ ] Setup instructions include dependencies on other repos\n- [ ] Document is readable without access to other repositories\n","# Repository Documentation\n\nGenerate comprehensive, self-contained documentation for code repositories with awareness of cross-repository integration points and dependencies.\n\n## Purpose\n\nCreate and maintain repository documentation that includes README files, API documentation, contributing guides, and architecture documents. Each generated document is self-contained while explicitly documenting how the repository interacts with other repositories, services, and external dependencies.\n\n## When to Use\n\nTrigger this skill when:\n- User asks to \"generate documentation for this repo\"\n- User mentions \"create\u002Fupdate README\", \"document API\", \"write architecture docs\"\n- User asks about \"how this repo connects to other repos\"\n- User requests \"CONTRIBUTING guide\" or \"setup documentation\"\n- User wants to document integration points with other repositories\n\n## Documentation Workflow\n\n### Phase 1: Repository Analysis\n\nBefore generating documentation, analyze the codebase to understand:\n\n1. **Repository Structure**\n   - Use `Glob` to discover key files: `README.md`, `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`, `pom.xml`, etc.\n   - Identify main source directories (`src\u002F`, `lib\u002F`, `app\u002F`, `internal\u002F`, etc.)\n   - Find configuration files (`.env.example`, `docker\u002F`, `k8s\u002F`, etc.)\n   - Locate existing documentation (`docs\u002F`, `*.md` files)\n\n2. **Cross-Repository Integration Discovery**\n   - Search for imports\u002Frequires referencing other repos (use `Grep` for common patterns)\n   - Look for API client libraries pointing to internal services\n   - Find shared dependencies or monorepo references\n   - Identify external service integrations (databases, APIs, message queues)\n   - Check for `.gitmodules`, `workspace` declarations, or subpackage references\n\n3. **Technology Detection**\n   - Identify primary programming language(s)\n   - Find frameworks and major dependencies\n   - Detect build systems and tooling\n   - Note testing frameworks and CI\u002FCD configuration\n\n### Phase 2: Document Generation\n\nFor each document type, follow the structured templates in `examples\u002F`. Templates contain:\n- Section headers with placeholder content\n- Specific placeholders for integration points\n- Cross-repository dependency sections\n\n**Key Principle:** Every generated document must include an \"Integrations\" or \"Related Repositories\" section that explicitly documents:\n- Which other repositories this repo depends on\n- How this repo is consumed by other repositories\n- External services and dependencies\n- Data flow between repositories\n\n### Phase 3: Existing Document Updates\n\nWhen updating existing documentation:\n1. Read the current document using `Read`\n2. Compare against current codebase state\n3. Identify gaps (missing features, outdated integrations, stale dependencies)\n4. Use `Edit` to update specific sections\n5. Preserve existing voice and formatting where appropriate\n6. Add newly discovered integration points\n\n## Document Types\n\n### README.md\n\nThe primary entry point for the repository. Use `examples\u002FREADME-template.md` as a starting point.\n\nRequired sections:\n- Project title and brief description\n- Integration points with other repositories\n- Quick start \u002F Installation\n- Usage examples\n- API\u002FCLI reference (link to detailed docs if separate)\n- Contributing (link to CONTRIBUTING.md)\n- License\n\n### API Documentation\n\nDocument public APIs, functions, classes, and endpoints. Use `examples\u002FAPI-template.md`.\n\nRequired sections:\n- Overview\n- Authentication\u002FAuthorization\n- Endpoints\u002FFunctions with signatures\n- Request\u002Fresponse examples\n- Error handling\n- Rate limits (if applicable)\n- Integration points with other services\n\n### CONTRIBUTING.md\n\nGuide for contributors. Use `examples\u002FCONTRIBUTING-template.md`.\n\nRequired sections:\n- Prerequisites (other repos to clone, tools to install)\n- Development setup\n- Running tests\n- Code style guidelines\n- Pull request process\n- Related repositories and their roles\n\n### ARCHITECTURE.md\n\nHigh-level design and integration documentation. Use `examples\u002FARCHITECTURE-template.md`.\n\nRequired sections:\n- System overview\n- Component diagram (describe verbally or use Mermaid)\n- Cross-repository architecture\n- Data flow between repositories\n- Design decisions and rationale\n- Scaling considerations\n\n### INTEGRATIONS.md (Optional but Recommended)\n\nDedicated document for cross-repository relationships. Use `examples\u002FINTEGRATIONS-template.md`.\n\nSections:\n- Upstream dependencies (repos\u002Fservices this depends on)\n- Downstream consumers (repos\u002Fservices that depend on this)\n- Sibling repositories (related repos in the same ecosystem)\n- External services\n- Communication protocols between services\n\n## Integration Discovery Guidelines\n\nWhen scanning for integration points, search for:\n\n| Pattern | Indicates |\n|---------|-----------|\n| `from @org\u002F` | Internal package\u002Frepo imports (JS\u002FTS) |\n| `import.*internal` | Internal imports (Python\u002FJava) |\n| `github.com\u002Forg\u002F` | Go module references to other repos |\n| `client.*[Aa]pi` | API clients to other services |\n| `restTemplate` | REST client usage (Java) |\n| `fetch(` or `axios` | HTTP calls to external services |\n| `messaging:` | Spring Cloud\u002FSidecar integrations |\n| `pom.xml` `\u003CartifactId>` | Maven dependencies |\n\nUse `scripts\u002Ffind-integration-points.py` to automate discovery.\n\n## Writing Guidelines\n\n### 1. Be Specific About Integrations\n- Name the repositories explicitly: \"Depends on `user-service` repo for authentication\"\n- Explain the relationship: \"This repo consumes events from `event-bus` via Kafka\"\n- Link to the actual repositories when possible\n\n### 2. Self-Contained Yet Connected\n- Each document should stand alone\n- Cross-reference other documents and repositories explicitly\n- Include enough context for someone new to the broader ecosystem\n\n### 3. Concise and Scannable\n- **Use bullet points** over paragraphs for lists and procedures\n- **Lead with the essential** - put most important information first\n- **Use tables** for reference material (configs, commands, options)\n- **Code over prose** - show examples instead of lengthy explanations\n- **Collapse details** - use collapsible sections or \"expand to read more\" for depth\n- **One concept per section** - avoid mixing multiple topics\n- **Link, don't duplicate** - reference existing docs instead of repeating\n- **Target reading time** - a README should take ~3-5 minutes to scan\n\n### 4. Keep Examples Current\n- Use actual code snippets from the repository\n- Verify commands work before including them\n- Update version numbers and dependency references\n- Keep examples minimal - show only what's needed to understand\n\n### 5. Progressive Detail\n- Lead with high-level overview\n- Link to detailed documentation\n- Provide quick paths to \"just make it work\" and deep dives\n\n## Tools and Utilities\n\n### Scripts\n\nUse scripts in `scripts\u002F` for automation:\n\n- **`find-integration-points.py`** - Scan codebase for references to other repositories\n- **`analyze-repo-structure.py`** - Generate summary of repository structure and dependencies\n\nExecute scripts without reading into context:\n```bash\npython skills\u002Frepo-docs\u002Fscripts\u002Ffind-integration-points.py \u002Fpath\u002Fto\u002Frepo\n```\n\n### References\n\nConsult `references\u002F` for detailed guidance:\n- **`references\u002Fbest-practices.md`** - Repository documentation standards\n- **`references\u002Fintegration-patterns.md`** - Common integration patterns and how to document them\n- **`references\u002Ftech-detection.md`** - Technology detection patterns\n\n## Additional Resources\n\n### Reference Files\n\nFor detailed guidance beyond this core workflow:\n- **`references\u002Fbest-practices.md`** - Industry standards for repository documentation\n- **`references\u002Fintegration-patterns.md`** - Documenting microservices, monorepos, and distributed systems\n- **`references\u002Ftech-detection.md`** - Patterns for identifying technologies and frameworks\n\n### Example Templates\n\nTemplates in `examples\u002F` provide starting points:\n- **`examples\u002FREADME-template.md`** - Standard README structure with integrations section\n- **`examples\u002FAPI-template.md`** - API documentation template\n- **`examples\u002FCONTRIBUTING-template.md`** - Contributor guide template\n- **`examples\u002FARCHITECTURE-template.md`** - Architecture documentation template\n- **`examples\u002FINTEGRATIONS-template.md`** - Dedicated integrations document\n\n### Scripts\n\nUtilities in `scripts\u002F`:\n- **`scripts\u002Ffind-integration-points.py`** - Automated integration discovery\n- **`scripts\u002Fanalyze-repo-structure.py`** - Repository structure analysis\n\n## Quality Checklist\n\nBefore finalizing documentation, verify:\n\n- [ ] All cross-repository dependencies are documented\n- [ ] Integration points are explicitly named and described\n- [ ] Quick start instructions actually work\n- [ ] Code examples are from the actual codebase\n- [ ] Links to other repos are included where applicable\n- [ ] External service dependencies are listed\n- [ ] Setup instructions include dependencies on other repos\n- [ ] Document is readable without access to other repositories\n",{"name":5,"version":56,"description":7},"1.0.0","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs",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":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill repo-docs",{"tool":72,"command":73},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill repo-docs",{"tool":75,"command":76},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill repo-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002FSKILL.md",true,[80,86,90,94,98,102,106,110,116,120],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"examples\u002FAPI-template.md","REFERENCE","参考文档",1398,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Fexamples\u002FAPI-template.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"examples\u002FARCHITECTURE-template.md",1606,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Fexamples\u002FARCHITECTURE-template.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"examples\u002FCONTRIBUTING-template.md",1651,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Fexamples\u002FCONTRIBUTING-template.md",{"path":95,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":96,"sourceHtmlUrl":97},"examples\u002FINTEGRATIONS-template.md",2936,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Fexamples\u002FINTEGRATIONS-template.md",{"path":99,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":100,"sourceHtmlUrl":101},"examples\u002FREADME-template.md",1208,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Fexamples\u002FREADME-template.md",{"path":103,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fintegration-patterns.md",5049,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Freferences\u002Fintegration-patterns.md",{"path":107,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Ftech-detection.md",5604,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Freferences\u002Ftech-detection.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fanalyze-repo-structure.py","SCRIPT","脚本",8801,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Fscripts\u002Fanalyze-repo-structure.py",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Ffind-integration-points.py",8280,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Fscripts\u002Ffind-integration-points.py",{"path":121,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":122,"sourceHtmlUrl":123},"skill-report.json",10714,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fastrabit-cpt\u002Frepo-docs\u002Fskill-report.json",[125,135,145,154,160,167],{"skillNo":126,"name":127,"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":128,"categories":129,"keywords":131,"publishedAt":51},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[130],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[132,133,134],"model","model hierarchy","model hierarchy skill",{"skillNo":136,"name":137,"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":138,"categories":139,"keywords":141,"publishedAt":51},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[140],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[142,143,144],"MCP","zoom","zoom mcp",{"skillNo":146,"name":147,"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":148,"categories":149,"keywords":150,"publishedAt":51},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[151,152,153,143],"sdk","zoom apps sdk","apps",{"skillNo":155,"name":156,"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":157,"categories":158,"keywords":159,"publishedAt":51},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[156],{"skillNo":161,"name":162,"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":163,"categories":164,"keywords":166,"publishedAt":51},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[165],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[162],{"skillNo":168,"name":169,"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":170,"categories":171,"keywords":172,"publishedAt":51},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[169]]