CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antd-migration

Migrate between Ant Design major versions. Use when upgrading from antd v4 to v5 or addressing breaking changes in component APIs.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 concise, well-organized single-purpose migration guide with genuinely actionable component mappings and tooling pointers. Its main gaps are the absence of any validation/verification step in the migration workflow and the lack of a copy-paste-ready codemod command.

Suggestions

Add a validation step after running the codemod, e.g., "Run build/tests; if component errors appear, check the migration guide for that component and re-run the codemod" — this addresses the workflow_clarity cap.

Include the exact command for the automated tool (e.g., `npx @ant-design/codemod-v5 src/`) instead of just naming it, making the guidance copy-paste ready for actionability.

Merge the Notes section into the Instructions where it duplicates them (Less/CSS-in-JS, deprecated APIs) to remove redundancy and tighten conciseness.

DimensionReasoningScore

Conciseness

The body is lean with no padding of concepts Claude already knows, but the Notes section partially repeats the Instructions (Less/CSS-in-JS and deprecated-API points), which could be trimmed for a fully token-efficient 5.

4 / 5

Actionability

Concrete mappings ("BackTop → FloatButton.BackTop", "Comment → use @ant-design/compatible"), a named tool, and specific URLs make the guidance mostly executable; it falls short of 5 because no exact command for running the codemod is given and "check migration guide for full list" defers key details.

4 / 5

Workflow Clarity

Steps 1-4 are listed in a sensible sequence, but there are no validation checkpoints (e.g., run build/tests after applying the codemod); since a version migration touches many files, the missing feedback loop caps this at 3 rather than 4.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references; the well-organized When to Use / Instructions / Notes sections fully satisfy the simple-skill exception for a top score.

5 / 5

Total

16

/

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 description that explicitly covers what the skill does and when to use it with concrete, version-specific trigger terms. Its only weakness is that the capability statement stays at one generic action rather than enumerating the specific migration sub-tasks.

DimensionReasoningScore

Specificity

"Migrate between Ant Design major versions" names the domain and a single concrete action, but unlike the level-4/5 anchors it does not list several specific sub-actions (e.g., theme token conversion, component replacements).

3 / 5

Completeness

It explicitly answers both parts: "Migrate between Ant Design major versions" (what) and "Use when upgrading from antd v4 to v5 or addressing breaking changes in component APIs" (when, with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

"upgrading from antd v4 to v5" and "breaking changes in component APIs" are natural phrases users would say, with good version-specific keywords; a few common variations (e.g., "Less to CSS-in-JS", "migration") are missing, keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The antd v4-to-v5 migration niche is tightly scoped with version-specific triggers, making conflict with other skills minimal and clearly distinguishable.

5 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ant-design/ant-design

Path

public/.well-known/agent-skills/antd-migration/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.