CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-to-aws

Migrate Microsoft Azure workloads to AWS. Triggers on: Azure to AWS, move off Azure, AKS to EKS, App Service or Azure VMs to AWS compute, Azure SQL/Database to RDS, Cosmos DB to DynamoDB, Azure OpenAI to Bedrock, Azure cost estimates, or what-if workshops. Discovery uses the authenticated read-only `az` CLI, Terraform, a Resource Discovery for Azure (RDfA) report, and app code, with optional consent-gated OpenAI, OpenRouter, and Anthropic usage APIs. Terraform is optional. Runs Discover, Clarify, Design, Estimate, optional repricing, Generate, and Feedback; Clarify gates later phases and Generate is opt-in. Bicep/ARM discovery is not implemented; billing-export discovery is not implemented. Do not use for GCP or Heroku migrations, reverse migrations, general AWS architecture, or Azure-to-Azure refactoring.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 mature, well-orchestrated SKILL.md for a complex multi-phase migration: concrete paths, prompts, and validation checklists throughout, with an unusually disciplined progressive-disclosure and context-budget design. The main costs are conciseness — time-sensitive status facts and meta-commentary embedded in prose that could be sectioned or trimmed — and multi-level reference chains that occasionally rely on shorthand path mentions.

Suggestions

Move time-sensitive facts (the April 2026 App Runner policy, the 404 share-link status, and the build-status blockquote) into a single '## Status / Deprecated' section so they are easy to re-verify and do not penalize the evergreen prose.

Trim meta-commentary asides (e.g. 'the rule has no mechanical teeth and depends on the interpreter honoring it', 'not artifact-patching to pass a gate') to their operative one-line rule; the rationale can live in INTERPRETER.md.

Use full paths (or define a phase-directory convention once) for shorthand mentions like 'clarify.md § Step 0.5' and 'generate.md' so every reference is unambiguous from SKILL.md alone.

DimensionReasoningScore

Conciseness

The body is information-dense with no basic-concept padding, but it could be tightened: meta-commentary asides ('which CI binds but never evaluates — the rule has no mechanical teeth', 'this is reconstruction of ground truth, not artifact-patching to pass a gate') and time-sensitive facts ('no longer accepting new customers as of April 2026', the 404 share-link status, the build-status blockquote) sit in running prose rather than a dedicated status/deprecated section where they would not rot or cost re-reading. Mostly efficient with some trimmable explanation — the 3 anchor; not 4 because the unsectioned time-sensitive information and chatty parentheticals go beyond 'minor instances'.

3 / 5

Actionability

Guidance is highly concrete for an orchestration skill: exact load targets ('Load it first ... references/vendored/dsl/INTERPRETER.md', 'begin at references/phases/discover/discover.md'), copy-paste output strings ('Unrecognized phase: [value]. Valid phases: discover, clarify, design, estimate, workshop, generate, feedback.'), exact A/B prompts, and specific defaults (us-east-1, db.t4g.micro-class, USD, 2-18 weeks). Matches the 4 anchor (mostly executable with minor gaps); not 5 because much of the executable detail is deferred to reference files and some instructions remain conditional prose.

4 / 5

Workflow Clarity

Cold/warm start rules, mandatory Clarify gating, the run_mode consent gate, and a 7-rule state-validation checklist with STOP conditions and artifact-based recovery ('Enumerate $MIGRATION_DIR and infer completed phases from artifacts ... Confirmation is the safety net') give a clear sequence with most checkpoints and genuine feedback loops. It falls short of 5 only because the phase sequence itself is delegated to INTERPRETER.md frontmatter rather than restated, and one gate is acknowledged as having 'no mechanical teeth'.

4 / 5

Progressive Disclosure

Scored against the actual bundle: SKILL.md is a routing overview over a well-organized tree (phases/ orchestrators plus fragments, design-refs/ with an index.md, shared/ and vendored/ with READMEs), with explicit conditional-loading rules and a ~800-line per-phase budget — every referenced path checked exists. Matches the 4 anchor (good structure, references mostly clear, minor gaps); not 5 because references are more than one level deep (phase file to fragment to shared extract file) and several mentions use shorthand ('clarify.md § Step 0.5', 'generate.md') without full paths.

4 / 5

Total

15

/

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.

An exemplary description: it states concrete capabilities and inputs, gives an explicit trigger list with natural user phrasings, defines both what and when, and fences off wrong-skill cases with explicit exclusions. Dense but not padded — every clause carries information.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'Migrate Microsoft Azure workloads to AWS', 'Runs Discover, Clarify, Design, Estimate, optional repricing, Generate, and Feedback', discovery via 'the authenticated read-only `az` CLI, Terraform, a Resource Discovery for Azure (RDfA) report, and app code' — and even states explicit non-capabilities ('Bicep/ARM discovery is not implemented'). This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); it exceeds the 4 anchor because there are no meaningful coverage gaps.

5 / 5

Completeness

It explicitly answers both what (migration actions, discovery sources, phase pipeline) and when ('Triggers on: ...' plus negative scope 'Do not use for GCP or Heroku migrations, reverse migrations, general AWS architecture, or Azure-to-Azure refactoring'). Clear what AND when with concrete trigger phrases — the exact 5 anchor example pattern; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

'Triggers on: Azure to AWS, move off Azure, AKS to EKS, App Service or Azure VMs to AWS compute, Azure SQL/Database to RDS, Cosmos DB to DynamoDB, Azure OpenAI to Bedrock, Azure cost estimates, or what-if workshops' covers both the generic phrasing and the per-service synonyms a user would naturally say. Matches the 5 anchor for comprehensive natural-term coverage including synonyms; no common variation is conspicuously missing.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear Azure-to-AWS niche with distinct triggers and explicitly excludes adjacent confusable cases ('Do not use for GCP or Heroku migrations, reverse migrations, general AWS architecture, or Azure-to-Azure refactoring'). Minimal conflict risk — matches the 5 anchor; a 4 would imply overlap with closely related skills, which the exclusions pre-empt.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (references/shared/extract-), 10 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

aws/agent-toolkit-for-aws

Path

plugins/aws-startup-advisor/skills/azure-to-aws/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.