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

migrate-v8-to-v9

Perform a complete TanStack Table v8-to-v9 migration audit: feature registration, row-model and function-registry slots, state/store changes, prototype methods, column pinning and resizing renames, sorting and selection semantics, removed internals, helpers, meta typing, and generic changes. Load this shared inventory before the installed framework adapter's migration skill.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/table-core/skills/migrate-v8-to-v9/SKILL.md

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 highly actionable and well-sequenced with concrete mappings and validation checkpoints, achieving strong actionability and workflow clarity. Its weaker dimension is progressive disclosure: the entire inventory is a single long inlined document with no reference files to offload the dense mapping tables.

Suggestions

Move the large rename/mapping tables (pinning, sorting, row-models) into a references/ file and keep only the highest-value example inline, reducing SKILL.md length and improving progressive disclosure.

Convert several 'Test ...' checklist items into explicit validate-fix-retry feedback loops for batch/destructive migration steps to lift workflow_clarity to 5.

Tighten the aggregation section (section 2) into table form like the other rename sections to remove the verbose prose passage.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely assumes Claude's competence—tables of renames and short imperative rules instead of concept lectures—with only minor passages (e.g., the multi-paragraph aggregation section) that could be tightened.	4 / 5
Actionability	It provides executable code blocks, exact rename mappings, concrete feature-registration tables, and specific commands like inspecting 'node_modules/@tanstack/table-core/dist/index.d.ts', covering the common migration cases copy-paste ready.	5 / 5
Workflow Clarity	A clear six-step migration strategy precedes a complete audit checklist with validation checkpoints ('Test every enabled client/server row-model stage', type-check without casts, test LTR/RTL); a few checkpoints are checks rather than explicit validate-fix-retry loops.	4 / 5
Progressive Disclosure	No bundle files exist, so all material is inlined in one ~330-line SKILL.md; sectioning is good, but the large rename/mapping tables that could live in reference files are kept inline, and external pointers (adapter skills, installed dist files) are referenced but not organized as one-level-deep bundle references.	3 / 5
	Total	16 / 20 Passed

Description

63%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 highly specific and distinct, enumerating a thorough set of v8-to-v9 migration actions. Its main weakness is the absence of an explicit 'Use when...' trigger clause and limited natural-language synonyms, which cap completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause such as 'Use when migrating a TanStack Table codebase from v8 to v9 or when the user mentions a table-core v9 upgrade, react-table v9, or v8-to-v9 migration.'

Broaden trigger-term coverage with natural synonyms users say ('tanstack', 'react-table', 'v9 upgrade', 'table-core') rather than only technical slot names.

Make the 'when' guidance explicit (during migration/upgrade work) instead of only the load-order hint 'Load this shared inventory before...'.

Dimension	Reasoning	Score
Specificity	Lists numerous concrete migration actions—'feature registration, row-model and function-registry slots, state/store changes, prototype methods, column pinning and resizing renames, sorting and selection semantics, removed internals, helpers, meta typing, and generic changes'—giving comprehensive coverage of the capability surface.	5 / 5
Completeness	It clearly states what the skill does (a complete migration audit inventory), but the 'when' is only weakly implied via 'Load this shared inventory before the installed framework adapter's migration skill'—there is no explicit 'Use when...' clause guiding when Claude should invoke it.	3 / 5
Trigger Term Quality	It uses the natural phrase 'TanStack Table v8-to-v9 migration' and 'migration audit', but it omits common synonyms or shorthand a user might say (e.g. 'tanstack', 'react-table', 'v9 upgrade', 'table-core') and repeats technical slots rather than expanding trigger vocabulary.	3 / 5
Distinctiveness Conflict Risk	The TanStack Table v8-to-v9 scope is a clear niche with distinct triggers and minimal conflict risk; minor overlap could occur with sibling per-adapter migration skills it explicitly defers to.	4 / 5
	Total	15 / 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/table-core/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.