skills/microsoft/azure-upgrade/SKILL.md
Assess and upgrade Azure workloads between plans, tiers, or SKUs within Azure. Generates assessment reports and automates upgrade steps. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, migrate hosting plan, upgrade Functions SKU, move to Flex Consumption, upgrade Azure service tier, change hosting plan, upgrade function app plan, migrate App Service to Container Apps.
npx skillsauth add aiskillstore/marketplace azure-upgradeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill handles assessment and automated upgrades of existing Azure workloads from one Azure service, hosting plan, or SKU to another — all within Azure. This includes plan/tier upgrades (e.g. Consumption → Flex Consumption), cross-service migrations (e.g. App Service → Container Apps), and SKU changes. This is NOT for cross-cloud migration — use
azure-cloud-migratefor that.
| User Intent | Example Prompts | |-------------|-----------------| | Upgrade Azure Functions plan | "Upgrade my function app from Consumption to Flex Consumption" | | Change hosting tier | "Move my function app to a better plan" | | Assess upgrade readiness | "Is my function app ready for Flex Consumption?" | | Automate plan migration | "Automate the steps to upgrade my Functions plan" |
mcp_azure_mcp_get_bestpractices and mcp_azure_mcp_documentation MCP toolsask_user — global-rules| Source | Target | Reference | |--------|--------|-----------| | Azure Functions Consumption Plan | Azure Functions Flex Consumption Plan | consumption-to-flex.md |
No matching scenario? Use
mcp_azure_mcp_documentationandmcp_azure_mcp_get_bestpracticestools to research the upgrade path.
| Tool | Purpose |
|------|---------|
| mcp_azure_mcp_get_bestpractices | Get Azure best practices for the target service |
| mcp_azure_mcp_documentation | Look up Azure documentation for upgrade scenarios |
| mcp_azure_mcp_appservice | Query App Service and Functions plan details |
| mcp_azure_mcp_applicationinsights | Verify monitoring configuration |
azure-validate for deep validation or azure-deploy for CI/CD setupTrack progress in upgrade-status.md inside the workspace root.
After upgrade is validated, hand off to:
azure-validate — for thorough post-upgrade validationazure-deploy — if the user wants to set up CI/CD for the new appdevelopment
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.