CtrlK
BlogDocsLog inGet started
Tessl Logo

mpg-migration-pr-review

Review Azure SDK management-plane migration PRs (Swagger/AutoRest -> TypeSpec). Checks customization quality, TypeSpec decorator usage, and migration-specific anti-patterns on top of the standard mgmt PR review.

74

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

100%

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

The body is a lean, highly actionable migration-PR review checklist with clear sequencing, an explicit re-review feedback loop, and well-organized sections, all carrying domain knowledge Claude would not already have.

DimensionReasoningScore

Conciseness

Dense, instruction-only content with no explanation of concepts Claude already knows (no primer on TypeSpec/AutoRest/Swagger); every line is substantive review guidance that earns its token place.

3 / 3

Actionability

Highly actionable for an instruction-only skill: exact rule IDs (4.1-4.11), exact attributes and decorators ([CodeGenMember("GeneratedName")], @@clientName(..., "csharp")), and concrete bad/good example pairs per rule.

3 / 3

Workflow Clarity

Clear numbered sequence (base Phases 1-3 first, then migration Phases 4-6) with an explicit re-review feedback loop in Phase 5 ("On re-review, inspect every newly added rename customization...") and required final counts in the output format.

3 / 3

Progressive Disclosure

Self-contained review checklist well-organized into clear sections (phases, numbered rules, triage table, output format) with no need for external bundle references; no nested/deep reference chains.

3 / 3

Total

12

/

12

Passed

Description

82%

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 specific, distinct, and uses natural domain terms, but it omits an explicit 'Use when...' trigger clause, leaving the activation condition implied rather than stated.

Suggestions

Add an explicit 'Use when...' clause, e.g. "Use when reviewing Azure SDK management-plane migration PRs from Swagger/AutoRest to TypeSpec (titles like 'Migrate to TypeSpec' or 'MPG migration', or PRs adding tsp-location.yaml / removing autorest.md)."

Surface concrete file/shape triggers (tsp-location.yaml, deleted autorest.md, regenerated src/Generated/) into the description so users can identify eligible PRs without reading the body.

DimensionReasoningScore

Specificity

Lists multiple concrete review actions: "Checks customization quality, TypeSpec decorator usage, and migration-specific anti-patterns" on top of reviewing migration PRs, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly states what the skill does, but lacks any "Use when..." clause or explicit trigger guidance in the description itself, so the "when" is only implied; per guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Natural niche terms an Azure SDK contributor would say are present — "migration PRs", "Swagger/AutoRest -> TypeSpec", "management-plane", "mgmt PR review" — giving good coverage rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

A narrow, well-defined niche — Azure .NET management SDK Swagger/AutoRest-to-TypeSpec migration PRs — with distinct triggers unlikely to overlap with other skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.