azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with migration reports and code conversion guidance. Supports AWS, GCP, and other providers. WHEN: migrate Lambda to Azure Functions, migrate AWS to Azure, Lambda migration assessment, convert AWS serverless to Azure, migration readiness report, migrate from AWS, migrate from GCP, cross-cloud migration.
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 clearly defines its scope (cross-cloud migration to Azure), lists concrete capabilities (assessment, migration reports, code conversion), and provides an explicit WHEN clause with diverse, natural trigger terms. The description is concise yet comprehensive, covering both the what and when effectively while maintaining a distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'assess and migrate cross-cloud workloads', 'migration reports', 'code conversion guidance'. It names specific services like Lambda to Azure Functions and specifies supported providers (AWS, GCP). | 3 / 3 |
Completeness | Clearly answers both 'what' (assess and migrate cross-cloud workloads with migration reports and code conversion guidance) and 'when' (explicit WHEN clause with multiple trigger scenarios like Lambda migration, AWS to Azure migration, etc.). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'migrate Lambda to Azure Functions', 'migrate AWS to Azure', 'Lambda migration assessment', 'convert AWS serverless to Azure', 'migration readiness report', 'migrate from GCP', 'cross-cloud migration'. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: cross-cloud migration specifically to Azure, with named source providers (AWS, GCP) and specific service pairs (Lambda to Azure Functions). Unlikely to conflict with general cloud or coding 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 organizes a complex multi-step migration workflow. Its strengths are excellent progressive disclosure, lean content, and clear workflow sequencing with appropriate checkpoints. The main weakness is that actionability relies heavily on referenced files, so the skill itself provides limited directly executable guidance.
Suggestions
Consider adding a brief concrete example of what the assessment output or migration-status.md looks like to improve actionability without bloating the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of what cloud migration is or how Azure works. The table format for scenarios is efficient, and rules are terse but clear. | 3 / 3 |
Actionability | The steps are concrete and sequenced, but the actual executable guidance is delegated to referenced files (assessment.md, code-migration.md, etc.). The skill itself lacks concrete code examples or commands that Claude could directly execute. | 2 / 3 |
Workflow Clarity | Clear sequential phases with explicit ordering (assess before migrate), a validation checkpoint via ask_user before destructive actions, a handoff step, and progress tracking via migration-status.md. The rule 'do not skip' phases reinforces the sequence. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview that delegates details to clearly signaled one-level-deep references (assessment.md, code-migration.md, global-rules.md, workflow-details.md). Navigation is easy with inline links in both the table and steps. | 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
9d594ab
- 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.