Name: migrate-v8-to-v9
Rating: 63.2 (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

76%

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

77%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 body is a well-structured, actionable migration inventory with a clear validated workflow and feedback loops. Its weakest area is progressive disclosure: everything is inlined in one file with no references to supporting bundle files.

Suggestions

Move the large twelve-section breaking-change inventory into a separate reference file (e.g. references/breaking-changes.md) and link to it one level deep from SKILL.md, keeping the strategy, minimal shape, and checklist inline.

Tighten the aggregation section (lines 126-142) into a compact table or bullet list to reduce prose verbosity.

Add the installed-package discovery commands as concrete executable shell snippets rather than only prose steps.

Dimension	Reasoning	Score
Conciseness	Dense mapping tables and copy-paste code assume Claude's library knowledge with no basic-concept padding, but the aggregation prose (lines 126-142) and a few repeated caveats could be trimmed further.	4 / 5
Actionability	Concrete v8-to-v9 rename tables plus executable code blocks (minimal shape, bound methods, indeterminate selection, metaHelper) give mostly executable guidance, with minor gaps where it deliberately defers to the adapter skill.	4 / 5
Workflow Clarity	A six-step migration strategy with explicit validation checkpoints (tests-before, type-check, per-stage testing), common-failure feedback loops, and a complete audit checklist clearly sequence the process.	5 / 5
Progressive Disclosure	No bundle files exist and there are no file references; the twelve-section breaking-change inventory is inlined in SKILL.md rather than split into a one-level-deep reference, despite good internal section headers.	3 / 5
	Total	16 / 20 Passed

Description

75%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 specific and highly distinct, clearly scoping a v8-to-v9 TanStack Table migration audit. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when migrating TanStack Table / React Table code from v8 to v9 or upgrading across the v9 breaking changes.'

Include a couple of natural synonyms ('upgrade', 'React Table') alongside the technical enumeration to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and enumerates eleven specific migration areas (feature registration, row-model slots, prototype methods, pinning/resizing renames, meta typing, generics), giving comprehensive concrete coverage.	5 / 5
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause; 'Load this shared inventory before the installed framework adapter's migration skill' is sequencing guidance rather than a trigger, so completeness is capped at 3.	3 / 5
Trigger Term Quality	'TanStack Table v8-to-v9 migration audit' is a strong natural trigger phrase, but the bulk of the description is technical jargon and it misses synonyms like 'upgrade' or 'React Table'.	4 / 5
Distinctiveness Conflict Risk	The v8-to-v9 TanStack Table migration niche is highly specific with distinct triggers and minimal overlap 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
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: d01c01b

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.