CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-cloud-migrate

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.

71

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 routing/orchestration skill that efficiently directs Claude to the right migration scenario and reference materials. Its strengths are excellent progressive disclosure, concise presentation, and clear scenario mapping. Its main weaknesses are the lack of concrete executable examples at the top level and missing explicit validation checkpoints in the workflow.

Suggestions

Add a validation/verification step between 'Migrate' and 'Ask User' (e.g., 'Verify converted code compiles/lints successfully before presenting to user') to strengthen the workflow and catch errors early.

Include a brief concrete example of what a migration-status.md entry looks like, so Claude knows the expected tracking format without needing to load the referenced file.

DimensionReasoningScore

Conciseness

The skill is lean and efficient. It avoids explaining what cloud migration is, what Lambda or Azure Functions are, or any other concepts Claude already knows. Every section serves a clear purpose: rules, scenario routing, output conventions, and steps.

3 / 3

Actionability

The skill provides clear structural guidance (phases, scenario table, output directory conventions) and references specific MCP tools, but lacks executable code examples or concrete commands. The actual migration logic is delegated entirely to referenced files, so the SKILL.md itself is more of a routing document than an actionable guide.

2 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced and includes an ask_user checkpoint before deployment. However, validation/verification steps are largely absent from the main workflow — there's no explicit 'validate migration output' step before asking the user, and feedback loops for error recovery are not described at this level.

2 / 3

Progressive Disclosure

Excellent progressive disclosure structure. The SKILL.md serves as a concise overview and routing table, with well-organized one-level-deep references to scenario-specific assessment, code-migration, and deployment guides. The migration scenarios table provides clear navigation to the appropriate reference for each source/target combination.

3 / 3

Total

10

/

12

Passed

Description

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 specific migration paths as concrete capabilities, and provides an explicit WHEN clause with comprehensive trigger terms. The description is concise yet thorough, covering multiple cloud platforms and service mappings that users would naturally reference.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: assess and migrate workloads, generate reports, perform code conversion. Also enumerates specific migration paths (Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps).

3 / 3

Completeness

Clearly answers both 'what' (assess and migrate cross-cloud workloads with reports and code conversion, with specific migration paths) and 'when' (explicit WHEN clause listing numerous trigger scenarios like 'migrate Lambda to Functions', 'AWS to Azure', etc.).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'migrate Lambda to Functions', 'AWS to Azure', 'migrate Beanstalk', 'migrate Heroku', 'Cloud Run migration', 'Fargate to ACA', 'ECS/Kubernetes/GKE/EKS to Container Apps', 'Spring Boot to Container Apps', 'cross-cloud migration'. These are highly natural phrases a user would type.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Azure-targeted cross-cloud migration with specific source-to-target mappings. The enumerated migration paths (Lambda→Functions, Beanstalk→App Service, etc.) make it very unlikely to conflict with other skills.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/github-copilot-for-azure
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.