antd-migration

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./public/.well-known/agent-skills/antd-migration/SKILL.md

Quality

Content

80%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 tight, well-structured migration guide that is token-efficient and points to authoritative external references. Its main weakness is the absence of a validation/verification step for a batch migration operation.

Suggestions

Add an explicit validation checkpoint after running the codemod — e.g. 'Run tests/build and confirm no deprecated API warnings before committing' — to lift workflow_clarity above 3.

Include a short, copy-pasteable example (e.g. the npx codemod command and a ConfigProvider theme-token snippet) to move actionability from 4 toward 5.

Show how to verify a specific component migration (e.g. confirm BackTop usages now reference FloatButton.BackTop) as a concrete verification step.

Dimension	Reasoning	Score
Conciseness	Lean and efficient body that assumes Claude's competence — short sections, only the non-obvious facts (Less dropped for CSS-in-JS, class-name prefix changes), and every token earns its place. It is not below 5 because there is no padding or over-explanation of concepts Claude already knows.	5 / 5
Actionability	Provides concrete specifics — the `@ant-design/codemod-v5` tool, exact component mappings (BackTop -> FloatButton.BackTop), and URLs to fetch the full change list. It is not 5 because there is no copy-paste-ready code example covering common migration cases.	4 / 5
Workflow Clarity	Steps are sequenced (review guide -> apply key steps -> use codemod -> fetch full list) but migration is a batch operation with no validation/verification checkpoint to confirm the migration succeeded, which caps this dimension at 3 per the destructive/batch feedback-loop guideline. It is not 4 because an explicit validation step is absent.	3 / 5
Progressive Disclosure	Well-organized sections (When to Use, Instructions, Notes) with clearly signaled one-level references to the official migration docs and llms-full.txt. As a short, single-purpose skill under 50 lines with no need for local bundle files, this qualifies for the simple-skill score of 5.	5 / 5
	Total	17 / 20 Passed

Description

73%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 concise, well-targeted description that explicitly states both what the skill does and when to use it, with strong distinctiveness. The main gap is action specificity and broader trigger-term coverage.

Suggestions

Add a few more concrete migration actions to the description (e.g. 'replace Less theme customization with ConfigProvider tokens') to lift specificity from 3 toward 5.

Broaden trigger terms with synonyms users naturally say, such as 'Ant Design upgrade', 'migrate antd', or 'antd v5 migration'.

Consider adding file/version synonyms (e.g. '.antd', 'antd 5') to strengthen trigger-term completeness.

Dimension	Reasoning	Score
Specificity	Names the domain ('Migrate between Ant Design major versions') and 1-2 concrete actions ('upgrading from antd v4 to v5', 'addressing breaking changes in component APIs') but the action list is not comprehensive. It does not reach 4 because it lists fewer than several specific concrete actions.	3 / 5
Completeness	Clearly answers 'what' ('Migrate between Ant Design major versions') and 'when' ('Use when upgrading from antd v4 to v5 or addressing breaking changes'). It is not 5 because the trigger phrases, while explicit, could be more comprehensive with additional synonyms.	4 / 5
Trigger Term Quality	Includes relevant natural keywords users would say — 'antd v4 to v5', 'Ant Design', 'upgrading', 'breaking changes' — with good coverage. It is not 5 because some common phrasings and synonyms (e.g. 'Ant Design upgrade', 'migrate antd') are not all present.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Ant Design major-version migration with v4-to-v5 specifics — with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: df3386b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.