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

migrate-v8-to-v9

Complete Lit v8-to-v9 migration reference: TableController construction, explicit features and row-model slots, selected/atom state, FlexRender, createTableHook, type generics, prototype methods, sorting, sizing, selection, and logical pinning.

Quality

74%

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/lit-table/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 for a breaking-change migration, with concrete code and exact API mappings plus a verification step, but it is a monolithic single-file reference that underuses progressive disclosure and carries minor version-pin verbosity.

Suggestions

Move the large logical-pinning and row-model mapping tables into a reference file (e.g. references/breaking-changes.md) and link to it one level deep, keeping SKILL.md as an overview.

Relocate time-sensitive version pins (Lit 3.1.3, beta.80, Beta.38 note) into a clearly labeled 'Version / deprecated' section so they do not penalize conciseness.

Add an explicit per-step validation checkpoint in the Recommended Migration Order (e.g. 'after moving row models, verify the table renders before proceeding') to close the workflow validation gap.

Dimension	Reasoning	Score
Conciseness	The body is dense and reference-style with no padding about what Lit/TanStack is, but embeds time-sensitive version pins (Lit 3.1.3, beta.80, Beta.38) outside any 'deprecated/old patterns' section and repeats the controller construction point across table, code, failures, and checklist, leaving minor trimmable instances.	4 / 5
Actionability	It provides a copy-paste-ready TypeScript controller/table() example plus exact v8-to-v9 mapping tables, an explicit feature-import roster, named factory slots, and concrete node_modules file paths to verify, fully covering the common migration cases.	5 / 5
Workflow Clarity	A clear 6-step 'Recommended Migration Order', a 'Common Migration Failures' recovery section, and an 'API Discovery' verification step give a strong sequence with checkpoints, but there is no per-step validate-then-proceed feedback loop, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Section structure is clear, but no bundle files exist and all dense tabular content (the large logical-pinning table, row-model mapping, shared breaking-change map) is inlined in a single ~180-line SKILL.md rather than split into one-level-deep reference files.	3 / 5
	Total	16 / 20 Passed

Description

70%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, distinctive, and rich in relevant trigger terms for a narrow migration domain, but it omits an explicit 'Use when...' trigger clause, which caps its completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when migrating TanStack Lit table code from v8 to v9, or when the user mentions Lit table upgrades, beta.38+, or v9 breaking changes.'

Lead with a verb-led action ('Migrate Lit v8 table code to v9: ...') to convert the topic list into concrete actions and lift specificity toward 5.

Include synonymous trigger terms such as 'TanStack table', 'table-core', 'upgrade', and the package name '@tanstack/lit-table' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete, named migration areas ('TableController construction, explicit features and row-model slots, ... sorting, sizing, selection, and logical pinning'), giving comprehensive topical coverage, but they are noun-phrase topics rather than verb-led actions, sitting just below the verb-action anchor 5.	4 / 5
Completeness	It clearly states the 'what' (a complete v8-to-v9 migration reference with enumerated topics) but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap completeness stays at 3.	3 / 5
Trigger Term Quality	It surfaces strong natural keywords a migrating user would say ('Lit v8-to-v9 migration', 'TableController', 'FlexRender', 'createTableHook', 'sorting', 'pinning'), but misses common synonyms/variants like 'TanStack', 'table-core', 'upgrade', or package names.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific (TanStack Lit table v8-to-v9 migration with named APIs), giving it distinct triggers and minimal risk of firing for an unrelated skill.	5 / 5
	Total	16 / 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/lit-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.