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

migrate-v8-to-v9

Complete Angular v8-to-v9 migration reference: injectTable and injection context, explicit features and row-model slots, signal/atom state, FlexRender directives, type generics, prototype methods, sorting, sizing, selection, and logical pinning.

Quality

72%

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/angular-table/skills/migrate-v8-to-v9/SKILL.md

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 a high-quality, actionable migration reference with an explicit ordered workflow, failure catalog, and final verification checklist. Its main weakness is that the exhaustive rename tables are inlined monolithically with no external reference files to offload the bulk.

Suggestions

Move the large v8-to-v9 rename tables (logical pinning, row-model mapping) into a reference file and link to it from SKILL.md to reduce inline bulk.

Add a brief 'Validate' checkpoint in the migration order referencing the Final Checklist rather than leaving verification only at the end.

Consider an API Discovery snippet showing the exact node_modules types path command to make that step executable.

Dimension	Reasoning	Score
Conciseness	The body is dense but nearly every line is actionable migration detail; it assumes Angular/TanStack competence and avoids explaining what the library is. It is slightly above the midpoint but the long inline method-renaming tables are reference bulk that could be trimmed or split out.	4 / 5
Actionability	Provides copy-paste-ready code for the central injectTable/tableFeatures pattern plus exhaustive concrete v8-to-v9 rename tables and explicit failure cases, giving executable guidance across the common cases.	5 / 5
Workflow Clarity	A numbered 'Recommended Migration Order' is followed by a 'Common Migration Failures' section with severity tags and a 'Final Checklist' that serves as explicit validation; this is a clear sequenced workflow with checkpoints and a verification list.	5 / 5
Progressive Disclosure	Well-organized into clear sections with a logical overview-to-detail progression, but no bundle files exist and the large rename tables/API lists are inlined rather than split into reference files, leaving minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

58%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 distinctive within a narrow migration niche, but it omits any explicit 'Use when...' trigger guidance and leans on dense technical enumeration over natural user phrasing. Adding a trigger clause and lighter wording would lift the completeness and trigger scores.

Suggestions

Append an explicit trigger clause, e.g. 'Use when upgrading a TanStack Angular Table project from v8 to v9.'

Soften the dense feature enumeration into a few concrete actions so the description reads as discrete capabilities rather than a keyword list.

Add natural synonyms users might say ('upgrade', 'TanStack Angular Table') alongside the version-specific jargon.

Dimension	Reasoning	Score
Specificity	Lists several concrete migration areas ('injectTable and injection context', 'explicit features and row-model slots', 'signal/atom state', 'FlexRender directives', 'type generics', 'prototype methods', 'sorting, sizing, selection, and logical pinning') but is a dense enumeration rather than crisp discrete actions, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clearly stated as a complete migration reference, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric this caps completeness at 3.	3 / 5
Trigger Term Quality	Includes version-specific trigger tokens ('Angular v8-to-v9 migration', 'FlexRender', 'injectTable') that a developer needing this skill would say, but lacks common synonyms or natural phrasings like 'upgrade TanStack Angular Table' and is jargon-heavy rather than user-natural.	3 / 5
Distinctiveness Conflict Risk	The highly specific v8-to-v9 / @tanstack/angular-table niche with explicit version pinning is unlikely to trigger for any other skill; conflict risk is minimal.	5 / 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/angular-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.