azure-cloud-migrate
**WORKFLOW SKILL** — Assess and migrate cross-cloud workloads to Azure. Generates assessment reports and converts code from AWS, GCP, or other providers to Azure services. WHEN: "migrate Lambda to Azure Functions", "migrate AWS to Azure", "convert AWS serverless to Azure", "migration readiness report", "cross-cloud migration". DO NOT USE FOR: greenfield Azure deployment (azure-prepare), Azure-only refactor (azure-prepare).
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 an excellent skill description that hits all the marks. It provides specific capabilities, rich natural trigger terms, explicit when/when-not guidance, and clear disambiguation from related skills. The DO NOT USE FOR clause is a particularly strong addition that reduces conflict risk with the azure-prepare skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Assess and migrate cross-cloud workloads to Azure', 'Generates assessment reports', 'converts code from AWS, GCP, or other providers to Azure services'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (assess and migrate cross-cloud workloads, generate reports, convert code) and 'when' (explicit WHEN clause with trigger phrases). Also includes a helpful DO NOT USE FOR clause that further clarifies boundaries. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'migrate Lambda to Azure Functions', 'migrate AWS to Azure', 'convert AWS serverless to Azure', 'migration readiness report', 'cross-cloud migration'. These are realistic phrases a user would type. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (cross-cloud migration TO Azure). The DO NOT USE FOR clause explicitly disambiguates from the related 'azure-prepare' skill for greenfield and Azure-only scenarios, minimizing conflict risk. | 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 workflow skill that serves as an effective orchestration overview. Its strengths are excellent progressive disclosure, clear sequential workflow with validation checkpoints, and concise token-efficient writing. The main weakness is that actionability relies heavily on referenced files — the SKILL.md itself contains no executable code or concrete migration commands, though this is somewhat justified by the complexity and variability of migration scenarios.
Suggestions
Consider adding a minimal concrete example in the Steps section showing what a typical MCP tool invocation looks like (e.g., the exact mcp_azure-mcp_documentation call for researching a target service), so the skill has at least one executable snippet.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Azure, AWS Lambda, or migration concepts are. Every section serves a clear purpose with no padding or unnecessary context. The table format is compact and scannable. | 3 / 3 |
Actionability | The skill provides a clear sequential workflow and references specific MCP tools and output directories, but the actual concrete guidance (code examples, specific commands) is deferred entirely to referenced files. The SKILL.md itself contains no executable code or copy-paste-ready commands. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit phases (create → assess → migrate → ask user → hand off). It includes a validation checkpoint via 'Ask User' before deployment, enforces sequential execution (Rule 1), mandates assessment before migration (Rule 2), and requires user confirmation for destructive actions (Rule 6). Progress tracking via migration-status.md adds another verification layer. | 3 / 3 |
Progressive Disclosure | Content is well-structured as an overview with clear one-level-deep references to specific files (assessment.md, code-migration.md, lambda-to-functions.md, workflow-details.md, global-rules.md). The 'Load these on demand — do NOT read all at once' instruction is excellent progressive disclosure guidance. References are clearly signaled with context about when to load them. | 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
- jonathan-vella/azure-agentic-infraops
- Commit
05d7617
- 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.