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 communicates specific migration capabilities from multiple cloud platforms to Azure services. It uses third person voice, lists concrete source→target mappings, and includes an explicit WHEN clause with comprehensive natural trigger terms. The description is concise yet thorough, covering both the 'what' and 'when' effectively.
| 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, supporting specific migration paths) and 'when' (explicit WHEN clause listing numerous trigger scenarios like 'migrate Lambda to Functions', 'AWS to Azure', etc.). | 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', 'cross-cloud migration'. These are highly natural phrases a user would type. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: cross-cloud migration specifically to Azure. The specific source-to-target mappings (Lambda→Functions, Beanstalk→App Service, etc.) make it very unlikely to conflict with other skills. The domain is narrow and well-defined. | 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 routing/orchestration skill that efficiently maps multiple cloud migration scenarios to detailed reference guides. Its strengths are excellent progressive disclosure, a clear sequential workflow with validation checkpoints, and token-efficient presentation. Its main weakness is the lack of any concrete executable examples or commands in the SKILL.md itself — all actionability is delegated to referenced files that weren't provided for evaluation.
Suggestions
Consider adding one brief concrete example (e.g., a sample assessment report snippet or a single migration command) to make the SKILL.md itself more actionable without requiring reference file lookups.
| 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 table) 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 routing document 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 user confirmation for destructive actions, Rule 7 mandates progress reporting, and the workflow includes a validation checkpoint (step 4 asks user before proceeding). The 'follow phases sequentially — do not skip' rule reinforces discipline. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a concise overview and routing table, with well-signaled one-level-deep references to scenario-specific assessment, migration, and deployment guides. The migration scenarios table provides clear navigation to the appropriate reference for each source/target combination. | 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/azure-skills
- Commit
d02fd24
- 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.