tanstack-router-migration

Migrate React applications from React Router to TanStack Router with file-based routing. Use when user requests: (1) Router migration, (2) TanStack Router setup, (3) File-based routing implementation, (4) React Router replacement, (5) Type-safe routing, or mentions 'migrate router', 'tanstack router', 'file-based routes'.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The content is a strong, actionable migration guide with excellent progressive disclosure and a clear phased workflow. Its main weakness is conciseness, driven by duplicated definitions and repeated guidance that could be consolidated.

Suggestions

Consolidate the RouterContext type definition so it appears once (Phase 4's __root.tsx) and is referenced rather than redefined in Phase 3.

Merge the trailing-slash-in-from guidance: keep it in one place (e.g. Common Pitfalls) and link from the Quick Reference instead of restating it.

Add an explicit verify checkpoint after Phase 5 (e.g. "run the app and exercise migrated routes; fix and re-run before moving to Integrations") to create a validation feedback loop between phases.

Dimension	Reasoning	Score
Conciseness	The body is dominated by useful, executable code rather than concept explanation, but it carries noticeable redundancy: RouterContext is defined in both Phase 3 and Phase 4, trailing-slash guidance appears in both the Quick Reference and Common Pitfall #8, and Zod search patterns are repeated. This fits "mostly efficient but could be tightened."	3 / 5
Actionability	Provides abundant copy-paste-ready code and commands (build plugin configs, createRouter setup, file-based route structure, hook before/after migration, Zod validation, test utilities, Sentry/nuqs integrations) covering the common migration cases, matching the fully-executable top anchor.	5 / 5
Workflow Clarity	A clear seven-phase sequence (Assessment through Integrations) is paired with per-phase checklists that act as verification gates. It stops short of the top anchor because there is no explicit run-the-app / run-tests feedback loop between migration phases to catch regressions early.	4 / 5
Progressive Disclosure	Detailed material is offloaded to one-level-deep, well-signaled references (build-configuration.md, route-templates.md, migration-patterns.md, incremental-migration.md), all of which exist in ./references/, while core guidance stays inline — matching the clear-overview top anchor.	5 / 5
	Total	17 / 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.

The description is well-constructed: it states a clear purpose and provides explicit, natural trigger guidance with synonyms. Its only mild weakness is specificity, since it frames the skill around a single migrate action rather than enumerating multiple discrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the precise domain and one concrete action ("Migrate React applications from React Router to TanStack Router with file-based routing"), but does not enumerate several distinct capabilities, matching the anchor for naming a domain with 1-2 concrete actions.	3 / 5
Completeness	Clearly states what the skill does and follows with an explicit "Use when user requests: (1)...(5)..., or mentions '...'" clause containing concrete trigger phrases, exactly matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("migrate router", "tanstack router", "file-based routes") plus synonyms ("React Router replacement", "Router migration"). Coverage is strong but not fully comprehensive enough for the top anchor, which emphasizes exhaustive synonyms/extensions.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow, specific niche (React Router to TanStack Router migration) with distinct trigger terms, giving it minimal overlap or conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (597 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	14 / 16 Passed

Repository: redpanda-data/console
Path: frontend/.claude/skills/tanstack-router-migration/SKILL.md
Commit: 60125ec

Reviewed: 1 day 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.