azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.
75
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its purpose (cross-cloud migration to Azure), lists specific migration paths with concrete source and target platforms, and includes an explicit WHEN clause with comprehensive trigger terms. The description is concise yet thorough, covering multiple cloud providers and service types without being verbose or vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Assess and migrate cross-cloud workloads to Azure with reports and code conversion' and enumerates specific migration paths like 'Lambda→Functions', 'Beanstalk/Heroku/App Engine→App Service', 'Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps'. | 3 / 3 |
Completeness | Clearly answers both 'what' (assess and migrate cross-cloud workloads to Azure with reports and code conversion, with specific source→target mappings) and 'when' (explicit 'WHEN:' clause listing numerous trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrate Lambda to Functions', 'AWS to Azure', 'migrate Beanstalk', 'migrate Heroku', 'Cloud Run migration', 'Fargate to ACA', 'ECS/Kubernetes/GKE/EKS to Container Apps', 'Spring Boot to Container Apps'. These are highly specific and match real user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: cross-cloud migration specifically to Azure. The specific source-to-target platform mappings (Lambda→Functions, Heroku→App Service, etc.) make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that serves effectively as a migration dispatcher. Its strengths are excellent progressive disclosure via the scenario routing table, clear sequential workflow with validation checkpoints, and token-efficient presentation. The main weakness is that the SKILL.md itself contains no executable code or concrete commands—all actionability is delegated to referenced files, which makes it slightly less self-contained.
Suggestions
Consider adding a brief concrete example of the output directory naming convention (e.g., 'If workspace root is `my-lambda-app/`, output goes to `my-lambda-app-azure/`') to reduce ambiguity without significant token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It avoids explaining what Azure, Lambda, or containers are. Every section serves a purpose: rules, scenario routing table, output conventions, and steps. No unnecessary padding or concept explanations. | 3 / 3 |
Actionability | The skill provides clear structural guidance (phases, output directory naming, scenario routing) and references specific MCP tools, but lacks executable code examples or concrete commands. The actual migration steps are delegated entirely to referenced files, so the SKILL.md itself is more of a dispatcher than an actionable guide. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit ordering (assess before migrate, ask user before deploy). Rule 6 requires destructive action confirmation, Rule 7 mandates progress reporting, and the workflow includes a validation checkpoint (Step 4 asks user before proceeding). The feedback loop for service discovery audit (Rule 8) adds robustness. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a concise overview/router with a well-organized scenario table linking to specific reference files. References are one level deep and clearly signaled with descriptive link text. Content is appropriately split between the overview and detailed guides. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/github-copilot-for-azure
- Commit
915f809
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.