CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-v8-to-v9

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

Quality

77%

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

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 body is a lean, well-structured migration checklist with concrete symbol-level guidance, a clear core-first workflow, and exemplary conditional reference signaling to a real one-level-deep bundle file. It falls just short of top marks on actionability and workflow clarity only because before/after code and error-recovery loops live in the reference rather than the body, which is an appropriate trade for this skill's size.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and directive with no padding or explanation of known concepts; the only trimmable instance is the enumeration of the core skill's scope ('It owns feature registration, row-model slots, ... TypeScript mappings'), which duplicates what loading that skill reveals. Fits 'efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

Gives symbol-level concrete guidance ('Replace `createAngularTable` with `injectTable`', 'Hoist features, columns, and factories outside the signal-tracked initializer'), an executable command (`intent load @tanstack/table-core#migrate-v8-to-v9`), and node_modules paths to inspect. Minor gaps: no before/after code in the body (deferred to the reference file), keeping it at 'mostly executable guidance' rather than fully copy-paste ready.

4 / 5

Workflow Clarity

Clear sequence (load core skill first, prerequisites, adapter checklist, apply affected mappings, then 'Final checks' validation checklist) with most checkpoints present. Not 5 because there is no explicit fix-and-retry feedback loop for failed checks; not 3 because validation checkpoints exist as the final-checks checklist and per-item checklists.

4 / 5

Progressive Disclosure

The body is a concise overview with a well-signaled, conditionally-triggered, one-level-deep reference ('Read [adapter-migration](references/adapter-migration.md) when changing construction, rendering, state, or app hooks' — verified to exist in the bundle), plus clearly labeled cross-skill pointers for getting-started and table-state. Content is appropriately split and easy to navigate.

5 / 5

Total

17

/

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 and distinctive, with a clear niche and concrete audit areas, but it lacks any 'when to use' trigger guidance, capping completeness at 3. Adding an explicit 'Use when...' clause with natural synonyms (TanStack, upgrade, @tanstack/angular-table) would raise both completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when migrating or upgrading @tanstack/angular-table (TanStack Table for Angular) from v8 to v9.'

Include natural synonyms users would say: 'TanStack', 'upgrade', and the package name '@tanstack/angular-table'.

Briefly mention the TypeScript/API rename coverage in the 'what' portion to round out capability coverage without adding fluff.

DimensionReasoningScore

Specificity

Names the domain ('Migrate angular Table v8 to v9') and lists several concrete audit areas ('framework construction, rendering, state, and app hooks'), matching 'lists several specific actions; minor gaps in coverage'. Not 5 because comprehensive coverage is delegated to the core migration skill rather than enumerated; not 3 because it goes beyond 1-2 generic actions with named subsystems.

4 / 5

Completeness

Has a clear 'what' (migrate v8 to v9; audit construction, rendering, state, app hooks) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural phrases users would say ('Migrate', 'angular Table', 'v8 to v9', 'app hooks') but misses common synonyms like 'TanStack', 'upgrade', and the package name '@tanstack/angular-table', fitting 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

'angular Table v8 to v9' is a clear niche with distinct triggers, and explicitly noting 'shared API changes in the core migration skill' delineates the boundary from the companion core skill, minimizing conflict risk.

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/angular-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.