[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71PQR8F76DY229WEX3XV2WG":3,"skill-same:01M71PQR8F76DY229WEX3XV2WG":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M71PQR8F76DY229WEX3XV2WG","azure-resource-visualizer",null,"Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. Use this skill when the user asks for a diagram of their Azure resources or help in understanding how the resources relate to each other.","Thamielis\u002F.agents","Thamielis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F52717133?v=4","01M71NG040Z4RAKTDW6JVQTZA0","01M71NG04N9WFE1H3RH0BF6VDY",0,"MIT","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"azure","azure resource visualizer","user","groups","relationships","microsoft","help","azure resources","use","architecture diagrams","for","how","mermaid","generate","diagram","analyze","architecture","when","resources","diagrams","2026-11-10 13:02:02",false,"---\nname: azure-resource-visualizer\ndescription: Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. Use this skill when the user asks for a diagram of their Azure resources or help in understanding how the resources relate to each other.\nlicense: Complete terms in LICENSE.txt\nmetadata:\n  author: Tom Meschter (tom.meschter@microsoft.com)\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\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\n**Diagram Structure Guidelines:**\n\n```mermaid\ngraph TB\n    %% Use subgraphs to group related resources\n    subgraph \"Resource Group: [name]\"\n        subgraph \"Network Layer\"\n            VNET[Virtual Network\u003Cbr\u002F>10.0.0.0\u002F16]\n            SUBNET1[Subnet: web\u003Cbr\u002F>10.0.1.0\u002F24]\n            SUBNET2[Subnet: data\u003Cbr\u002F>10.0.2.0\u002F24]\n            NSG[Network Security Group]\n        end\n        \n        subgraph \"Compute Layer\"\n            APP[App Service\u003Cbr\u002F>Plan: P1v2]\n            FUNC[Function App\u003Cbr\u002F>Runtime: .NET 8]\n        end\n        \n        subgraph \"Data Layer\"\n            SQL[Azure SQL Database\u003Cbr\u002F>DTU: S1]\n            STORAGE[Storage Account\u003Cbr\u002F>Type: Standard LRS]\n        end\n        \n        subgraph \"Security & Identity\"\n            KV[Key Vault]\n            MI[Managed Identity]\n        end\n    end\n    \n    %% Define relationships with descriptive labels\n    APP -->|\"HTTPS requests\"| FUNC\n    FUNC -->|\"SQL connection\"| SQL\n    FUNC -->|\"Blob\u002FQueue access\"| STORAGE\n    APP -->|\"Uses identity\"| MI\n    MI -->|\"Access secrets\"| KV\n    VNET --> SUBNET1\n    VNET --> SUBNET2\n    SUBNET1 --> APP\n    SUBNET2 --> SQL\n    NSG -->|\"Rules applied to\"| SUBNET1\n```\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## Example Interaction\n\n**User**: \"Analyze my production resource group\"\n\n**Agent**:\n1. Lists all resource groups in subscription\n2. Asks user to select: \"Which resource group? 1) rg-prod-app, 2) rg-dev-app, 3) rg-shared\"\n3. User selects: \"1\"\n4. Queries all resources in rg-prod-app\n5. Analyzes: App Service, Function App, SQL Database, Storage Account, Key Vault, VNet, NSG\n6. Identifies relationships: App → Function, Function → SQL, Function → Storage, All → Key Vault\n7. Creates detailed Mermaid diagram with subgraphs\n8. Generates `rg-prod-app-architecture.md` with complete documentation\n9. Displays: \"Created architecture diagram in rg-prod-app-architecture.md. Found 7 resources with 8 key relationships.\"\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\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\n**Diagram Structure Guidelines:**\n\n```mermaid\ngraph TB\n    %% Use subgraphs to group related resources\n    subgraph \"Resource Group: [name]\"\n        subgraph \"Network Layer\"\n            VNET[Virtual Network\u003Cbr\u002F>10.0.0.0\u002F16]\n            SUBNET1[Subnet: web\u003Cbr\u002F>10.0.1.0\u002F24]\n            SUBNET2[Subnet: data\u003Cbr\u002F>10.0.2.0\u002F24]\n            NSG[Network Security Group]\n        end\n        \n        subgraph \"Compute Layer\"\n            APP[App Service\u003Cbr\u002F>Plan: P1v2]\n            FUNC[Function App\u003Cbr\u002F>Runtime: .NET 8]\n        end\n        \n        subgraph \"Data Layer\"\n            SQL[Azure SQL Database\u003Cbr\u002F>DTU: S1]\n            STORAGE[Storage Account\u003Cbr\u002F>Type: Standard LRS]\n        end\n        \n        subgraph \"Security & Identity\"\n            KV[Key Vault]\n            MI[Managed Identity]\n        end\n    end\n    \n    %% Define relationships with descriptive labels\n    APP -->|\"HTTPS requests\"| FUNC\n    FUNC -->|\"SQL connection\"| SQL\n    FUNC -->|\"Blob\u002FQueue access\"| STORAGE\n    APP -->|\"Uses identity\"| MI\n    MI -->|\"Access secrets\"| KV\n    VNET --> SUBNET1\n    VNET --> SUBNET2\n    SUBNET1 --> APP\n    SUBNET2 --> SQL\n    NSG -->|\"Rules applied to\"| SUBNET1\n```\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## Example Interaction\n\n**User**: \"Analyze my production resource group\"\n\n**Agent**:\n1. Lists all resource groups in subscription\n2. Asks user to select: \"Which resource group? 1) rg-prod-app, 2) rg-dev-app, 3) rg-shared\"\n3. User selects: \"1\"\n4. Queries all resources in rg-prod-app\n5. Analyzes: App Service, Function App, SQL Database, Storage Account, Key Vault, VNet, NSG\n6. Identifies relationships: App → Function, Function → SQL, Function → Storage, All → Key Vault\n7. Creates detailed Mermaid diagram with subgraphs\n8. Generates `rg-prod-app-architecture.md` with complete documentation\n9. Displays: \"Created architecture diagram in rg-prod-app-architecture.md. Found 7 resources with 8 key relationships.\"\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,"license":44,"metadata":45,"description":7},"Complete terms in LICENSE.txt",{"author":46},"Tom Meschter (tom.meschter@microsoft.com)","main","dd673a28ba66191245f0e384c525b1dcff1c427a","skills\u002Fazure-resource-visualizer","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents","https:\u002F\u002Fgithub.com\u002FThamielis","2026-06-08 04:03:12",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Thamielis\u002F.agents --skill azure-resource-visualizer",{"tool":59,"command":60},"bunx","bunx skills add Thamielis\u002F.agents --skill azure-resource-visualizer",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Thamielis\u002F.agents --skill azure-resource-visualizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Ftemplate-architecture.md","ASSET","资产文件",970,"https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fazure-resource-visualizer\u002Fassets\u002Ftemplate-architecture.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1078,[79,112,137,166,197,222],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":95,"publishedAt":39},"01M71QFD7835D0JG8MS43NRRVE","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[87,92],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000009","前端开发",[96,97,98,99,100,101,102,103,104,105,29,106,107,108,109,110,111],"webapp","testing","webapp testing","local","frontend","debugging","logs","browser","ui","screenshots","applications","toolkit","with","playwright","web","behavior",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":39},"01M71QF1RVYQPZ2HPHXYWBC27K","web-artifacts-builder","Suite of tools for creating elaborate, multi-component Codex.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[119],{"categoryNo":93,"categoryName":94,"taxonomyType":90,"taxonomyTypeDesc":91},[121,122,123,110,124,125,126,29,127,128,100,129,27,130,131,132,133,134,135,136],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","components","react","multi","state","routing","state management",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":149,"publishedAt":39},"01M71QEMXGG7MTTMSRVE3YFCXC","visual-explainer","Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-explainer\u002FSKILL.md",[143,144],{"categoryNo":93,"categoryName":94,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[150,151,152,153,154,155,156,35,157,32,158,159,160,161,162,29,163,164,165,27],"visual","visual explainer","explainer","project","files","image","you","plan","present","concepts","table","as","view","ascii table","ascii","surf",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":178,"publishedAt":39},"01M71QDJVMVM82514TRK7VHXC5","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[172,175],{"categoryNo":173,"categoryName":174,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":176,"categoryName":177,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",[179,180,181,182,183,184,185,186,187,188,154,189,190,191,36,192,193,194,195,196],"Media","processing","transloadit media processing","media processing","transloadit","images","Video","ocr","Audio","pipeline","MCP","free","documents","mcp server","thumbnails","server","mcp-server","cli",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":201,"sourceHtmlUrl":202,"categories":203,"keywords":207,"publishedAt":39},"01M71QDEJ4M9TP6VZRNK3J9NKX","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[204],{"categoryNo":205,"categoryName":206,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000015","视觉设计",[208,209,210,211,212,29,213,214,215,216,156,123,217,107,218,219,108,220,32,221],"theme","theme factory","factory","SET","slides","landing","pages","new","themes","apply","can","fonts","artifact","fly",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":231,"publishedAt":39},"01M71QD9QXM9M9RWQX40E981D4","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FThamielis\u002F.agents\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[228],{"categoryNo":229,"categoryName":230,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000011","运维与部署",[211,232,233,234,235,236,237,37,238,29,239,240,241,242,19,243,244,245,27,246],"diff","terraform azurerm set diff analyzer","analyzer","terraform","gateway","firewall","attributes","provider","resource changes","balancer","front","diffs","load balancer","only","load"]