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

migrate-v8-to-v9

Perform a complete @tanstack/solid-table v8-to-v9 migration: createTable, explicit features and row-model slots, getter-based Solid reactivity, atom state, rendering, composable tables, type helpers, and every shared API rename and semantic change. Use for migration plans, implementation, or audits.

Quality

87%

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

82%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 highly actionable, well-structured migration reference with exhaustive rename maps, executable code, and a procedure plus checklist. Weakest on conciseness (procedure/checklist overlap) and on an explicit validation feedback loop, both of which keep those dimensions at 4 rather than 5.

Suggestions

Consolidate the "Migration procedure" and "Final migration checklist" into a single sequenced section to remove the redundancy that lowers conciseness.

Add an explicit validate→fix→retry loop after step 9 (e.g. "If type-check or a flow fails, fix the mapping and re-run before proceeding") to lift workflow_clarity to a 5.

Consider moving the large shared-API rename tables into a references/ file referenced one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and reference-like (rename tables, code, checklists) and assumes Solid/TanStack competence, but the "Migration procedure" and "Final migration checklist" cover substantially overlapping ground, adding redundancy that keeps it just below the lean-every-token-earns-its-place anchor of 5.	4 / 5
Actionability	It provides copy-paste-ready code (createTable, getters, table.Subscribe) plus an exhaustive v8→v9 API rename map and concrete procedure steps, fully covering the common migration cases as the anchor requires.	5 / 5
Workflow Clarity	There is a clear 10-step procedure, a validation checkpoint (step 9: type-check and exercise every flow), a checklist, and a common-failures section, but an explicit validate→fix→re-validate gating loop is only implicit, so it falls short of the anchor-5 example.	4 / 5
Progressive Disclosure	The body is well organized with clear section headers and navigable tables, and no bundle files exist to split further, but it is a single ~195-line monolithic file with no one-level-deep references, so it does not reach the clear-overview-with-external-references anchor of 5.	4 / 5
	Total	17 / 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, specific, third-person description that covers what the skill does and when to use it with concrete triggers and a distinct niche. The only gap is trigger-term breadth: a few natural synonyms (e.g. "upgrade") would round out the keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete migration actions — "createTable, explicit features and row-model slots, getter-based Solid reactivity, atom state, rendering, composable tables, type helpers, and every shared API rename and semantic change" — for comprehensive coverage, matching the anchor for several specific concrete actions rather than the minor-gaps anchor at 4.	5 / 5
Completeness	It explicitly answers both what ("Perform a complete @tanstack/solid-table v8-to-v9 migration: ...") and when ("Use for migration plans, implementation, or audits.") with concrete trigger phrases, matching the explicit-both anchor.	5 / 5
Trigger Term Quality	Natural terms like "v8-to-v9 migration", "migration plans, implementation, or audits" are present and would be said by a user needing this, but synonyms (e.g. "upgrade") and version/file extensions are missing, so it sits just below the comprehensive-coverage anchor of 5.	4 / 5
Distinctiveness Conflict Risk	The trigger is a highly specific library+version migration niche, so it is clearly distinguishable from other skills with minimal risk of firing for the wrong one.	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/solid-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.