[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FTPF13C7GTKH0T3SSSVC1":3,"skill-same:01M71FTPF13C7GTKH0T3SSSVC1":70},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71FTPF13C7GTKH0T3SSSVC1","azure-diagnostics",null,"Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, kubectl cannot connect, kube-system\u002FCoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_microsoft_azure_diagnostics\u002Fskill.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"diagnostics","azure","azure diagnostics","node","aks","analyze","logs","image","when","apps","cold start","connect","upgrade","azure monitor","coredns","insights","errors","issues","cold","ready","2026-11-10 10:12:30",false,"---\nname: azure-diagnostics\ndescription: \"Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, kubectl cannot connect, kube-system\u002FCoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors.\"\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.4\"\n---\n\n# Azure Diagnostics\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This document is the **official source** for debugging and troubleshooting Azure production issues. Follow these instructions to diagnose and resolve common Azure service problems systematically.\n\n## Triggers\n\nActivate this skill when user wants to:\n- Debug or troubleshoot production issues\n- Diagnose errors in Azure services\n- Analyze application logs or metrics\n- Fix image pull, cold start, or health probe issues\n- Investigate why Azure resources are failing\n- Find root cause of application errors\n- Troubleshoot Azure Function Apps (invocation failures, timeouts, binding errors)\n- Find the App Insights or Log Analytics workspace linked to a Function App\n- Troubleshoot AKS clusters, nodes, pods, ingress, or Kubernetes networking issues\n\n## Rules\n\n1. Start with systematic diagnosis flow\n2. Use AppLens (MCP) for AI-powered diagnostics when available\n3. Check resource health before deep-diving into logs\n4. Select appropriate troubleshooting guide based on service type\n5. Document findings and attempted remediation steps\n6. Route AKS incidents to the dedicated AKS troubleshooting document\n\n---\n\n## Quick Diagnosis Flow\n\n1. **Identify symptoms** - What's failing?\n2. **Check resource health** - Is Azure healthy?\n3. **Review logs** - What do logs show?\n4. **Analyze metrics** - Performance patterns?\n5. **Investigate recent changes** - What changed?\n\n---\n\n## Troubleshooting Guides by Service\n\n| Service | Common Issues | Reference |\n|---------|---------------|-----------|\n| **Container Apps** | Image pull failures, cold starts, health probes, port mismatches | container-apps\u002F (`references\u002Fcontainer-apps\u002FREADME.md`) |\n| **Function Apps** | App details, invocation failures, timeouts, binding errors, cold starts, missing app settings | functions\u002F (`references\u002Ffunctions\u002FREADME.md`) |\n| **AKS** | Cluster access, nodes, `kube-system`, scheduling, crash loops, ingress, DNS, upgrades | AKS Troubleshooting (`aks-troubleshooting\u002Faks_troubleshooting.md`) |\n\n---\n\n## Routing\n\n- Keep Container Apps and Function Apps diagnostics in this parent skill.\n- Route active AKS incidents, AKS-specific intake, evidence gathering, and remediation guidance to AKS Troubleshooting (`aks-troubleshooting\u002Faks_troubleshooting.md`).\n\n---\n\n## Quick Reference\n\n### Common Diagnostic Commands\n\n```bash\n# Check resource health\naz resource show --ids RESOURCE_ID\n\n# View activity log\naz monitor activity-log list -g RG --max-events 20\n\n# Container Apps logs\naz containerapp logs show --name APP -g RG --follow\n\n# Function App logs (query App Insights traces)\naz monitor app-insights query --apps APP-INSIGHTS -g RG \\\n  --analytics-query \"traces | where timestamp > ago(1h) | order by timestamp desc | take 50\"\n```\n\n### AppLens (MCP Tools)\n\nFor AI-powered diagnostics, use:\n```\nmcp_azure_mcp_applens\n  intent: \"diagnose issues with \u003Cresource-name>\"\n  command: \"diagnose\"\n  parameters:\n    resourceId: \"\u003Cresource-id>\"\n\nProvides:\n- Automated issue detection\n- Root cause analysis\n- Remediation recommendations\n```\n\n### Azure Monitor (MCP Tools)\n\nFor querying logs and metrics:\n```\nmcp_azure_mcp_monitor\n  intent: \"query logs for \u003Cresource-name>\"\n  command: \"logs_query\"\n  parameters:\n    workspaceId: \"\u003Cworkspace-id>\"\n    query: \"\u003CKQL-query>\"\n```\n\nSee kql_queries.md (`references\u002Fkql_queries.md`) for common diagnostic queries.\n\n---\n\n## Check Azure Resource Health\n\n### Using MCP\n\n```\nmcp_azure_mcp_resourcehealth\n  intent: \"check health status of \u003Cresource-name>\"\n  command: \"get\"\n  parameters:\n    resourceId: \"\u003Cresource-id>\"\n```\n\n### Using CLI\n\n```bash\n# Check specific resource health\naz resource show --ids RESOURCE_ID\n\n# Check recent activity\naz monitor activity-log list -g RG --max-events 20\n```\n\n---\n\n## References\n\n- KQL Query Library (`references\u002Fkql_queries.md`)\n- Azure Resource Graph Queries (`references\u002Fazure_resource_graph.md`)\n- Function Apps Troubleshooting (`references\u002Ffunctions\u002FREADME.md`)\n","# Azure Diagnostics\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This document is the **official source** for debugging and troubleshooting Azure production issues. Follow these instructions to diagnose and resolve common Azure service problems systematically.\n\n## Triggers\n\nActivate this skill when user wants to:\n- Debug or troubleshoot production issues\n- Diagnose errors in Azure services\n- Analyze application logs or metrics\n- Fix image pull, cold start, or health probe issues\n- Investigate why Azure resources are failing\n- Find root cause of application errors\n- Troubleshoot Azure Function Apps (invocation failures, timeouts, binding errors)\n- Find the App Insights or Log Analytics workspace linked to a Function App\n- Troubleshoot AKS clusters, nodes, pods, ingress, or Kubernetes networking issues\n\n## Rules\n\n1. Start with systematic diagnosis flow\n2. Use AppLens (MCP) for AI-powered diagnostics when available\n3. Check resource health before deep-diving into logs\n4. Select appropriate troubleshooting guide based on service type\n5. Document findings and attempted remediation steps\n6. Route AKS incidents to the dedicated AKS troubleshooting document\n\n---\n\n## Quick Diagnosis Flow\n\n1. **Identify symptoms** - What's failing?\n2. **Check resource health** - Is Azure healthy?\n3. **Review logs** - What do logs show?\n4. **Analyze metrics** - Performance patterns?\n5. **Investigate recent changes** - What changed?\n\n---\n\n## Troubleshooting Guides by Service\n\n| Service | Common Issues | Reference |\n|---------|---------------|-----------|\n| **Container Apps** | Image pull failures, cold starts, health probes, port mismatches | container-apps\u002F (`references\u002Fcontainer-apps\u002FREADME.md`) |\n| **Function Apps** | App details, invocation failures, timeouts, binding errors, cold starts, missing app settings | functions\u002F (`references\u002Ffunctions\u002FREADME.md`) |\n| **AKS** | Cluster access, nodes, `kube-system`, scheduling, crash loops, ingress, DNS, upgrades | AKS Troubleshooting (`aks-troubleshooting\u002Faks_troubleshooting.md`) |\n\n---\n\n## Routing\n\n- Keep Container Apps and Function Apps diagnostics in this parent skill.\n- Route active AKS incidents, AKS-specific intake, evidence gathering, and remediation guidance to AKS Troubleshooting (`aks-troubleshooting\u002Faks_troubleshooting.md`).\n\n---\n\n## Quick Reference\n\n### Common Diagnostic Commands\n\n```bash\n# Check resource health\naz resource show --ids RESOURCE_ID\n\n# View activity log\naz monitor activity-log list -g RG --max-events 20\n\n# Container Apps logs\naz containerapp logs show --name APP -g RG --follow\n\n# Function App logs (query App Insights traces)\naz monitor app-insights query --apps APP-INSIGHTS -g RG \\\n  --analytics-query \"traces | where timestamp > ago(1h) | order by timestamp desc | take 50\"\n```\n\n### AppLens (MCP Tools)\n\nFor AI-powered diagnostics, use:\n```\nmcp_azure_mcp_applens\n  intent: \"diagnose issues with \u003Cresource-name>\"\n  command: \"diagnose\"\n  parameters:\n    resourceId: \"\u003Cresource-id>\"\n\nProvides:\n- Automated issue detection\n- Root cause analysis\n- Remediation recommendations\n```\n\n### Azure Monitor (MCP Tools)\n\nFor querying logs and metrics:\n```\nmcp_azure_mcp_monitor\n  intent: \"query logs for \u003Cresource-name>\"\n  command: \"logs_query\"\n  parameters:\n    workspaceId: \"\u003Cworkspace-id>\"\n    query: \"\u003CKQL-query>\"\n```\n\nSee kql_queries.md (`references\u002Fkql_queries.md`) for common diagnostic queries.\n\n---\n\n## Check Azure Resource Health\n\n### Using MCP\n\n```\nmcp_azure_mcp_resourcehealth\n  intent: \"check health status of \u003Cresource-name>\"\n  command: \"get\"\n  parameters:\n    resourceId: \"\u003Cresource-id>\"\n```\n\n### Using CLI\n\n```bash\n# Check specific resource health\naz resource show --ids RESOURCE_ID\n\n# Check recent activity\naz monitor activity-log list -g RG --max-events 20\n```\n\n---\n\n## References\n\n- KQL Query Library (`references\u002Fkql_queries.md`)\n- Azure Resource Graph Queries (`references\u002Fazure_resource_graph.md`)\n- Function Apps Troubleshooting (`references\u002Ffunctions\u002FREADME.md`)\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"version":46},"Microsoft","1.0.4","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_microsoft_azure_diagnostics",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill azure-diagnostics",{"tool":62,"command":63},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill azure-diagnostics",{"tool":65,"command":66},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill azure-diagnostics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_microsoft_azure_diagnostics\u002Fskill.md",true,[],[71,103,125,147,167,190],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":102},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,27,97,98,99,100,101],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":102},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[109],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[83,111,112,87,113,114,115,116,96,28,27,117,97,118,119,120,121,122,123,124],"react native","native","vercel react native skills","react native skills","modules","performance","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":102},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[131],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[83,133,134,87,135,116,136,27,137,117,97,138,139,140,141,142,143,144,145,146],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":102},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[153],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[155,87,156,143,157,158,159,160,146,161,162,163,27,164,117,97,165,166,98,83],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":102},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000010","后端与接口",[177,178,179,180,135,181,182,183,124,144,116,184,185,136,186,163,187,188,189,27],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":197,"publishedAt":212},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[196],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[198,199,200,201,202,93,203,160,36,96,204,205,27,83,206,207,208,209,210,211],"text","portable text serialization","portable","serialization","extracting","strings","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]