azure-cloud-migrate
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, 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 purpose (cross-cloud migration to Azure), lists concrete actions (assessment reports, code conversion), and provides an explicit WHEN clause with diverse, natural trigger terms. The description is concise, uses third-person voice correctly, and carves out a distinct niche that would be easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Assess and migrate cross-cloud workloads', '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 assessment reports, convert code) and 'when' with an explicit 'WHEN:' clause listing specific trigger scenarios. | 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 specific source platforms (AWS, GCP) and specific service types (Lambda, serverless). Unlikely to conflict with general coding or cloud 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, clear sequential workflow with validation checkpoints, and token-efficient presentation. The main weakness is that actionable details (concrete code examples, specific commands) are entirely delegated to referenced files, making the skill itself more of a routing document than a self-contained guide.
Suggestions
Consider adding a brief concrete example of what the assessment report output looks like (even a 3-4 line snippet) to make the skill more self-contained and actionable without requiring reference file loading.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose — rules, scenario table, output directory convention, steps, and reference index. No unnecessary explanations of what cloud migration is or how Azure works. | 3 / 3 |
Actionability | The steps are clear and sequenced, but the actual concrete guidance is delegated to referenced files (assessment.md, code-migration.md, etc.). The skill itself contains no executable code or specific commands — it's an orchestration overview that relies heavily on external references for actionable details. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit phases (create → assess → migrate → ask user → hand off). It includes a validation checkpoint via the ask_user step before deployment, enforces sequential execution in Rule #1, requires assessment before code migration in Rule #2, and mandates user confirmation for destructive actions. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview and well-signaled one-level-deep references. The reference index table with 'When to Load' guidance and the explicit instruction 'Load these on demand — do NOT read all at once' demonstrate thoughtful content organization. | 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
ec7b8ff
- 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.