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.

72

Quality

90%

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

80%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.

The content is well-structured and token-efficient, using progressive disclosure to push scenario detail into verified references. Its main gap is workflow validation: a destructive/batch migration skill should include an explicit verify-the-output checkpoint before hand-off.

Suggestions

Add an explicit validation step in the Steps (e.g., 'Verify — build/run the migrated project locally; only proceed on success') before the Ask User / Hand off steps to satisfy the destructive/batch validation requirement.

Inline one or two short, copy-paste-ready commands for the most common action (e.g., the initial output-directory creation or a representative code-conversion snippet) to lift actionability toward fully executable.

Make the error-recovery loop explicit for assessment failures (assess → review errors → re-assess) so the workflow has a clear feedback loop rather than only a forward sequence.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a tight rules list, a dense scenario table, and terse steps with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Concrete guidance is present (output directory name, specific MCP tool names, reference links, a named code-scanning task with an example hostname), but the actual code-conversion execution is deferred to referenced files rather than given as inline copy-paste-ready steps.

4 / 5

Workflow Clarity

A clear five-step sequence with a destructive-action ask_user gate exists, but the workflow lacks an explicit validation/verification checkpoint before hand-off; per the rubric, destructive/batch skills missing validation are capped at 3.

3 / 5

Progressive Disclosure

The body is a concise overview with well-signaled one-level-deep references organized in a per-service table; all referenced bundle files exist and the structure is easy to navigate.

5 / 5

Total

17

/

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.

The description is strong across all dimensions: it names concrete actions, enumerates comprehensive source→target scenarios, provides an explicit WHEN trigger clause, and uses a distinctive third-person voice. It is both specific and well-scoped.

DimensionReasoningScore

Specificity

Lists concrete actions ('Assess and migrate', 'reports', 'code conversion') plus an enumerated set of source→target mappings, giving comprehensive coverage across eight migration scenarios.

5 / 5

Completeness

Explicitly answers both 'what' (assess and migrate cross-cloud workloads with reports and code conversion) and 'when' via a concrete WHEN: clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases a user would actually say ('migrate Lambda to Functions', 'AWS to Azure', 'migrate Beanstalk', 'Cloud Run migration', 'Fargate to ACA', 'Spring Boot to Container Apps', 'cross-cloud migration') with synonym coverage (ECS/Kubernetes/GKE/EKS).

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (cross-cloud workloads to Azure) with distinct, specific triggers and minimal overlap risk with unrelated 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.

Validation14 / 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
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.