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.
Install with Tessl CLI
npx tessl i github:microsoft/azure-skills --skill azure-cloud-migrate94
Quality
92%
Does it follow best practices?
Impact
96%
2.66xAverage score across 3 eval scenarios
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 well-crafted skill description that excels across all dimensions. It clearly specifies concrete capabilities (assessment, code conversion, report generation), provides comprehensive trigger terms covering multiple cloud providers and migration scenarios, and explicitly separates the 'what' from the 'when' using a clear WHEN: clause. The Azure-specific focus creates strong distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Assess and migrate cross-cloud workloads', 'Generates assessment reports', 'converts code from AWS, GCP, or other providers to Azure services'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (assess workloads, generate reports, convert code) AND when with explicit 'WHEN:' clause listing specific trigger scenarios. The structure explicitly separates capabilities from usage triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural 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 AWS', 'migrate from GCP', 'cross-cloud migration'. These match real user language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on cross-cloud migration TO Azure. The specific mention of AWS, GCP, Lambda, Azure Functions creates distinct triggers 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 skill that excels at conciseness and progressive disclosure. The workflow is clear with proper sequencing and safety checkpoints. The main weakness is that actionability relies heavily on referenced files rather than providing inline executable examples, though this is partially justified by the complexity of migration scenarios.
Suggestions
Consider adding a minimal inline code snippet showing the basic structure of a migrated function to improve actionability without requiring navigation to reference files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what cloud migration is or how Azure works. Every line provides actionable guidance or essential structure. | 3 / 3 |
Actionability | Provides clear structure and references to detailed guides, but the main skill file lacks concrete code examples or executable commands. The actual implementation details are delegated to reference files. | 2 / 3 |
Workflow Clarity | Clear sequential phases with explicit validation checkpoint (ask_user before destructive actions). Steps are numbered, include a feedback loop via status tracking, and require assessment before migration. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise overview and well-signaled one-level-deep references. Migration scenarios table provides clear navigation, and detailed content is appropriately split into reference files. | 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.
Table of Contents
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.