[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AA863ZPDSHCZDRW5KCZR3":3,"skill-same:01M69AA863ZPDSHCZDRW5KCZR3":58},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M69AA863ZPDSHCZDRW5KCZR3","azure-functions-setup",null,"Verify prerequisites and set up your environment for Azure Functions development","microsoft\u002Fazure-dev-tools","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A91XHRQE41P3D1XV8V707",10,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools\u002Fblob\u002Fmain\u002Fcanvases\u002Fazure-functions\u002Fskills\u002Fazure-functions-setup\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"setup","azure functions setup","azure","azure functions","functions","development","SET","verify","environment","up","for","2026-11-10 10:12:30",false,"---\nname: azure-functions-setup\ndescription: \"Verify prerequisites and set up your environment for Azure Functions development\"\n---\n\n> **Language**: Always respond in the same language the user is using.\n\n# azure-functions-setup — Azure Functions Environment Setup\n\nVerify that the developer's environment has all prerequisites for Azure Functions development.\n\n## Checks\n\nRun each check and report results:\n\n```bash\naz --version        # Azure CLI ≥ 2.60 (≥ 2.87.0 for Go deployments)\nazd version         # Azure Developer CLI, required for Azure Skills deployment workflows\nfunc --version      # Azure Functions Core Tools ≥ 4.x (≥ 4.12 for Go projects)\nnode --version      # Node.js 24 or 22 for new Node.js\u002FTypeScript projects\npython --version    # Python 3.13 preferred; 3.10-3.13 supported for Python projects\npython3 --version   # Use this fallback when python is not on PATH\ndotnet --version    # .NET SDK ≥ 8.0 (if .NET project)\ngo version          # Go 1.24 or later (if Go project; Go support is in preview)\n```\n\nRun the language checks that match the user's project or stated intent. Do not report a missing Go toolchain as a problem for a Python project, and do not report a missing Python interpreter as a problem for a Go project.\n\n## Azure Skills Plugin Check\n\nAzure Functions deployment is proxied through the Azure Skills deployment workflow. For deployment scenarios, verify that the Azure Skills plugin is installed and that these skills are available:\n\n- `azure-prepare`\n- `azure-validate`\n- `azure-deploy`\n\n**How to detect availability**: Check your current tool\u002Fskill list for the above skill names. If they appear in the list of available skills (e.g., in `\u003Cavailable_skills>` or equivalent plugin registry), they are installed. You do not need to run any commands — the presence of these skills in the agent's tool list is sufficient confirmation.\n\nIf the Azure Skills plugin is missing, install it for the active host before using `azure-functions-deploy`.\n\n| Host | Install guidance |\n|------|------------------|\n| GitHub Copilot CLI | `\u002Fplugin marketplace add microsoft\u002Fazure-skills`, then `\u002Fplugin install azure@azure-skills` |\n| Claude Code | `\u002Fplugin install azure@claude-plugins-official` |\n| Codex CLI | `codex plugin marketplace add microsoft\u002Fazure-skills`, then install `azure` from `\u002Fplugins` |\n| VS Code | Install the Azure MCP extension and companion Azure Skills integration, then reload VS Code |\n| GitHub Copilot fallback | `npx skills add https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Ftree\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills -a github-copilot -g -y` |\n\n## Output Format\n\nPresent results as a checklist:\n\n```\nAzure Functions Environment Check\n\n  ✅ Azure CLI          \u003Cversion>\n  ✅ Azure Developer CLI \u003Cversion>\n  ✅ Core Tools         \u003Cversion>\n  ✅ Node.js            \u003Cversion>\n  ⚠️  Azure subscription  Not logged in → Run 'az login'\n  ⚠️  Azure Skills plugin Missing → install before azure-functions-deploy\n```\n\n## Fix Instructions\n\nFor each failing check, provide:\n1. **What's wrong** — one-line description\n2. **How to fix** — exact install\u002Ffix command for the user's OS and shell\n3. **Docs link** — Microsoft Learn URL\n\nUse the user's operating system when choosing fix commands. Do **not** give Linux-only installation commands to Windows or macOS users. If the operating system or package manager is unclear, show the OS-specific choices and ask the user to run the one that matches their machine.\n\nFor language runtimes, prefer the latest Azure Functions **GA-supported** version for new installs. Do not recommend preview runtimes unless the user explicitly asks for previews.\n\n| Tool | Recommended version | Windows | macOS | Linux | Docs |\n|------|---------------------|---------|-------|-------|------|\n| Azure CLI | Latest stable, ≥ 2.60; **≥ 2.87.0 for Go** | `winget install --exact --id Microsoft.AzureCLI` | `brew update && brew install azure-cli` | Use the distro-specific Microsoft Learn command for your package manager | https:\u002F\u002Flearn.microsoft.com\u002Fcli\u002Fazure\u002Finstall-azure-cli |\n| Azure Developer CLI | Latest stable | `winget install --exact --id Microsoft.Azd` | `brew install azure\u002Fazd\u002Fazd` | Use the Microsoft Learn instructions for your distro or install the signed `.deb`\u002F`.rpm` package from the Azure Developer CLI release | https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fdeveloper\u002Fazure-developer-cli\u002Finstall-azd |\n| Core Tools | v4.x; **4.12 or later for Go** | Download and run the v4.x 64-bit MSI installer from Microsoft Learn | `brew tap azure\u002Ffunctions && brew install azure-functions-core-tools@4` | Use the Microsoft package repository for your distro, then install `azure-functions-core-tools-4` | https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-functions\u002Ffunctions-run-local |\n| Node.js | Node.js 24 GA for new apps; Node.js 22 also supported | `winget install --exact --id OpenJS.NodeJS.LTS` or `fnm install 24` | `brew install node@24` or `fnm install 24` | Use your distro package manager or a version manager such as `fnm install 24` | https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-functions\u002Ffunctions-versions |\n| Python | Python 3.13 GA for new apps; 3.10-3.13 supported | `winget install --exact --id Python.Python.3.13` | `brew install python@3.13` | Use your distro package manager or a version manager such as `pyenv install 3.13` | https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-functions\u002Ffunctions-versions |\n| .NET SDK | .NET 8 LTS minimum; use the latest GA version supported by the target Functions model | `winget install --exact --id Microsoft.DotNet.SDK.8` | `brew install --cask dotnet-sdk` | Use the Microsoft Learn instructions for your distro | https:\u002F\u002Flearn.microsoft.com\u002Fdotnet\u002Fcore\u002Finstall\u002F |\n| Go | Go 1.24 or later (Go support is in preview) | `winget install --exact --id GoLang.Go` | `brew install go` | Use your distro package manager or the official tarball from the Go downloads page | https:\u002F\u002Fgo.dev\u002Fdl\u002F |\n\nAzure Functions runtime 4.x currently supports Node.js 24 and 22 for Node.js\u002FTypeScript apps, and Python 3.10 through 3.13 for Python apps. Python 3.14 can appear in preview; keep Python 3.13 as the default recommendation until the user opts into preview support. Mention hosting caveats when relevant: newer language versions might not be available on Linux Consumption, so Flex Consumption is the safer default for new Linux-hosted apps.\n\n### Go prerequisites\n\nGo support on Azure Functions is in **public preview**. Say so before recommending it for production work.\n\nGo has two version floors that no other language has.\n\n- **Core Tools 4.12 or later.** The `native` worker that runs Go ships in 4.12. Earlier 4.x versions reject a Go project with a misleading \"unsupported worker runtime\" error, so compare the reported `func --version` against 4.12 rather than only checking for a `4.` prefix.\n- **Azure CLI 2.87.0 or later**, needed when creating Azure resources or deploying packages. The general 2.60 floor used elsewhere in this checklist is not sufficient for Go, so a Go environment can otherwise be reported as ready when it is not. Check with `az version`.\n\nIf the installed Core Tools or Azure CLI is present but below the Go floor, report it as a failing check and give the upgrade command for the user's platform.\n\nGo projects also use `FUNCTIONS_WORKER_RUNTIME=native` in `local.settings.json`, not `go` or `golang`. Mention this when a Go project is detected, because it is the most common local configuration mistake.\n\nScaffold Go projects with `func init \u003Cproject-name> --worker-runtime go`. `func new` is not supported for Go.\n\nSee https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-functions\u002Ffunctions-reference-go for the authoritative prerequisite list.\n\n## After Setup\n\nAfter the environment check completes, report the checklist and recommend the most relevant next skill. No local setup state is created or updated.\n\nWhen all checks pass, suggest the next step:\n\n> ✅ Your environment is ready! Next:\n> - Use **azure-functions-create** to scaffold a new Azure Functions project (HTTP triggers, timer triggers, queue triggers, etc.)\n> - Use **azure-functions-hosted-skills** to build cloud-hosted, event-driven intelligent capabilities with Markdown, Functions triggers, code, tools, HTTP, and MCP\n\nFor deployment, confirm the Azure Skills plugin is available before suggesting **azure-functions-deploy**. `azure-functions-deploy` delegates to `azure-prepare`, `azure-validate`, and `azure-deploy`.\n\n## Next steps\n\n- On success, suggest `azure-functions-create` for traditional Functions projects, or `azure-functions-hosted-skills` for Azure Functions Hosted Skills — let the user choose based on their goal.\n- On failure, keep the user in `azure-functions-setup`: explain fixes, then ask them to rerun setup verification.\n- If deployment is requested and Azure Skills is missing, keep the user in `azure-functions-setup` until the Azure Skills plugin is installed or the user explicitly chooses a fallback deployment path.\n","> **Language**: Always respond in the same language the user is using.\n\n# azure-functions-setup — Azure Functions Environment Setup\n\nVerify that the developer's environment has all prerequisites for Azure Functions development.\n\n## Checks\n\nRun each check and report results:\n\n```bash\naz --version        # Azure CLI ≥ 2.60 (≥ 2.87.0 for Go deployments)\nazd version         # Azure Developer CLI, required for Azure Skills deployment workflows\nfunc --version      # Azure Functions Core Tools ≥ 4.x (≥ 4.12 for Go projects)\nnode --version      # Node.js 24 or 22 for new Node.js\u002FTypeScript projects\npython --version    # Python 3.13 preferred; 3.10-3.13 supported for Python projects\npython3 --version   # Use this fallback when python is not on PATH\ndotnet --version    # .NET SDK ≥ 8.0 (if .NET project)\ngo version          # Go 1.24 or later (if Go project; Go support is in preview)\n```\n\nRun the language checks that match the user's project or stated intent. Do not report a missing Go toolchain as a problem for a Python project, and do not report a missing Python interpreter as a problem for a Go project.\n\n## Azure Skills Plugin Check\n\nAzure Functions deployment is proxied through the Azure Skills deployment workflow. For deployment scenarios, verify that the Azure Skills plugin is installed and that these skills are available:\n\n- `azure-prepare`\n- `azure-validate`\n- `azure-deploy`\n\n**How to detect availability**: Check your current tool\u002Fskill list for the above skill names. If they appear in the list of available skills (e.g., in `\u003Cavailable_skills>` or equivalent plugin registry), they are installed. You do not need to run any commands — the presence of these skills in the agent's tool list is sufficient confirmation.\n\nIf the Azure Skills plugin is missing, install it for the active host before using `azure-functions-deploy`.\n\n| Host | Install guidance |\n|------|------------------|\n| GitHub Copilot CLI | `\u002Fplugin marketplace add microsoft\u002Fazure-skills`, then `\u002Fplugin install azure@azure-skills` |\n| Claude Code | `\u002Fplugin install azure@claude-plugins-official` |\n| Codex CLI | `codex plugin marketplace add microsoft\u002Fazure-skills`, then install `azure` from `\u002Fplugins` |\n| VS Code | Install the Azure MCP extension and companion Azure Skills integration, then reload VS Code |\n| GitHub Copilot fallback | `npx skills add https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-skills\u002Ftree\u002Fmain\u002F.github\u002Fplugins\u002Fazure-skills\u002Fskills -a github-copilot -g -y` |\n\n## Output Format\n\nPresent results as a checklist:\n\n```\nAzure Functions Environment Check\n\n  ✅ Azure CLI          \u003Cversion>\n  ✅ Azure Developer CLI \u003Cversion>\n  ✅ Core Tools         \u003Cversion>\n  ✅ Node.js            \u003Cversion>\n  ⚠️  Azure subscription  Not logged in → Run 'az login'\n  ⚠️  Azure Skills plugin Missing → install before azure-functions-deploy\n```\n\n## Fix Instructions\n\nFor each failing check, provide:\n1. **What's wrong** — one-line description\n2. **How to fix** — exact install\u002Ffix command for the user's OS and shell\n3. **Docs link** — Microsoft Learn URL\n\nUse the user's operating system when choosing fix commands. Do **not** give Linux-only installation commands to Windows or macOS users. If the operating system or package manager is unclear, show the OS-specific choices and ask the user to run the one that matches their machine.\n\nFor language runtimes, prefer the latest Azure Functions **GA-supported** version for new installs. Do not recommend preview runtimes unless the user explicitly asks for previews.\n\n| Tool | Recommended version | Windows | macOS | Linux | Docs |\n|------|---------------------|---------|-------|-------|------|\n| Azure CLI | Latest stable, ≥ 2.60; **≥ 2.87.0 for Go** | `winget install --exact --id Microsoft.AzureCLI` | `brew update && brew install azure-cli` | Use the distro-specific Microsoft Learn command for your package manager | https:\u002F\u002Flearn.microsoft.com\u002Fcli\u002Fazure\u002Finstall-azure-cli |\n| Azure Developer CLI | Latest stable | `winget install --exact --id Microsoft.Azd` | `brew install azure\u002Fazd\u002Fazd` | Use the Microsoft Learn instructions for your distro or install the signed `.deb`\u002F`.rpm` package from the Azure Developer CLI release | https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fdeveloper\u002Fazure-developer-cli\u002Finstall-azd |\n| Core Tools | v4.x; **4.12 or later for Go** | Download and run the v4.x 64-bit MSI installer from Microsoft Learn | `brew tap azure\u002Ffunctions && brew install azure-functions-core-tools@4` | Use the Microsoft package repository for your distro, then install `azure-functions-core-tools-4` | https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-functions\u002Ffunctions-run-local |\n| Node.js | Node.js 24 GA for new apps; Node.js 22 also supported | `winget install --exact --id OpenJS.NodeJS.LTS` or `fnm install 24` | `brew install node@24` or `fnm install 24` | Use your distro package manager or a version manager such as `fnm install 24` | https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-functions\u002Ffunctions-versions |\n| Python | Python 3.13 GA for new apps; 3.10-3.13 supported | `winget install --exact --id Python.Python.3.13` | `brew install python@3.13` | Use your distro package manager or a version manager such as `pyenv install 3.13` | https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-functions\u002Ffunctions-versions |\n| .NET SDK | .NET 8 LTS minimum; use the latest GA version supported by the target Functions model | `winget install --exact --id Microsoft.DotNet.SDK.8` | `brew install --cask dotnet-sdk` | Use the Microsoft Learn instructions for your distro | https:\u002F\u002Flearn.microsoft.com\u002Fdotnet\u002Fcore\u002Finstall\u002F |\n| Go | Go 1.24 or later (Go support is in preview) | `winget install --exact --id GoLang.Go` | `brew install go` | Use your distro package manager or the official tarball from the Go downloads page | https:\u002F\u002Fgo.dev\u002Fdl\u002F |\n\nAzure Functions runtime 4.x currently supports Node.js 24 and 22 for Node.js\u002FTypeScript apps, and Python 3.10 through 3.13 for Python apps. Python 3.14 can appear in preview; keep Python 3.13 as the default recommendation until the user opts into preview support. Mention hosting caveats when relevant: newer language versions might not be available on Linux Consumption, so Flex Consumption is the safer default for new Linux-hosted apps.\n\n### Go prerequisites\n\nGo support on Azure Functions is in **public preview**. Say so before recommending it for production work.\n\nGo has two version floors that no other language has.\n\n- **Core Tools 4.12 or later.** The `native` worker that runs Go ships in 4.12. Earlier 4.x versions reject a Go project with a misleading \"unsupported worker runtime\" error, so compare the reported `func --version` against 4.12 rather than only checking for a `4.` prefix.\n- **Azure CLI 2.87.0 or later**, needed when creating Azure resources or deploying packages. The general 2.60 floor used elsewhere in this checklist is not sufficient for Go, so a Go environment can otherwise be reported as ready when it is not. Check with `az version`.\n\nIf the installed Core Tools or Azure CLI is present but below the Go floor, report it as a failing check and give the upgrade command for the user's platform.\n\nGo projects also use `FUNCTIONS_WORKER_RUNTIME=native` in `local.settings.json`, not `go` or `golang`. Mention this when a Go project is detected, because it is the most common local configuration mistake.\n\nScaffold Go projects with `func init \u003Cproject-name> --worker-runtime go`. `func new` is not supported for Go.\n\nSee https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Fazure-functions\u002Ffunctions-reference-go for the authoritative prerequisite list.\n\n## After Setup\n\nAfter the environment check completes, report the checklist and recommend the most relevant next skill. No local setup state is created or updated.\n\nWhen all checks pass, suggest the next step:\n\n> ✅ Your environment is ready! Next:\n> - Use **azure-functions-create** to scaffold a new Azure Functions project (HTTP triggers, timer triggers, queue triggers, etc.)\n> - Use **azure-functions-hosted-skills** to build cloud-hosted, event-driven intelligent capabilities with Markdown, Functions triggers, code, tools, HTTP, and MCP\n\nFor deployment, confirm the Azure Skills plugin is available before suggesting **azure-functions-deploy**. `azure-functions-deploy` delegates to `azure-prepare`, `azure-validate`, and `azure-deploy`.\n\n## Next steps\n\n- On success, suggest `azure-functions-create` for traditional Functions projects, or `azure-functions-hosted-skills` for Azure Functions Hosted Skills — let the user choose based on their goal.\n- On failure, keep the user in `azure-functions-setup`: explain fixes, then ask them to rerun setup verification.\n- If deployment is requested and Azure Skills is missing, keep the user in `azure-functions-setup` until the Azure Skills plugin is installed or the user explicitly chooses a fallback deployment path.\n",{"name":5,"description":7},"main","9718865ce93334acfc18b60111a6c0f68078c672","canvases\u002Fazure-functions\u002Fskills\u002Fazure-functions-setup",3,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 13:42:21",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add microsoft\u002Fazure-dev-tools --skill azure-functions-setup",{"tool":50,"command":51},"bunx","bunx skills add microsoft\u002Fazure-dev-tools --skill azure-functions-setup",{"tool":53,"command":54},"pnpm","pnpm dlx skills add microsoft\u002Fazure-dev-tools --skill azure-functions-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools\u002Fblob\u002Fmain\u002Fcanvases\u002Fazure-functions\u002Fskills\u002Fazure-functions-setup\u002FSKILL.md",true,[],[59,84,108,129,155,176],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":70,"publishedAt":30},"01M69AAPPZ3X1ZW6Z9MARMQ3YK","create-canvas-app","Create a canvas app with the native create-canvas skill and Microsoft Canvas Toolkit. Includes counter and read-only Azure resource-group starters.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools\u002Fblob\u002Fmain\u002Fplugins\u002Fcanvas-authoring\u002Fskills\u002Fcreate-canvas-app\u002FSKILL.md",[65],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[71,72,73,74,75,76,9,77,21,78,79,80,81,82,83],"create canvas app","canvas app","canvas","create canvas","app","create","read-only","only","toolkit","with","native","read","starters",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":30},"01M69AAMY1DX5TJ1N0Q60Z5G1X","containers","Open the Containers canvas for existing local Docker or Podman containers, Compose apps and images: what is running, stopped or restarting; container or combined Compose logs; CPU, memory, ports, files; lifecycle controls; image layers and provenance. Compose apps are discovered and grouped automatically. Not for writing Dockerfiles or Compose files, deploying Compose apps, registry or cloud container services, or build failures that never produced a container.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools\u002Fblob\u002Fmain\u002Fcanvases\u002Fcontainers\u002Fskills\u002Fcontainers\u002FSKILL.md",[],[86,91,92,93,73,94,95,96,97,98,99,29,100,101,102,103,104,105,106,107],"writing","memory","docker","images","running","ports","never","combined","compose","layers","lifecycle","local","podman","container","open","files","controls",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":30},"01M69AAGF20QEM47TVZP0C70KJ","azure-storage","Open Azure Storage canvas first to browse storage accounts, containers, blobs, queues, tables and file shares, run bulk transfers with live progress, filter with statistics, mint SAS links, and plan account to account copies. Not for provisioning storage accounts or infrastructure as code.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools\u002Fblob\u002Fmain\u002Fcanvases\u002Fazure-storage\u002Fskills\u002Fazure-storage\u002FSKILL.md",[],[115,116,21,86,73,117,118,119,120,121,29,122,105,123,124,125,126,80,127,128],"azure storage","storage","infrastructure as code","bulk","as","links","browse","transfers","file","code","statistics","filter","plan","progress",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":139,"publishedAt":30},"01M69AAECE5MQ51C8ZPNTPZHQH","azure-sre-agent-canvas","Open SRE Agent Canvas for failing Azure apps, ICM\u002FS360 tickets, connected investigation follow-ups, evidence, hypotheses, blockers and incident handoffs. Also operates SRE incidents, tasks, connectors and memories. Not for plugin development\u002Ftesting, infrastructure implementation or unrelated KQL authoring.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools\u002Fblob\u002Fmain\u002Fcanvases\u002Fazure-sre-agent\u002Fskills\u002Fazure-sre-agent-canvas\u002FSKILL.md",[135,136],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},{"categoryNo":137,"categoryName":138,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000023","Skill与智能体开发",[140,141,73,142,21,143,144,145,146,147,148,24,29,149,150,151,152,105,153,154],"azure sre agent","azure sre agent canvas","sre","connectors","testing","follow-ups","kql","memories","evidence","plugin development","incident","incidents","failing","apps","tasks",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":30},"01M69AACDBB35GRPDCNDYH63GF","azure-resources-query","Use only for explicit requests to list, find or browse existing Azure resource inventory as the answer, explicit requests to open Azure Resources Query, or refinements clearly referring to its current results. Not for incidental discovery in another workflow, single-resource details, counts, text-only answers, writing\u002Fexplaining KQL, code\u002Fdocs\u002Frouting discussions, telemetry, creation, deployment, configuration, access changes or sign-in.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools\u002Fblob\u002Fmain\u002Fcanvases\u002Fazure-resources-query\u002Fskills\u002Fazure-resources-query\u002FSKILL.md",[],[162,163,21,164,165,91,166,167,119,146,168,121,29,169,170,171,172,173,105,174,78,175],"azure resources query","resources","query","telemetry","docs","workflow","creation","discovery","deployment","answer","inventory","resource inventory","single","use",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":30},"01M69AA9XFNM3D25MKEX94GFMQ","azure-functions-update","Use only when the user explicitly asks to use or resume azure-functions-update by name. Migrate Azure Functions programming models and configuration through an approved scenario. Current scenarios: C# in-process to .NET isolated worker, Python programming model v1 to v2, Python Blob SDK type bindings, Python HTTP streaming, extension bundles v1-v3 to v4, and the Durable Functions extension v1 or v2 to a current version. Language-version and hosting-plan updates are separate handoffs. Do not select this workflow from a generic update request or a name in a question, quotation, file, or review.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazure-dev-tools\u002Fblob\u002Fmain\u002Fcanvases\u002Fazure-functions\u002Fskills\u002Fazure-functions-update\u002FSKILL.md",[],[183,184,21,23,22,167,185,186,187,188,189,190,191,78,192,193,194,195,196,127,197,198],"azure functions update","update","sdk","review","python","azure-functions","model","select","worker","question","when","updates","migrate","streaming","request","scenario"]