Name: migrate-v8-to-v9
Rating: 75.2 (1 reviews)
Author: TanStack

migrate-v8-to-v9

Perform a complete @tanstack/react-table v8-to-v9 migration: hook and feature architecture, row-model slots, React state and subscriptions, rendering, composable tables, type helpers, and every shared API rename and semantic change. Use for migration plans, implementation, or audits. Treat useLegacyTable only as a deprecated temporary bridge.

Quality

94%

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

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 exhaustive, highly actionable migration reference with a clear sequenced workflow, validation checkpoints, and error-recovery guidance. The only structural weakness is that a large mapping reference lives entirely inline in SKILL.md rather than being split into one-level-deep reference files.

Suggestions

Move the large 'Complete breaking-change map' tables (construction/state/rendering/types/shared-API) into a reference file such as references/breaking-changes.md, keeping a concise summary and a clearly signaled link in SKILL.md.

Add a short 'Quick start' or minimal-migration snippet near the top so the most common small migration is reachable before the exhaustive mapping tables.

Consider extracting the 'Final migration checklist' into a separate references/migration-checklist.md so it can be referenced independently during review.

Dimension	Reasoning	Score
Conciseness	Dense reference content with no concept over-explanation (no 'what is React Table' padding); every table row and code block carries concrete v8→v9 information and assumes Claude's competence.	5 / 5
Actionability	Provides executable TSX (target architecture, controlled state, selector/FlexRender usage), exact API rename mappings, and concrete file paths to inspect — copy-paste ready and specific across common cases.	5 / 5
Workflow Clarity	A 10-step sequenced migration procedure with explicit validation (step 9: type-check then exercise every feature flow), a final completion checklist, and a 'Common migration failures' section supplying error-recovery feedback.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and clearly signaled peer-skill references ('Read @tanstack/table-core#migrate-v8-to-v9, getting-started, and table-state'), but the large breaking-change tables are inlined in a single ~200-line file that could offload detail to reference files.	4 / 5
	Total	19 / 20 Passed

Description

92%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 explicitly covers both what the skill does and when to use it, with a well-scoped, low-conflict trigger niche. Only minor synonym coverage is missing from the trigger terms.

Dimension	Reasoning	Score
Specificity	Enumerates concrete migration scope areas — 'hook and feature architecture, row-model slots, React state and subscriptions, rendering, composable tables, type helpers, and every shared API rename and semantic change' — with comprehensive, non-vague coverage rather than abstract language.	5 / 5
Completeness	Clearly states what ('Perform a complete @tanstack/react-table v8-to-v9 migration: ...') and an explicit when ('Use for migration plans, implementation, or audits.'), satisfying both halves with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords ('v8-to-v9 migration', '@tanstack/react-table', 'migration plans, implementation, or audits') but missing common synonyms like 'upgrade'/'update'; good but not exhaustive coverage.	4 / 5
Distinctiveness Conflict Risk	The '@tanstack/react-table v8-to-v9 migration' niche is highly specific with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 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
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: TanStack/table
Path: packages/react-table/skills/migrate-v8-to-v9/SKILL.md
Commit: 9e523bc

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.