[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ESZ83GMWQTTGDGP13NDWFV":3,"skill-same:01M6ESZ83GMWQTTGDGP13NDWFV":78},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6ESZ83GMWQTTGDGP13NDWFV","codebase-analysis",null,"Techniques for analyzing existing codebases to reverse-engineer requirements and understand business logic. Use when conducting brownfield analysis or understanding existing system capabilities.","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\u002Fdoubleslashse\u002Fcodebase-analysis\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"analysis","codebase analysis","capabilities","analyzing","system","grep","read","business","use","engineer","lsp","brownfield","requirements","logic","understand","2026-11-10 10:12:30",false,"---\nname: codebase-analysis\ndescription: Techniques for analyzing existing codebases to reverse-engineer requirements and understand business logic. Use when conducting brownfield analysis or understanding existing system capabilities.\nallowed-tools: Read, Grep, Glob, LSP\n---\n\n# Codebase Analysis Skill\n\n## Overview\n\nThis skill provides techniques for extracting business requirements, domain knowledge, and technical specifications from existing codebases.\n\n## Analysis Objectives\n\nWhen analyzing a codebase, seek to understand:\n1. **Domain Model**: Core entities and their relationships\n2. **Business Rules**: Validation, calculations, workflows\n3. **Integrations**: External systems and data flows\n4. **User Capabilities**: What users can do in the system\n5. **Technical Constraints**: Architecture patterns and limitations\n\n## Analysis Process\n\n### Phase 1: Structure Discovery\n1. Map project structure and organization\n2. Identify main components and layers\n3. Locate configuration and entry points\n4. Understand build and deployment setup\n\n### Phase 2: Domain Model Extraction\n1. Find entity\u002Fmodel definitions\n2. Map relationships between entities\n3. Identify domain vocabulary (ubiquitous language)\n4. Document data types and constraints\n\n### Phase 3: Business Logic Identification\n1. Locate service\u002Fbusiness logic layers\n2. Extract validation rules\n3. Document calculations and formulas\n4. Map state machines and workflows\n\n### Phase 4: Integration Mapping\n1. Find API endpoints and contracts\n2. Identify external service calls\n3. Map data flows in\u002Fout of system\n4. Document authentication patterns\n\n### Phase 5: Capability Documentation\n1. List user-facing features\n2. Map permissions and access control\n3. Document user workflows\n4. Identify edge cases and error handling\n\n## Code Pattern Recognition\n\n### Entity\u002FModel Identification\n\nLook for these patterns:\n```\n\u002F\u002F C# Entity\npublic class Order { ... }\n\n\u002F\u002F Java Entity\n@Entity\npublic class Order { ... }\n\n\u002F\u002F TypeScript Interface\ninterface Order { ... }\n\n\u002F\u002F Database Schema\nCREATE TABLE orders ( ... )\n```\n\n### Business Rule Indicators\n\nWatch for these keywords and patterns:\n- Validation: `Validate`, `Check`, `Ensure`, `Must`, `Should`\n- Calculations: `Calculate`, `Compute`, `Total`, `Sum`\n- Conditions: `If`, `When`, `Unless`, `Only`\n- Constraints: `Max`, `Min`, `Required`, `Limit`\n\n### Service Layer Patterns\n\nIdentify business logic in:\n```\n\u002F\u002F Service classes\npublic class OrderService { ... }\n\n\u002F\u002F Use cases \u002F Application services\npublic class CreateOrderUseCase { ... }\n\n\u002F\u002F Command\u002FQuery handlers\npublic class CreateOrderHandler { ... }\n```\n\n### API Endpoint Patterns\n\nLook for:\n```\n\u002F\u002F REST Controllers\n[Route(\"api\u002Forders\")]\n[HttpPost]\npublic async Task\u003COrder> Create(...)\n\n\u002F\u002F Express routes\napp.post('\u002Fapi\u002Forders', ...)\n\n\u002F\u002F GraphQL resolvers\nMutation: { createOrder: ... }\n```\n\n## Analysis Heuristics\n\n### Finding Domain Models\n1. Search for `class`, `interface`, `type` definitions\n2. Look in folders named: `Models`, `Entities`, `Domain`\n3. Check database migrations and schema files\n4. Review ORM configurations\n\n### Finding Business Rules\n1. Search for validation attributes\u002Fdecorators\n2. Look for `throw` statements (business exceptions)\n3. Find conditional logic in services\n4. Check for rule engines or policy patterns\n\n### Finding Integrations\n1. Search for HTTP client usage\n2. Look for message queue producers\u002Fconsumers\n3. Find database connection configurations\n4. Check for external SDK imports\n\n### Finding User Capabilities\n1. Review API endpoints and their permissions\n2. Check UI components and forms\n3. Look at authorization\u002Frole definitions\n4. Review menu structures and navigation\n\n## Output Artifacts\n\n### Domain Model Documentation\n```markdown\n## Entity: Order\n\n### Attributes\n| Name | Type | Description | Constraints |\n|------|------|-------------|-------------|\n| id | UUID | Unique identifier | Required |\n| status | Enum | Order status | Required |\n| total | Decimal | Order total | >= 0 |\n\n### Relationships\n- Order has many OrderItems (1:N)\n- Order belongs to Customer (N:1)\n\n### Business Rules\n- Order total must equal sum of item totals\n- Status can only transition: Draft -> Submitted -> Approved -> Completed\n```\n\n### Business Rule Documentation\n```markdown\n## Rule: Order Validation\n\n### Description\nOrders must meet these criteria before submission\n\n### Conditions\n1. Order must have at least one item\n2. All items must have valid product references\n3. Customer must have valid payment method\n4. Total must be greater than $0\n\n### Implementation\n- File: src\u002FServices\u002FOrderService.cs\n- Method: ValidateForSubmission()\n- Line: 145-180\n```\n\n### Integration Documentation\n```markdown\n## Integration: Payment Gateway\n\n### Type\nREST API (Synchronous)\n\n### Endpoint\nPOST https:\u002F\u002Fapi.payments.com\u002Fv1\u002Fcharges\n\n### Data Flow\n- Input: Order total, Customer payment token\n- Output: Transaction ID, Status\n\n### Error Handling\n- Timeout: Retry 3 times with exponential backoff\n- Failure: Mark order as payment pending, notify support\n\n### Implementation\n- File: src\u002FIntegrations\u002FPaymentGateway.cs\n```\n\n## Code Search Patterns\n\n### Finding Entities (by language)\n```bash\n# C# \u002F .NET\ngrep -r \"public class.*Entity\" --include=\"*.cs\"\ngrep -r \"\\[Table\\(\" --include=\"*.cs\"\n\n# Java\ngrep -r \"@Entity\" --include=\"*.java\"\n\n# TypeScript\ngrep -r \"interface.*{\" --include=\"*.ts\"\n```\n\n### Finding Validation Rules\n```bash\n# C# Attributes\ngrep -r \"\\[Required\\]|\\[Range\\]|\\[StringLength\\]\" --include=\"*.cs\"\n\n# Java Annotations\ngrep -r \"@NotNull|@Size|@Valid\" --include=\"*.java\"\n\n# Custom validation\ngrep -r \"Validate|throw.*Exception\" --include=\"*.cs\"\n```\n\n### Finding API Endpoints\n```bash\n# .NET Controllers\ngrep -r \"\\[Http.*\\]|\\[Route\\(\" --include=\"*.cs\"\n\n# Express.js\ngrep -r \"app\\.(get|post|put|delete)\\(\" --include=\"*.js\"\n```\n\n## Reverse Engineering Tips\n\n### Start With Entry Points\n1. Find main() or startup configuration\n2. Follow dependency injection setup\n3. Trace from API controllers to services to data\n\n### Follow the Data\n1. Start with database schema or entities\n2. Trace how data flows through system\n3. Map CRUD operations for each entity\n\n### Look for Tests\n1. Unit tests reveal expected behavior\n2. Integration tests show workflows\n3. Test data shows valid\u002Finvalid scenarios\n\n### Check Documentation\n1. Look for README files\n2. Check API documentation (Swagger\u002FOpenAPI)\n3. Review code comments and XML docs\n\n## Questions to Answer\n\nAfter analysis, you should be able to answer:\n\n1. **What entities exist and how do they relate?**\n2. **What can users do in this system?**\n3. **What business rules govern behavior?**\n4. **What external systems does this integrate with?**\n5. **What are the key workflows?**\n6. **What constraints exist (technical and business)?**\n7. **What data does the system manage?**\n8. **Who has access to what?**\n\nSee [patterns.md](patterns.md) for common architectural patterns to identify.\n","# Codebase Analysis Skill\n\n## Overview\n\nThis skill provides techniques for extracting business requirements, domain knowledge, and technical specifications from existing codebases.\n\n## Analysis Objectives\n\nWhen analyzing a codebase, seek to understand:\n1. **Domain Model**: Core entities and their relationships\n2. **Business Rules**: Validation, calculations, workflows\n3. **Integrations**: External systems and data flows\n4. **User Capabilities**: What users can do in the system\n5. **Technical Constraints**: Architecture patterns and limitations\n\n## Analysis Process\n\n### Phase 1: Structure Discovery\n1. Map project structure and organization\n2. Identify main components and layers\n3. Locate configuration and entry points\n4. Understand build and deployment setup\n\n### Phase 2: Domain Model Extraction\n1. Find entity\u002Fmodel definitions\n2. Map relationships between entities\n3. Identify domain vocabulary (ubiquitous language)\n4. Document data types and constraints\n\n### Phase 3: Business Logic Identification\n1. Locate service\u002Fbusiness logic layers\n2. Extract validation rules\n3. Document calculations and formulas\n4. Map state machines and workflows\n\n### Phase 4: Integration Mapping\n1. Find API endpoints and contracts\n2. Identify external service calls\n3. Map data flows in\u002Fout of system\n4. Document authentication patterns\n\n### Phase 5: Capability Documentation\n1. List user-facing features\n2. Map permissions and access control\n3. Document user workflows\n4. Identify edge cases and error handling\n\n## Code Pattern Recognition\n\n### Entity\u002FModel Identification\n\nLook for these patterns:\n```\n\u002F\u002F C# Entity\npublic class Order { ... }\n\n\u002F\u002F Java Entity\n@Entity\npublic class Order { ... }\n\n\u002F\u002F TypeScript Interface\ninterface Order { ... }\n\n\u002F\u002F Database Schema\nCREATE TABLE orders ( ... )\n```\n\n### Business Rule Indicators\n\nWatch for these keywords and patterns:\n- Validation: `Validate`, `Check`, `Ensure`, `Must`, `Should`\n- Calculations: `Calculate`, `Compute`, `Total`, `Sum`\n- Conditions: `If`, `When`, `Unless`, `Only`\n- Constraints: `Max`, `Min`, `Required`, `Limit`\n\n### Service Layer Patterns\n\nIdentify business logic in:\n```\n\u002F\u002F Service classes\npublic class OrderService { ... }\n\n\u002F\u002F Use cases \u002F Application services\npublic class CreateOrderUseCase { ... }\n\n\u002F\u002F Command\u002FQuery handlers\npublic class CreateOrderHandler { ... }\n```\n\n### API Endpoint Patterns\n\nLook for:\n```\n\u002F\u002F REST Controllers\n[Route(\"api\u002Forders\")]\n[HttpPost]\npublic async Task\u003COrder> Create(...)\n\n\u002F\u002F Express routes\napp.post('\u002Fapi\u002Forders', ...)\n\n\u002F\u002F GraphQL resolvers\nMutation: { createOrder: ... }\n```\n\n## Analysis Heuristics\n\n### Finding Domain Models\n1. Search for `class`, `interface`, `type` definitions\n2. Look in folders named: `Models`, `Entities`, `Domain`\n3. Check database migrations and schema files\n4. Review ORM configurations\n\n### Finding Business Rules\n1. Search for validation attributes\u002Fdecorators\n2. Look for `throw` statements (business exceptions)\n3. Find conditional logic in services\n4. Check for rule engines or policy patterns\n\n### Finding Integrations\n1. Search for HTTP client usage\n2. Look for message queue producers\u002Fconsumers\n3. Find database connection configurations\n4. Check for external SDK imports\n\n### Finding User Capabilities\n1. Review API endpoints and their permissions\n2. Check UI components and forms\n3. Look at authorization\u002Frole definitions\n4. Review menu structures and navigation\n\n## Output Artifacts\n\n### Domain Model Documentation\n```markdown\n## Entity: Order\n\n### Attributes\n| Name | Type | Description | Constraints |\n|------|------|-------------|-------------|\n| id | UUID | Unique identifier | Required |\n| status | Enum | Order status | Required |\n| total | Decimal | Order total | >= 0 |\n\n### Relationships\n- Order has many OrderItems (1:N)\n- Order belongs to Customer (N:1)\n\n### Business Rules\n- Order total must equal sum of item totals\n- Status can only transition: Draft -> Submitted -> Approved -> Completed\n```\n\n### Business Rule Documentation\n```markdown\n## Rule: Order Validation\n\n### Description\nOrders must meet these criteria before submission\n\n### Conditions\n1. Order must have at least one item\n2. All items must have valid product references\n3. Customer must have valid payment method\n4. Total must be greater than $0\n\n### Implementation\n- File: src\u002FServices\u002FOrderService.cs\n- Method: ValidateForSubmission()\n- Line: 145-180\n```\n\n### Integration Documentation\n```markdown\n## Integration: Payment Gateway\n\n### Type\nREST API (Synchronous)\n\n### Endpoint\nPOST https:\u002F\u002Fapi.payments.com\u002Fv1\u002Fcharges\n\n### Data Flow\n- Input: Order total, Customer payment token\n- Output: Transaction ID, Status\n\n### Error Handling\n- Timeout: Retry 3 times with exponential backoff\n- Failure: Mark order as payment pending, notify support\n\n### Implementation\n- File: src\u002FIntegrations\u002FPaymentGateway.cs\n```\n\n## Code Search Patterns\n\n### Finding Entities (by language)\n```bash\n# C# \u002F .NET\ngrep -r \"public class.*Entity\" --include=\"*.cs\"\ngrep -r \"\\[Table\\(\" --include=\"*.cs\"\n\n# Java\ngrep -r \"@Entity\" --include=\"*.java\"\n\n# TypeScript\ngrep -r \"interface.*{\" --include=\"*.ts\"\n```\n\n### Finding Validation Rules\n```bash\n# C# Attributes\ngrep -r \"\\[Required\\]|\\[Range\\]|\\[StringLength\\]\" --include=\"*.cs\"\n\n# Java Annotations\ngrep -r \"@NotNull|@Size|@Valid\" --include=\"*.java\"\n\n# Custom validation\ngrep -r \"Validate|throw.*Exception\" --include=\"*.cs\"\n```\n\n### Finding API Endpoints\n```bash\n# .NET Controllers\ngrep -r \"\\[Http.*\\]|\\[Route\\(\" --include=\"*.cs\"\n\n# Express.js\ngrep -r \"app\\.(get|post|put|delete)\\(\" --include=\"*.js\"\n```\n\n## Reverse Engineering Tips\n\n### Start With Entry Points\n1. Find main() or startup configuration\n2. Follow dependency injection setup\n3. Trace from API controllers to services to data\n\n### Follow the Data\n1. Start with database schema or entities\n2. Trace how data flows through system\n3. Map CRUD operations for each entity\n\n### Look for Tests\n1. Unit tests reveal expected behavior\n2. Integration tests show workflows\n3. Test data shows valid\u002Finvalid scenarios\n\n### Check Documentation\n1. Look for README files\n2. Check API documentation (Swagger\u002FOpenAPI)\n3. Review code comments and XML docs\n\n## Questions to Answer\n\nAfter analysis, you should be able to answer:\n\n1. **What entities exist and how do they relate?**\n2. **What can users do in this system?**\n3. **What business rules govern behavior?**\n4. **What external systems does this integrate with?**\n5. **What are the key workflows?**\n6. **What constraints exist (technical and business)?**\n7. **What data does the system manage?**\n8. **Who has access to what?**\n\nSee [patterns.md](patterns.md) for common architectural patterns to identify.\n",{"name":5,"description":7,"allowed-tools":44},"Read, Grep, Glob, LSP","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fdoubleslashse\u002Fcodebase-analysis",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill codebase-analysis",{"tool":60,"command":61},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill codebase-analysis",{"tool":63,"command":64},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill codebase-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fdoubleslashse\u002Fcodebase-analysis\u002FSKILL.md",true,[68,74],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"patterns.md","REFERENCE","参考文档",8368,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fdoubleslashse\u002Fcodebase-analysis\u002Fpatterns.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"skill-report.json",10148,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fdoubleslashse\u002Fcodebase-analysis\u002Fskill-report.json",[79,93,103,112,118,125],{"skillNo":80,"name":81,"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":82,"categories":83,"keywords":89,"publishedAt":39},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[90,91,92],"model","model hierarchy","model hierarchy skill",{"skillNo":94,"name":95,"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":96,"categories":97,"keywords":99,"publishedAt":39},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[98],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},[100,101,102],"MCP","zoom","zoom mcp",{"skillNo":104,"name":105,"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":106,"categories":107,"keywords":108,"publishedAt":39},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[109,110,111,101],"sdk","zoom apps sdk","apps",{"skillNo":113,"name":114,"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":115,"categories":116,"keywords":117,"publishedAt":39},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[114],{"skillNo":119,"name":120,"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":121,"categories":122,"keywords":124,"publishedAt":39},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[123],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},[120],{"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":130,"publishedAt":39},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[127]]