CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is azure-cloud-migrate in microsoft/GitHub-Copilot-for-Azure

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-architected orchestration skill: lean overview body, verified one-level-deep reference structure, and a clearly sequenced workflow with user-interaction checkpoints. The only minor gaps are the absence of an explicit post-migration verification step and a couple of delegative steps whose details live entirely in references.

Suggestions

Add an explicit validation checkpoint between steps 3 and 4 (e.g., build/run the converted code in the output directory and record pass/fail in migration-status.md) to close the workflow-clarity gap.

Inline one concrete example of an assessment report deliverable (filename and a skeleton of its sections) so step 2 is fully self-contained without opening the reference guide.

DimensionReasoningScore

Conciseness

The ~40-line body is a lean rule list, a scenario table, and terse numbered steps; nothing explains concepts Claude already knows (the Kubernetes DNS note in rule 8 is a non-obvious gotcha, not filler). Not 4: there are no over-explanation instances left to trim — every token earns its place.

5 / 5

Actionability

Concrete and executable for an orchestration skill: exact MCP tool names ("mcp_azure_mcp_get_azure_bestpractices", "mcp_azure_mcp_documentation"), a precise output-directory convention, a quoted user prompt ("Migration complete. Test locally or deploy to Azure?"), and per-scenario guide links. Not 5: a few steps are delegative ("Hand off to azure-prepare", assessment details live in references) leaving minor gaps; not 3: the guidance is specific and directly executable, not high-level hints or pseudocode.

4 / 5

Workflow Clarity

Five numbered sequential steps with an explicit ordering rule ("Follow phases sequentially — do not skip"), assessment-before-migration gate, ask_user requirement for destructive actions (rule 6), a user decision checkpoint (step 4), and status tracking via migration-status.md. Not 5: there is no explicit verification step for the migrated output (e.g., build/test the converted code) in the body; not 3: checkpoints are present and explicit, not missing or implicit.

4 / 5

Progressive Disclosure

The body is a pure overview: a scenario table with clearly labeled one-level-deep links, and all 17 referenced paths verified to exist in the bundle; deeper detail (runtimes/*, per-scenario assessment and deployment guides) is correctly pushed to second-level files rather than inlined. Not 4: navigation is well-signaled with descriptive labels and the split is appropriate throughout, with no inline content that belongs in a separate file.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A model description: third-person voice, concrete capabilities, an explicit WHEN trigger list with natural synonyms and platform variants, and a distinct cross-cloud-to-Azure niche. All four dimensions sit at the top anchor.

DimensionReasoningScore

Specificity

"Assess and migrate cross-cloud workloads to Azure with reports and code conversion" names multiple concrete actions, and the enumerated mappings ("Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps") give comprehensive coverage of supported scenarios. Not 4: coverage spans both the actions and the full scenario matrix with no notable gaps.

5 / 5

Completeness

Explicitly answers both questions: the first sentence states what the skill does (assess, migrate, reports, code conversion) and "WHEN:" provides a concrete explicit trigger list. Not 4: the 'when' is not merely present but spelled out with specific trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

The WHEN clause lists natural user phrases with synonyms and acronym variants: "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". Not 4: this is comprehensive coverage including platform variations (ACA, ECS/GKE/EKS) a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

"Assess and migrate cross-cloud workloads to Azure" with named source→target pairs is a clear niche with distinct triggers (specific cloud platforms and migration phrasing), so conflict with unrelated skills is minimal. Not 4: the triggers are unmistakably Azure-migration-specific rather than overlapping with adjacent skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 18 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 18 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

microsoft/azure-skills

Path

.github/plugins/azure-skills/skills/azure-cloud-migrate/SKILL.md

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.