azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with migration reports and code conversion. Supports Lambda→Functions, Fargate→Container Apps, Kubernetes→Container Apps, Cloud Run→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, Lambda assessment, convert serverless, readiness report, from AWS, from GCP, Cloud Run migration, Fargate to ACA, ECS to Container Apps, Kubernetes to ACA, GKE to Azure, EKS to Container Apps.
94
92%
Does it follow best practices?
Impact
Pending
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 excels across all dimensions. It clearly specifies concrete capabilities (assessment, migration, code conversion), enumerates specific supported migration paths, and provides an extensive WHEN clause with natural trigger terms covering multiple cloud providers and service names. The description is concise yet comprehensive, and its specificity to Azure migration makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'assess and migrate cross-cloud workloads', 'migration reports', 'code conversion', and enumerates specific migration paths (Lambda→Functions, Fargate→Container Apps, Kubernetes→Container Apps, Cloud Run→Container Apps). | 3 / 3 |
Completeness | Clearly answers both 'what' (assess and migrate cross-cloud workloads with migration reports and code conversion) and 'when' (explicit WHEN clause with extensive trigger phrases covering multiple migration scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrate Lambda to Functions', 'AWS to Azure', 'convert serverless', 'Cloud Run migration', 'Fargate to ACA', 'ECS to Container Apps', 'GKE to Azure', 'EKS to Container Apps'. These cover multiple cloud providers and common abbreviations users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: cross-cloud migration specifically to Azure. The specific migration paths (Lambda→Functions, Fargate→Container Apps, etc.) and cloud-specific terminology 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 orchestration skill that efficiently routes migration scenarios to detailed reference guides. Its strengths are excellent progressive disclosure, clear workflow sequencing with validation checkpoints, and token-efficient presentation. The main weakness is that actionability depends heavily on the referenced files — the SKILL.md itself contains no executable code or concrete migration examples, though this is appropriate for a routing/orchestration skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose — rules, scenario table, output directory, and steps are all tightly written without explaining concepts Claude already knows. No unnecessary padding or background explanations. | 3 / 3 |
Actionability | The skill provides clear structural guidance (phases, output directory conventions, scenario routing) and references specific MCP tools, but lacks executable code examples. The actual migration logic is delegated entirely to referenced files which aren't available for evaluation, so the SKILL.md itself gives direction rather than concrete executable steps. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit phases (create → assess → migrate → ask user → hand off). It includes validation checkpoints: assessment must precede code migration (rule 2), destructive actions require user confirmation (rule 6), and progress tracking via migration-status.md. The ask_user step before deployment is a good feedback loop. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a concise overview with a well-organized scenario table linking to specific assessment, migration, and deployment guides. References are one level deep and clearly signaled with descriptive link text. The table format makes scenario discovery easy. | 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
771a666
- 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.