azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with migration reports and code conversion. Supports AWS Lambda→Functions, Kubernetes→Container Apps, Cloud Run→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, Lambda assessment, convert serverless to Azure, readiness report, from AWS, from GCP, Cloud Run to Container Apps, Kubernetes 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
Advisory
Suggest reviewing before use
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 specific migration capabilities across cloud platforms, provides an explicit and comprehensive WHEN clause with natural trigger terms, and occupies a distinct niche. The description is concise yet thorough, covering both the actions performed and the scenarios that should trigger its use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'assess and migrate cross-cloud workloads', 'migration reports', 'code conversion', and names specific migration paths like 'AWS Lambda→Functions', '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 across specific platforms) and 'when' (explicit WHEN clause with a comprehensive list of trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrate Lambda to Functions', 'AWS to Azure', 'Lambda assessment', 'convert serverless to Azure', 'readiness report', 'from AWS', 'from GCP', 'Cloud Run to Container Apps', 'GKE to Azure', 'EKS to Container Apps'. These are highly natural phrases a user would type. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: cross-cloud migration specifically to Azure, with named source platforms (AWS, GCP) and specific service-to-service migration paths. 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 to scenario-specific references while maintaining clear sequencing and safety constraints. Its main weakness is that the inline content lacks concrete executable examples — the actionable detail lives entirely in referenced files. For a routing/orchestration skill this is reasonable, but a single concrete example (e.g., a sample assessment output snippet) would strengthen actionability.
Suggestions
Consider adding a brief concrete example of what a migration-status.md entry or assessment report snippet looks like, so Claude has an inline reference for expected output format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose — rules are terse, the scenario table is compact, and there's no explanation of what Azure or Lambda is. The skill assumes Claude's competence throughout. | 3 / 3 |
Actionability | The steps are clear but high-level (Assess, Migrate, Ask User, Hand off) without executable code or concrete commands inline. The actual actionable detail is deferred to referenced files, so the skill itself reads more like a routing document than a hands-on guide. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit ordering rules ('follow phases sequentially — do not skip'), a validation gate ('generate assessment before any code migration'), destructive-action safeguards via ask_user, progress tracking in migration-status.md, and a clear hand-off step. The feedback loop for user confirmation before deployment is present. | 3 / 3 |
Progressive Disclosure | The skill is a concise overview that cleanly routes to one-level-deep references via a well-structured table and inline links (assessment, code-migration, workflow-details, global-rules). Navigation is clear and references are well-signaled. | 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
742d20b
- 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.