CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-v8-to-v9

Migrate react Table v8 to v9. Audit framework construction, rendering, state, and app hooks, with shared API changes in the core migration skill.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/react-table/skills/migrate-v8-to-v9/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 an exemplar of lean, checklist-driven migration guidance with well-structured conditional references and a dedicated verification section. The only gaps are the absence of in-file code examples and an explicit error-recovery loop in the verification workflow.

DimensionReasoningScore

Conciseness

The ~30-line body is a lean directive checklist with zero padding: no React or library concept explanations, and every item ("Replace `useReactTable` with `useTable`", "Remove the global `onStateChange` option") adds non-obvious information.

5 / 5

Actionability

Concrete commands ("run `intent load @tanstack/table-core#migrate-v8-to-v9`", "Inspect `node_modules/@tanstack/react-table/dist/index.d.ts`") and exact API names (`table.Subscribe`, `useSelector`, `table.FlexRender`) make the guidance mostly executable, but no copy-paste code examples appear in SKILL.md itself — code details are deferred to references.

4 / 5

Workflow Clarity

A clear sequence runs prerequisite check → load core checklist → audit → read details conditionally → verify, with an explicit "Verify the migration" section and checklists. However, there is no error-recovery feedback loop stating what to do when type-checking or feature-flow verification fails.

4 / 5

Progressive Disclosure

A clear overview checklist with well-signaled, condition-based references: "read [adapter migration details](references/adapter-migration.md) before editing it" (verified to exist, one level deep) plus clearly motivated sibling-skill pointers; bulk detail is appropriately split out.

5 / 5

Total

18

/

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, action-oriented, and clearly delineated from the core migration skill, but it lacks any explicit "when to use" trigger guidance and misses a few natural synonyms ("TanStack Table", "upgrade"). Adding a trigger clause would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when migrating or upgrading a React app from TanStack Table v8 to v9."

Include common user synonyms such as "TanStack Table", "react-table", and "upgrade" alongside "react Table v8 to v9".

Optionally mention the verification step (type-checking against the installed v9 adapter) to round out coverage of what the skill does.

DimensionReasoningScore

Specificity

"Migrate react Table v8 to v9. Audit framework construction, rendering, state, and app hooks" names several concrete actions (migrate, audit construction/rendering/state/app hooks) with minor coverage gaps (e.g., verification steps and specific API renames are not mentioned).

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Migrate", "react Table", "v8 to v9" are the natural phrases a user would say, but common synonyms like "TanStack Table", "react-table", or "upgrade" are missing.

4 / 5

Distinctiveness Conflict Risk

A highly specific niche (React Table v8-to-v9 migration) with "with shared API changes in the core migration skill" explicitly delineating its boundary from the core migration skill; minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

TanStack/table

Path

packages/react-table/skills/migrate-v8-to-v9/SKILL.md

Reviewed

Table of Contents

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.