CtrlK
BlogDocsLog inGet started
Tessl Logo

mpg-migration

Handles Azure SDK for .NET management-plane migrations from AutoRest/Swagger to TypeSpec; use for MPG, mgmt migration, or Azure.ResourceManager.* migration requests.

73

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

92%

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

An excellent, dense procedural skill with concrete commands, explicit validation checkpoints, and a clear phased workflow. The main gap is progressive disclosure: a large single file with inline reference tables that could be offloaded to separate files.

Suggestions

Extract the decorator-fix and SDK-side fix-pattern tables into a reference file (e.g. references/fix-patterns.md) and link to it from the Build-Fix Loop section to reduce inline reference bulk.

Move the Resource Hierarchy Gate script invocation details into a referenced snippet so the main SKILL.md body stays a concise overview of the workflow phases.

Consider splitting the per-phase command examples (RegenSdkLocal.ps1, Export-API.ps1) into a scripts/ or references/ file, keeping only the key invocation in SKILL.md.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (no explaining what AutoRest, TypeSpec, or ApiCompat are); every line is actionable guidance with no padded concept explanations.

3 / 3

Actionability

Provides fully executable pwsh commands, exact decorator syntax (e.g. '@@alternateType(Model.prop, targetType, "csharp")'), and copy-paste-ready tables mapping problems to specific fixes.

3 / 3

Workflow Clarity

Clear phased sequence (Setup -> Resource Hierarchy Gate -> Build-Fix Loop -> Finalize -> Done When) with explicit validation checkpoints (exit codes 0/1/2, zero Swagger diff check) and a build/classify/fix feedback loop; not below because checkpoints are explicit, not implicit.

3 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a single >50-line file with no bundle files and substantial inline reference material (decorator and SDK fix-pattern tables) that could be split into separate referenced files; not 3 because content that could be separate is inline, and not 1 because sections are clearly signaled rather than a monolithic wall.

2 / 3

Total

11

/

12

Passed

Description

90%

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 tight, third-person description that clearly states both what it does and when to use it, with distinctive domain-specific triggers. Its only weakness is that it names a single migration action rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ('migrations from AutoRest/Swagger to TypeSpec') but lists only one action rather than multiple specific concrete actions, so it sits at anchor 2 rather than 3.

2 / 3

Completeness

Explicitly states what it does ('Handles Azure SDK for .NET management-plane migrations...') and when to use it ('use for MPG, mgmt migration...'), with an explicit trigger clause; not below because neither what nor when is missing.

3 / 3

Trigger Term Quality

'MPG, mgmt migration, or Azure.ResourceManager.* migration requests' are natural terms an Azure SDK engineer would actually say, giving good coverage; not the level below because it is not generic jargon.

3 / 3

Distinctiveness Conflict Risk

The niche is highly specific (Azure .NET management-plane, Azure.ResourceManager.*) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
Azure/azure-sdk-for-net
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.