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

91%

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

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-engineered orchestrator skill: a lean routing body that points to a complete, well-signaled bundle, with concrete tool names, an exact output convention, and a gated sequential workflow. The only improvements are cosmetic — consolidating duplicated scenario-guide links and surfacing an explicit validate/retry checkpoint in the top-level steps.

Suggestions

Consolidate the duplicated assessment/code-migration links: keep them in the Steps section only, or in the scenario table only, rather than repeating them in both places.

Add one explicit validation checkpoint line to the Steps (e.g., after Migrate: verify the converted code builds/passes the scenario guide's checks before asking the user), so the feedback loop lives in the top-level workflow rather than only in workflow-details.md.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanation of what Azure or Kubernetes is, terse rules ('Follow phases sequentially — do not skip'), and a dense scenario table. It falls just short of the 5 anchor because of minor redundancy: the assessment and code-migration links for Functions and App Service appear both in the scenario table row/parentheticals and again in Steps 2–3, and could be consolidated.

4 / 5

Actionability

For an orchestration-style skill the guidance is fully executable: named MCP tools ('mcp_azure_mcp_get_azure_bestpractices', 'mcp_azure_mcp_documentation'), an exact output-directory convention, the exact user prompt to ask ('Migration complete. Test locally or deploy to Azure?'), a concrete DNS-audit heuristic with an example hostname ('http://order-service:3001'), and explicit per-scenario file pointers for every step. Specific examples cover all eight common cases; nothing remains at the vague-direction level.

5 / 5

Workflow Clarity

The Steps section gives a clear, explicitly sequential workflow (Create → Assess → Migrate → Ask User → Hand off) with real checkpoints: assessment must precede migration (Rule 2), destructive actions require ask_user (Rule 6), and progress is tracked in migration-status.md. It is a 4 rather than 5 because explicit verify-and-retry feedback loops are not stated in the body itself — they are delegated to workflow-details.md and the scenario guides, which the anchors treat as a minor validation gap rather than an absent one.

4 / 5

Progressive Disclosure

Scored against the actual bundle: every link in the body (16 distinct paths across functions/app-service/container-apps plus workflow-details.md) resolves to a real file, and the body is a pure overview — rules, a scenario routing table, an output convention, and steps, with no inlined bulk content. References are one level deep from SKILL.md and clearly signaled via the table; deeper material (per-runtime rules, assessment/deployment guides) is appropriately split into bundle files that the scenario files link with clear tables, which is exactly the intended disclosure pattern.

5 / 5

Total

18

/

20

Passed

Description

95%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 strong description: concrete capabilities with an enumerated scenario matrix, an explicit WHEN trigger clause dense with natural user phrasings and acronym synonyms, and a clearly delimited niche. The only softness is that the action verbs are somewhat high-level relative to the specificity of the mapping list.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Assess and migrate cross-cloud workloads to Azure with reports and code conversion') and explicit source→target mappings ('Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps'). It sits at the 4 anchor — several specific actions with minor gaps — rather than 5 because the verbs themselves ('assess', 'migrate') are high-level and less granular than the multi-verb 5 anchor example.

4 / 5

Completeness

It explicitly answers both questions: 'what' (assess and migrate cross-cloud workloads to Azure with reports and code conversion, with the supported scenario set enumerated) and 'when' (an explicit 'WHEN:' clause listing concrete trigger phrases). This is a direct match to the 5 anchor; the 4 anchor's 'when could be more explicit' does not apply given the dedicated WHEN list.

5 / 5

Trigger Term Quality

The WHEN clause covers natural user phrasings comprehensively with synonyms and acronyms: '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'. This matches the 5 anchor's comprehensive synonym coverage; no common variation of these migration requests is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clearly delimited — cross-cloud migration to Azure with named source/target pairs (Lambda→Functions, Fargate to ACA) — so it is unlikely to trigger for unrelated skills. Matches the 5 anchor ('clear niche with distinct triggers; minimal conflict risk'); the acronym-stuffed WHEN list slightly stretches natural language but does not create overlap risk.

5 / 5

Total

19

/

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/GitHub-Copilot-for-Azure

Path

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.