[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EWPJ06VG7PYA5K0Z2X6NPE":3,"skill-same:01M6EWPJ06VG7PYA5K0Z2X6NPE":92},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6EWPJ06VG7PYA5K0Z2X6NPE","azure-resource-visualizer",null,"Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. USE FOR: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure DO NOT USE FOR: creating\u002Fmodifying resources (use azure-deploy), security scanning (use azure-security), performance troubleshooting (use azure-diagnostics), code generation (use relevant service skill)","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fmicrosoft\u002Fazure-resource-visualizer\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,42,43],"azure resource visualizer","azure","code","relevant","resources","map","show","diagrams","scanning","analyze","Code Generation","topology","performance","visualization","generate","create","architecture diagram","mermaid","diagram","architecture","2026-11-10 10:12:30",false,"---\nname: azure-resource-visualizer\ndescription: >-\n  Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources.\n  USE FOR: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure\n  DO NOT USE FOR: creating\u002Fmodifying resources (use azure-deploy), security scanning (use azure-security), performance troubleshooting (use azure-diagnostics), code generation (use relevant service skill)\n---\n\n# Azure Resource Visualizer - Architecture Diagram Generator\n\nA user may ask for help understanding how individual resources fit together, or to create a diagram showing their relationships. Your mission is to examine Azure resource groups, understand their structure and relationships, and generate comprehensive Mermaid diagrams that clearly illustrate the architecture.\n\n## Core Responsibilities\n\n1. **Resource Group Discovery**: List available resource groups when not specified\n2. **Deep Resource Analysis**: Examine all resources, their configurations, and interdependencies\n3. **Relationship Mapping**: Identify and document all connections between resources\n4. **Diagram Generation**: Create detailed, accurate Mermaid diagrams\n5. **Documentation Creation**: Produce clear markdown files with embedded diagrams\n\n## Workflow Process\n\n### Step 1: Resource Group Selection\n\nIf the user hasn't specified a resource group:\n\n1. Use your tools to query available resource groups. If you do not have a tool for this, use `az`.\n2. Present a numbered list of resource groups with their locations\n3. Ask the user to select one by number or name\n4. Wait for user response before proceeding\n\nIf a resource group is specified, validate it exists and proceed.\n\n### Step 2: Resource Discovery & Analysis\n\nFor bulk resource discovery across subscriptions, use Azure Resource Graph queries. See [Azure Resource Graph Queries](references\u002Fazure-resource-graph.md) for cross-subscription inventory and relationship discovery patterns.\n\nOnce you have the resource group:\n\n1. **Query all resources** in the resource group using Azure MCP tools or `az`.\n2. **Analyze each resource** type and capture:\n   - Resource name and type\n   - SKU\u002Ftier information\n   - Location\u002Fregion\n   - Key configuration properties\n   - Network settings (VNets, subnets, private endpoints)\n   - Identity and access (Managed Identity, RBAC)\n   - Dependencies and connections\n\n3. **Map relationships** by identifying:\n   - **Network connections**: VNet peering, subnet assignments, NSG rules, private endpoints\n   - **Data flow**: Apps → Databases, Functions → Storage, API Management → Backends\n   - **Identity**: Managed identities connecting to resources\n   - **Configuration**: App Settings pointing to Key Vaults, connection strings\n   - **Dependencies**: Parent-child relationships, required resources\n\n### Step 3: Diagram Construction\n\nCreate a **detailed Mermaid diagram** using the `graph TB` (top-to-bottom) or `graph LR` (left-to-right) format.\n\nSee [example-diagram.md](.\u002Fassets\u002Fexample-diagram.md) for a complete sample architecture diagram.\n\n**Key Diagram Requirements:**\n\n- **Group by layer or purpose**: Network, Compute, Data, Security, Monitoring\n- **Include details**: SKUs, tiers, important settings in node labels (use `\u003Cbr\u002F>` for line breaks)\n- **Label all connections**: Describe what flows between resources (data, identity, network)\n- **Use meaningful node IDs**: Abbreviations that make sense (APP, FUNC, SQL, KV)\n- **Visual hierarchy**: Subgraphs for logical grouping\n- **Connection types**:\n  - `-->` for data flow or dependencies\n  - `-.->` for optional\u002Fconditional connections\n  - `==>` for critical\u002Fprimary paths\n\n**Resource Type Examples:**\n- App Service: Include plan tier (B1, S1, P1v2)\n- Functions: Include runtime (.NET, Python, Node)\n- Databases: Include tier (Basic, Standard, Premium)\n- Storage: Include redundancy (LRS, GRS, ZRS)\n- VNets: Include address space\n- Subnets: Include address range\n\n### Step 4: File Creation\n\nUse [template-architecture.md](.\u002Fassets\u002Ftemplate-architecture.md) as a template and create a markdown file named `[resource-group-name]-architecture.md` with:\n\n1. **Header**: Resource group name, subscription, region\n2. **Summary**: Brief overview of the architecture (2-3 paragraphs)\n3. **Resource Inventory**: Table listing all resources with types and key properties\n4. **Architecture Diagram**: The complete Mermaid diagram\n5. **Relationship Details**: Explanation of key connections and data flows\n6. **Notes**: Any important observations, potential issues, or recommendations\n\n## Operating Guidelines\n\n### Quality Standards\n\n- **Accuracy**: Verify all resource details before including in diagram\n- **Completeness**: Don't omit resources; include everything in the resource group\n- **Clarity**: Use clear, descriptive labels and logical grouping\n- **Detail Level**: Include configuration details that matter for architecture understanding\n- **Relationships**: Show ALL significant connections, not just obvious ones\n\n### Tool Usage Patterns\n\n1. **Azure MCP Search**: \n   - Use `intent=\"list resource groups\"` to discover resource groups\n   - Use `intent=\"list resources in group\"` with group name to get all resources\n   - Use `intent=\"get resource details\"` for individual resource analysis\n   - Use `command` parameter when you need specific Azure operations\n\n2. **File Creation**:\n   - Always create in workspace root or a `docs\u002F` folder if it exists\n   - Use clear, descriptive filenames: `[rg-name]-architecture.md`\n   - Ensure Mermaid syntax is valid (test syntax mentally before output)\n\n3. **Terminal (when needed)**:\n   - Use Azure CLI for complex queries not available via MCP\n   - Example: `az resource list --resource-group \u003Cname> --output json`\n   - Example: `az network vnet show --resource-group \u003Cname> --name \u003Cvnet-name>`\n\n### Constraints & Boundaries\n\n**Always Do:**\n- ✅ List resource groups if not specified\n- ✅ Wait for user selection before proceeding\n- ✅ Analyze ALL resources in the group\n- ✅ Create detailed, accurate diagrams\n- ✅ Include configuration details in node labels\n- ✅ Group resources logically with subgraphs\n- ✅ Label all connections descriptively\n- ✅ Create a complete markdown file with diagram\n\n**Never Do:**\n- ❌ Skip resources because they seem unimportant\n- ❌ Make assumptions about resource relationships without verification\n- ❌ Create incomplete or placeholder diagrams\n- ❌ Omit configuration details that affect architecture\n- ❌ Proceed without confirming resource group selection\n- ❌ Generate invalid Mermaid syntax\n- ❌ Modify or delete Azure resources (read-only analysis)\n\n### Edge Cases & Error Handling\n\n- **No resources found**: Inform user and verify resource group name\n- **Permission issues**: Explain what's missing and suggest checking RBAC\n- **Complex architectures (50+ resources)**: Consider creating multiple diagrams by layer\n- **Cross-resource-group dependencies**: Note external dependencies in diagram notes\n- **Resources without clear relationships**: Group in \"Other Resources\" section\n\n## Output Format Specifications\n\n### Mermaid Diagram Syntax\n- Use `graph TB` (top-to-bottom) for vertical layouts\n- Use `graph LR` (left-to-right) for horizontal layouts (better for wide architectures)\n- Subgraph syntax: `subgraph \"Descriptive Name\"`\n- Node syntax: `ID[\"Display Name\u003Cbr\u002F>Details\"]`\n- Connection syntax: `SOURCE -->|\"Label\"| TARGET`\n\n### Markdown Structure\n- Use H1 for main title\n- Use H2 for major sections\n- Use H3 for subsections\n- Use tables for resource inventories\n- Use bullet lists for notes and recommendations\n- Use code blocks with `mermaid` language tag for diagrams\n\n## Success Criteria\n\nA successful analysis includes:\n- ✅ Valid resource group identified\n- ✅ All resources discovered and analyzed\n- ✅ All significant relationships mapped\n- ✅ Detailed Mermaid diagram with proper grouping\n- ✅ Complete markdown file created\n- ✅ Clear, actionable documentation\n- ✅ Valid Mermaid syntax that renders correctly\n- ✅ Professional, architect-level output\n\nYour goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.\n","# Azure Resource Visualizer - Architecture Diagram Generator\n\nA user may ask for help understanding how individual resources fit together, or to create a diagram showing their relationships. Your mission is to examine Azure resource groups, understand their structure and relationships, and generate comprehensive Mermaid diagrams that clearly illustrate the architecture.\n\n## Core Responsibilities\n\n1. **Resource Group Discovery**: List available resource groups when not specified\n2. **Deep Resource Analysis**: Examine all resources, their configurations, and interdependencies\n3. **Relationship Mapping**: Identify and document all connections between resources\n4. **Diagram Generation**: Create detailed, accurate Mermaid diagrams\n5. **Documentation Creation**: Produce clear markdown files with embedded diagrams\n\n## Workflow Process\n\n### Step 1: Resource Group Selection\n\nIf the user hasn't specified a resource group:\n\n1. Use your tools to query available resource groups. If you do not have a tool for this, use `az`.\n2. Present a numbered list of resource groups with their locations\n3. Ask the user to select one by number or name\n4. Wait for user response before proceeding\n\nIf a resource group is specified, validate it exists and proceed.\n\n### Step 2: Resource Discovery & Analysis\n\nFor bulk resource discovery across subscriptions, use Azure Resource Graph queries. See [Azure Resource Graph Queries](references\u002Fazure-resource-graph.md) for cross-subscription inventory and relationship discovery patterns.\n\nOnce you have the resource group:\n\n1. **Query all resources** in the resource group using Azure MCP tools or `az`.\n2. **Analyze each resource** type and capture:\n   - Resource name and type\n   - SKU\u002Ftier information\n   - Location\u002Fregion\n   - Key configuration properties\n   - Network settings (VNets, subnets, private endpoints)\n   - Identity and access (Managed Identity, RBAC)\n   - Dependencies and connections\n\n3. **Map relationships** by identifying:\n   - **Network connections**: VNet peering, subnet assignments, NSG rules, private endpoints\n   - **Data flow**: Apps → Databases, Functions → Storage, API Management → Backends\n   - **Identity**: Managed identities connecting to resources\n   - **Configuration**: App Settings pointing to Key Vaults, connection strings\n   - **Dependencies**: Parent-child relationships, required resources\n\n### Step 3: Diagram Construction\n\nCreate a **detailed Mermaid diagram** using the `graph TB` (top-to-bottom) or `graph LR` (left-to-right) format.\n\nSee [example-diagram.md](.\u002Fassets\u002Fexample-diagram.md) for a complete sample architecture diagram.\n\n**Key Diagram Requirements:**\n\n- **Group by layer or purpose**: Network, Compute, Data, Security, Monitoring\n- **Include details**: SKUs, tiers, important settings in node labels (use `\u003Cbr\u002F>` for line breaks)\n- **Label all connections**: Describe what flows between resources (data, identity, network)\n- **Use meaningful node IDs**: Abbreviations that make sense (APP, FUNC, SQL, KV)\n- **Visual hierarchy**: Subgraphs for logical grouping\n- **Connection types**:\n  - `-->` for data flow or dependencies\n  - `-.->` for optional\u002Fconditional connections\n  - `==>` for critical\u002Fprimary paths\n\n**Resource Type Examples:**\n- App Service: Include plan tier (B1, S1, P1v2)\n- Functions: Include runtime (.NET, Python, Node)\n- Databases: Include tier (Basic, Standard, Premium)\n- Storage: Include redundancy (LRS, GRS, ZRS)\n- VNets: Include address space\n- Subnets: Include address range\n\n### Step 4: File Creation\n\nUse [template-architecture.md](.\u002Fassets\u002Ftemplate-architecture.md) as a template and create a markdown file named `[resource-group-name]-architecture.md` with:\n\n1. **Header**: Resource group name, subscription, region\n2. **Summary**: Brief overview of the architecture (2-3 paragraphs)\n3. **Resource Inventory**: Table listing all resources with types and key properties\n4. **Architecture Diagram**: The complete Mermaid diagram\n5. **Relationship Details**: Explanation of key connections and data flows\n6. **Notes**: Any important observations, potential issues, or recommendations\n\n## Operating Guidelines\n\n### Quality Standards\n\n- **Accuracy**: Verify all resource details before including in diagram\n- **Completeness**: Don't omit resources; include everything in the resource group\n- **Clarity**: Use clear, descriptive labels and logical grouping\n- **Detail Level**: Include configuration details that matter for architecture understanding\n- **Relationships**: Show ALL significant connections, not just obvious ones\n\n### Tool Usage Patterns\n\n1. **Azure MCP Search**: \n   - Use `intent=\"list resource groups\"` to discover resource groups\n   - Use `intent=\"list resources in group\"` with group name to get all resources\n   - Use `intent=\"get resource details\"` for individual resource analysis\n   - Use `command` parameter when you need specific Azure operations\n\n2. **File Creation**:\n   - Always create in workspace root or a `docs\u002F` folder if it exists\n   - Use clear, descriptive filenames: `[rg-name]-architecture.md`\n   - Ensure Mermaid syntax is valid (test syntax mentally before output)\n\n3. **Terminal (when needed)**:\n   - Use Azure CLI for complex queries not available via MCP\n   - Example: `az resource list --resource-group \u003Cname> --output json`\n   - Example: `az network vnet show --resource-group \u003Cname> --name \u003Cvnet-name>`\n\n### Constraints & Boundaries\n\n**Always Do:**\n- ✅ List resource groups if not specified\n- ✅ Wait for user selection before proceeding\n- ✅ Analyze ALL resources in the group\n- ✅ Create detailed, accurate diagrams\n- ✅ Include configuration details in node labels\n- ✅ Group resources logically with subgraphs\n- ✅ Label all connections descriptively\n- ✅ Create a complete markdown file with diagram\n\n**Never Do:**\n- ❌ Skip resources because they seem unimportant\n- ❌ Make assumptions about resource relationships without verification\n- ❌ Create incomplete or placeholder diagrams\n- ❌ Omit configuration details that affect architecture\n- ❌ Proceed without confirming resource group selection\n- ❌ Generate invalid Mermaid syntax\n- ❌ Modify or delete Azure resources (read-only analysis)\n\n### Edge Cases & Error Handling\n\n- **No resources found**: Inform user and verify resource group name\n- **Permission issues**: Explain what's missing and suggest checking RBAC\n- **Complex architectures (50+ resources)**: Consider creating multiple diagrams by layer\n- **Cross-resource-group dependencies**: Note external dependencies in diagram notes\n- **Resources without clear relationships**: Group in \"Other Resources\" section\n\n## Output Format Specifications\n\n### Mermaid Diagram Syntax\n- Use `graph TB` (top-to-bottom) for vertical layouts\n- Use `graph LR` (left-to-right) for horizontal layouts (better for wide architectures)\n- Subgraph syntax: `subgraph \"Descriptive Name\"`\n- Node syntax: `ID[\"Display Name\u003Cbr\u002F>Details\"]`\n- Connection syntax: `SOURCE -->|\"Label\"| TARGET`\n\n### Markdown Structure\n- Use H1 for main title\n- Use H2 for major sections\n- Use H3 for subsections\n- Use tables for resource inventories\n- Use bullet lists for notes and recommendations\n- Use code blocks with `mermaid` language tag for diagrams\n\n## Success Criteria\n\nA successful analysis includes:\n- ✅ Valid resource group identified\n- ✅ All resources discovered and analyzed\n- ✅ All significant relationships mapped\n- ✅ Detailed Mermaid diagram with proper grouping\n- ✅ Complete markdown file created\n- ✅ Clear, actionable documentation\n- ✅ Valid Mermaid syntax that renders correctly\n- ✅ Professional, architect-level output\n\nYour goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fmicrosoft\u002Fazure-resource-visualizer",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill azure-resource-visualizer",{"tool":64,"command":65},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill azure-resource-visualizer",{"tool":67,"command":68},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill azure-resource-visualizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fmicrosoft\u002Fazure-resource-visualizer\u002FSKILL.md",true,[72,78,82,88],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Fexample-diagram.md","ASSET","资产文件",1777,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fmicrosoft\u002Fazure-resource-visualizer\u002Fassets\u002Fexample-diagram.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Ftemplate-architecture.md",970,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fmicrosoft\u002Fazure-resource-visualizer\u002Fassets\u002Ftemplate-architecture.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fazure-resource-graph.md","REFERENCE","参考文档",2477,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fmicrosoft\u002Fazure-resource-visualizer\u002Freferences\u002Fazure-resource-graph.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"skill-report.json",11792,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fmicrosoft\u002Fazure-resource-visualizer\u002Fskill-report.json",[93,103,113,122,128,135],{"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":44},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[98],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[100,101,102],"model","model hierarchy","model hierarchy skill",{"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":109,"publishedAt":44},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[108],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[110,111,112],"MCP","zoom","zoom mcp",{"skillNo":114,"name":115,"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":116,"categories":117,"keywords":118,"publishedAt":44},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[119,120,121,111],"sdk","zoom apps sdk","apps",{"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":127,"publishedAt":44},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[124],{"skillNo":129,"name":130,"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":131,"categories":132,"keywords":134,"publishedAt":44},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[130],{"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":140,"publishedAt":44},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[137]]