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.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured overview that delegates executable detail to a real, well-organized reference bundle with clear navigation and a sequenced, validated workflow. Its only weakness is that concrete code/commands and full feedback loops live in references rather than the body itself.

Suggestions

Inline one or two short executable snippets (e.g., a sample assessment-report skeleton or an MCP tool invocation example) so the body is self-sufficient for the most common case without requiring a reference hop.

Add an explicit validate→fix→retry checkpoint in the Steps section (e.g., re-run assessment validation after code conversion and only proceed on pass) to lift workflow_clarity toward 5.

Surface the migration-status.md progress-tracking format briefly in the body so the feedback loop is visible without opening workflow-details.md.

Dimension	Reasoning	Score
Conciseness	The ~44-line body is lean and assumes Claude's competence: no concept explanations of Azure or migration, every rule adds non-obvious value (e.g. rule 8's Kubernetes DNS-resolution gotcha), matching the lean/every-token-earns-its-place anchor.	5 / 5
Actionability	Concrete guidance via named MCP tools, explicit output-directory convention, a scenario→reference table, and a sequenced step list, but the executable detail lives in referenced files rather than as copy-paste code/commands in the body, fitting the 4 (mostly executable, minor gaps) anchor rather than 5.	4 / 5
Workflow Clarity	Clear sequenced steps with validation checkpoints (assessment before migration, ask_user for destructive actions, a final ask-user gate, progress tracking in migration-status.md); the destructive-operation cap does not apply since validation is present, but explicit validate→fix→retry feedback loops are delegated to references rather than shown inline, placing it at 4 not 5.	4 / 5
Progressive Disclosure	A clear overview body with well-signaled one-level-deep references; every referenced path resolves to a real bundle file organized under services/{functions,app-service,container-apps}/, matching the clear-overview/easy-navigation anchor.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, concise, and explicitly covers both what the skill does and when to use it with concrete trigger phrases and a comprehensive scenario mapping. It is a strong example of a high-quality skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Assess and migrate cross-cloud workloads to Azure with reports and code conversion') plus a comprehensive source→target mapping, matching the comprehensive-coverage anchor rather than the 4 anchor which expects minor gaps.	5 / 5
Completeness	Explicitly answers what ('Assess and migrate cross-cloud workloads to Azure with reports and code conversion') and when (a labeled 'WHEN:' clause with concrete trigger phrases), matching the 5 anchor exactly; not the 4 anchor since 'when' is explicit and specific rather than weakly stated.	5 / 5
Trigger Term Quality	The WHEN clause enumerates natural phrases users would say ('migrate Lambda to Functions', 'AWS to Azure', 'Fargate to ACA', 'ECS/Kubernetes/GKE/EKS to Container Apps', 'cross-cloud migration') with synonyms and service aliases, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Clear niche (cross-cloud migration to Azure) with distinct source→target triggers unlikely to fire for unrelated skills, matching the clear-niche/minimal-conflict anchor.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 18 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 18 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: microsoft/azure-skills
Path: .github/plugins/azure-skills/skills/azure-cloud-migrate/SKILL.md
Commit: 9d46511

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.