Apex Azure Upgrade
jonathan-vella/apex
ANALYSIS SKILL — Assess in-Azure upgrades of existing workloads: Functions Consumption to Flex Consumption, and Azure Cache for Redis to Azure Managed Redis.
Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code.
Install Azure Upgrade
$ npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/GitHub-Copilot-for-Azure azure-upgrade --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft/GitHub-Copilot-for-Azure.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/azure-skills/skills/azure-upgrade .claude/skills/azure-upgrade && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "azure-upgrade" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-skills/skills/azure-upgrade into .claude/skills/azure-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-upgrade", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-skills/skills/azure-upgradeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/GitHub-Copilot-for-Azure azure-upgrade --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/GitHub-Copilot-for-Azure.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/azure-skills/skills/azure-upgrade .agents/skills/azure-upgrade && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azure-upgrade" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-skills/skills/azure-upgrade into .agents/skills/azure-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-upgrade", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/GitHub-Copilot-for-Azure azure-upgrade --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/GitHub-Copilot-for-Azure.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/azure-skills/skills/azure-upgrade .cursor/skills/azure-upgrade && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "azure-upgrade" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-skills/skills/azure-upgrade into .cursor/skills/azure-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-upgrade", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft/GitHub-Copilot-for-Azure.git --path plugins/azure-skills/skills/azure-upgrade--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/GitHub-Copilot-for-Azure azure-upgrade --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/GitHub-Copilot-for-Azure.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/azure-skills/skills/azure-upgrade .gemini/skills/azure-upgrade && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "azure-upgrade" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-skills/skills/azure-upgrade into .gemini/skills/azure-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-upgrade", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft/GitHub-Copilot-for-Azure azure-upgradeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft/GitHub-Copilot-for-Azure.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/azure-skills/skills/azure-upgrade .github/skills/azure-upgrade && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "azure-upgrade" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-skills/skills/azure-upgrade into .github/skills/azure-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-upgrade", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft/GitHub-Copilot-for-Azure azure-upgrade --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/GitHub-Copilot-for-Azure.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/azure-skills/skills/azure-upgrade .opencode/skills/azure-upgrade && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "azure-upgrade" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-skills/skills/azure-upgrade into .opencode/skills/azure-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-upgrade", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
azure-upgrade- GitHub stars
- 255
- Used in
- 1 other repo
- Token cost
- ~1.5k tokens
- SKILL.md length
- 592 words
- Files
- 38 (incl. references)
- Skills in repo
- 56
- Repo updated
- First seen
- Licence
- MIT
At a glance
Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code.
- Works in 8 steps: Follow phases sequentially — do not skip → Generate an assessment before any… → Load the scenario reference and follow… → …
- Tasks that involve Legacy modernization
- SKILL.md covers Triggers, Rules, Upgrade Scenarios and MCP Tools, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Azure Upgrade is an agent skill from microsoft/GitHub-Copilot-for-Azure, published by the product's own GitHub organization. Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 43 other files, including reference files (for example `references/global-rules.md`, `references/languages/java/INSTRUCTION.md` and `references/languages/java/README.md`). Compatibility notes: python3.10+
It sits in Databases, covering Legacy modernization. It works with Microsoft Azure, Redis, Java and Azure Functions. The repository describes itself as: GitHub Copilot for Azure. The licence is MIT.
When your agent uses it
- Tasks that involve Legacy modernization
Example prompts
- “/azure-upgrade”
Requirements
- Compatibility (from SKILL.md): python3.10+
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Follow phases sequentially — do not skip
- Generate an assessment before any upgrade operations
- Load the scenario reference and follow its rules
- Use mcp_azure_mcp_get_azure_bestpractices and mcp_azure_mcp_documentation MCP tools
- Destructive actions require ask_user — global-rules
- Always confirm the target plan/SKU with the user before proceeding
- Never delete or stop the original app without explicit user confirmation
- All automation scripts must be idempotent and resumable
What it can do on your machine
Read from SKILL.md and the folder at commit d8f4f4e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
python3.10+
From compatibility in the SKILL.md frontmatter.
Context cost
Azure Upgrade loads about 1.5k tokens when it runs, and up to ~42k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 592 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from microsoft/GitHub-Copilot-for-Azure at commit d8f4f4e, republished under its MIT licence (© microsoft). 592 words, ~1,542 tokens.
Download SKILL.mdSave it as
.claude/skills/azure-upgrade/SKILL.md (or your agent's skills folder). This skill also uses 37 other files; get the full folder from GitHub.- name
- azure-upgrade
- description
- Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).
- compatibility
- python3.10+
- license
- MIT
- metadata.author
- Microsoft
- metadata.version
- 0.0.0-placeholder
Azure Upgrade
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. It also covers Azure SDK for Java source-code modernization (e.g. legacy Java
com.microsoft.azure.*→ moderncom.azure.*). This is NOT for cross-cloud migration — useazure-cloud-migratefor that.
Triggers
| 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" |
| Modernize legacy Azure Java SDK | "Migrate legacy Azure SDKs for Java", "Upgrade legacy Azure Java SDK", "Migrate my Java project from com.microsoft.azure to com.azure" |
| Migrate Azure Cache for Redis (ACR/OSS) to Azure Managed Redis (AMR) | "Migrate my Redis cache to AMR", "ACR to AMR", "OSS to AMR", "Upgrade my Premium P2 cache to Managed Redis", "Pick an AMR SKU", "Convert my Redis IaC template to AMR" |
| Migrate Azure Cache for Redis Enterprise (ACRE) to Azure Managed Redis (AMR) | "Migrate my Enterprise_E10 cache to AMR", "ACRE to AMR", "Update my ACRE IaC template for AMR", "Migrate EnterpriseFlash to AMR", "Migrate my geo-replicated Enterprise Redis" |
Rules
- Follow phases sequentially — do not skip
- Generate an assessment before any upgrade operations
- Load the scenario reference and follow its rules
- Use
mcp_azure_mcp_get_azure_bestpracticesandmcp_azure_mcp_documentationMCP tools - Destructive actions require
ask_user— global-rules - Always confirm the target plan/SKU with the user before proceeding
- Never delete or stop the original app without explicit user confirmation
- All automation scripts must be idempotent and resumable
Upgrade Scenarios
| Source | Target | Reference |
|---|---|---|
| Azure Functions Consumption Plan | Azure Functions Flex Consumption Plan | consumption-to-flex.md |
Legacy Azure Java SDK (com.microsoft.azure.*) | Modern Azure Java SDK (com.azure.*) | languages/java/README.md |
| Azure Cache for Redis (ACR/OSS) Basic/Standard/Premium | Azure Managed Redis (AMR) | services/redis/redis-to-amr.md |
| Azure Cache for Redis Enterprise (ACRE) / Enterprise Flash | Azure Managed Redis (AMR) | services/redis/redis-to-amr.md |
SDK upgrade scenarios (e.g. Java legacy → modern) run a source-code modernization flow that is distinct from Azure service/plan/SKU upgrades: follow the scenario reference, not the Steps below.
No matching scenario? Use
mcp_azure_mcp_documentationandmcp_azure_mcp_get_azure_bestpracticestools to research the upgrade path.
Show full SKILL.md (209 more words)Show less
MCP Tools
| Tool | Purpose |
|---|---|
mcp_azure_mcp_get_azure_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 |
Steps
- Identify — Determine the source and target Azure plans/SKUs. Ask user to confirm.
- Assess — Analyze existing app for upgrade readiness → load scenario reference (e.g., consumption-to-flex.md)
- Pre-migrate — Collect settings, identities, configs from the existing app
- Upgrade — Execute the automated upgrade steps (create new resources, migrate settings, deploy code)
- Validate — Hit the function app default URL to confirm the app is reachable, then verify endpoints and monitoring
- Ask User — "Upgrade complete. Would you like to verify performance, clean up the old app, or update your IaC?"
- Hand off to
azure-validatefor deep validation orazure-deployfor CI/CD setup
Track progress in upgrade-status.md inside the workspace root.
References
- Global Rules
- Workflow Details
- Functions
- Redis
- Redis (ACR or ACRE) to AMR Migration — routes to dedicated amr-migration-skill (ACR/OSS) or acre-to-amr-migration-skill (Enterprise)
- Java SDK Migration Templates
Next
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 app
© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 37 other files (references) in plugins/azure-skills/skills/azure-upgrade of microsoft/GitHub-Copilot-for-Azure.
- SKILL.md
- references/global-rules.md
- references/languages/java/INSTRUCTION.md
- references/languages/java/README.md
- references/languages/java/bom-migration/bom-gradle-settings.md
- references/languages/java/bom-migration/bom-gradle-toml.md
- references/languages/java/bom-migration/bom-gradle.md
- references/languages/java/bom-migration/bom-maven.md
- references/languages/java/bom-migration/bom-migration.md
- references/languages/java/bom-migration/bom-validation.md
- references/languages/java/package-specific/com.microsoft.azure.eventprocessorhost.md
- references/languages/java/package-specific/com.microsoft.azure.management.md
- references/languages/java/rules/efficiency.md
- references/languages/java/rules/execution-guidelines.md
- references/languages/java/rules/review-code-changes.md
- … and 23 more
Open the folder on GitHubat commit d8f4f4e
Used in 3 other repositories
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in microsoft/GitHub-Copilot-for-Azure, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Azure Upgrade next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azure Upgrade this skillmicrosoft/GitHub-Copilot-for-Azure | 255 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Apex Azure Upgradejonathan-vella/apex | 217 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Extend Commands APIredis/lettuce | 5.8k | — | ~7.7k | Automated safety check: Notes | MIT | |
| Writing Javadocredis/lettuce | 5.8k | — | ~809 | Automated safety check: Pass | MIT | |
| Apex Azure Reliabilityjonathan-vella/apex | 217 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Azsdk Common Generate SDK LocallyAzure/azure-sdk-for-android | 121 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Extend Commands API
redis/lettuce
Add or extend Redis commands in the Lettuce client API end-to-end — a new core command, a family of new commands, an extension to an existing command's options, or a module/area command…
- Official
Writing Javadoc
redis/lettuce
A skill your agent uses when writing or editing Javadoc for Lettuce public API — new methods, classes, deprecations, or when a reviewer asks to fix or improve doc comments.
Apex Azure Reliability
jonathan-vella/apex
ANALYSIS SKILL — Read-only reliability assessment for App Service and Azure Functions: zone redundancy, ZRS storage, health probes and multi-region failover.
- Official
Azsdk Common Generate SDK Locally
Azure/azure-sdk-for-android
Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization.
- Official
Azure Data API Builder
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure Data Api Builder development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and…
More from microsoft/GitHub-Copilot-for-Azure
All 56 skills in this repo- Official
Capacity
microsoft/GitHub-Copilot-for-Azure
Discovers available Azure OpenAI model capacity across regions and projects.
- Official
Deploy Model
microsoft/GitHub-Copilot-for-Azure
Unified Azure OpenAI model deployment skill with intelligent intent-based routing.
- Official
Entra Agent Id
microsoft/GitHub-Copilot-for-Azure
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant)…
- Official
Microsoft Foundry
microsoft/GitHub-Copilot-for-Azure
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end.
- Official
Azure Storage
microsoft/GitHub-Copilot-for-Azure
Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake.
- Official
Azure Diagnostics
microsoft/GitHub-Copilot-for-Azure
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.
Related
Categories
Questions about Azure Upgrade
What does Azure Upgrade do?
Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. Azure Upgrade is an agent skill from microsoft/GitHub-Copilot-for-Azure, published by the product's own GitHub organization. Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code.
When should I use Azure Upgrade?
Azure Upgrade fits situations like: tasks that involve Legacy modernization.
How do I install Azure Upgrade in Claude Code?
Run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a claude-code`. Or copy the skill folder (plugins/azure-skills/skills/azure-upgrade in microsoft/GitHub-Copilot-for-Azure) into .claude/skills/azure-upgrade in your project. Claude Code loads it when a task matches its description.
How do I install Azure Upgrade in Codex?
Run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a codex`. Or copy the skill folder (plugins/azure-skills/skills/azure-upgrade in microsoft/GitHub-Copilot-for-Azure) into .agents/skills/azure-upgrade in your project. Codex loads it when a task matches its description.
Can I use Azure Upgrade in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-upgrade, .gemini/skills/azure-upgrade, .github/skills/azure-upgrade and .opencode/skills/azure-upgrade in your project.
What does Azure Upgrade need to run?
SKILL.md names no scripts, command-line tools or credentials: Azure Upgrade is instructions for the agent only. Compatibility (from SKILL.md): python3.10+.
Does Azure Upgrade access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Azure Upgrade safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Azure Upgrade use?
Azure Upgrade is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azure Upgrade use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 40k tokens, read only when the agent opens those files.
What are the alternatives to Azure Upgrade?
Skills that share tags, products or a category with Azure Upgrade: Apex Azure Upgrade (jonathan-vella/apex, 217 stars), Extend Commands API (redis/lettuce, 5.8k stars), Writing Javadoc (redis/lettuce, 5.8k stars) and Apex Azure Reliability (jonathan-vella/apex, 217 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azure Upgrade?
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/GitHub-Copilot-for-Azure, which has 255 GitHub stars. The repository holds 56 skills in this directory. The repository was last updated on October 7, 2026.
Source: microsoft/GitHub-Copilot-for-Azure on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.