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.
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill azure-cloud-migrate94
Does it follow best practices?
Evaluation — 96%
↑ 2.66xAgent success when using this skill
Validation for skill structure
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 provides specific capabilities (assessment, code conversion, report generation), includes an explicit 'WHEN:' clause with comprehensive trigger terms that users would naturally use, and carves out a distinct niche for cross-cloud Azure migration that won't conflict with other skills.
| 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 (explicit 'WHEN:' clause with multiple trigger scenarios). The explicit trigger guidance is comprehensive. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user terms: '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 how users would naturally phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Azure-specific migration from other cloud providers. The specific mention of AWS, GCP, Lambda, Azure Functions creates a unique fingerprint 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 skill that excels at conciseness and progressive disclosure. The workflow is clear with appropriate validation checkpoints and user confirmation requirements. The main weakness is that actionability relies heavily on referenced files rather than providing inline executable examples, though this may be appropriate given the complexity of cloud migration scenarios.
Suggestions
Consider adding a minimal inline code snippet showing the basic structure of a migrated function to make the skill more immediately actionable 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 lacks concrete code examples or executable commands directly in the skill. The actual migration logic is delegated to reference files. | 2 / 3 |
Workflow Clarity | Clear sequential phases with explicit validation checkpoint (Ask User before proceeding). Rule 1 enforces sequential execution, Rule 6 requires user confirmation for destructive actions, and progress tracking is specified. | 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.
- 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.