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.

72

Quality

89%

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

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

An excellent, dense workflow document with executable commands, explicit validation checkpoints, and feedback loops for a fragile migration process. Its only weakness is that sizable reference tables are kept inline rather than factored into separate reference files.

DimensionReasoningScore

Conciseness

The body is lean and information-dense, assuming Claude's competence throughout — it never explains what AutoRest, TypeSpec, ApiCompat, or decorators are, and every line conveys domain-specific actionable knowledge Claude would not already know, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It provides fully executable, copy-paste-ready commands (e.g. 'pwsh eng/packages/http-client-csharp-mgmt/eng/scripts/RegenSdkLocal.ps1 -Services "Azure.ResourceManager.<Service>" -LocalSpecRepoPath <path> -SaveInputs') and precise decorator syntax ('@@alternateType(Model.prop, targetType, "csharp")'), with placeholders representing justified parameterization rather than pseudocode.

5 / 5

Workflow Clarity

The multi-step process (Setup → Resource Hierarchy Gate → Build-Fix Loop → Breaking Changes → Generator Bugs → Finalize → Done When) is clearly sequenced with explicit validation checkpoints (hierarchy-gate exit codes 0/1/2, ApiCompat-clean verification) and feedback loops ('build → classify → fix → regenerate if needed → rebuild'), plus a terminal 'Done When' checklist.

5 / 5

Progressive Disclosure

The file is well-organized into clearly labeled sections with no nested references and no bundle files present; it stops short of 5 only because several large reference tables (decorator fixes, SDK fix patterns, new-API triage) are inlined rather than split into one-level-deep reference files, leaving minor organization gaps.

4 / 5

Total

19

/

20

Passed

Description

82%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, third-person description that clearly states what the skill does and when to use it with concrete, niche-specific trigger terms. The only minor gap is that it names a single action rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action ('Handles Azure SDK for .NET management-plane migrations from AutoRest/Swagger to TypeSpec'), but lists only a single action rather than multiple specific actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the comprehensive 5.

3 / 5

Completeness

It explicitly answers both 'what' ('Handles Azure SDK for .NET management-plane migrations from AutoRest/Swagger to TypeSpec') and 'when' ('use for MPG, mgmt migration, or Azure.ResourceManager.* migration requests') with concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

It provides good natural trigger coverage with 'MPG, mgmt migration, or Azure.ResourceManager.* migration requests' — terms a user would actually say — though it stops short of the fully comprehensive synonym/extension coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Azure SDK .NET management-plane AutoRest/Swagger→TypeSpec migration) with distinct triggers and minimal overlap risk with other skills, matching the 5 anchor.

5 / 5

Total

17

/

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.

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.