CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-v8-to-v9

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

Quality

76%

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/vue-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-style migration guidance: correct sequencing, exact API mappings, conditional deep-dive references, and a real verification section. Its only soft spots are a couple of abstract directives and implicit rather than explicit failure-handling loops in the verify step.

DimensionReasoningScore

Conciseness

The ~33-line body is pure directive checklist with zero concept explanation and every line earning its place (e.g. "Replace `getState()` with tracked atom reads or intentional whole-store reads"). The only repetition ("complete the shared core checklist" vs "Complete the core checklist") functions as a verification echo, not padding.

5 / 5

Actionability

Concrete commands ("intent load @tanstack/table-core#migrate-v8-to-v9"), exact symbol mappings (useVueTable→useTable, table.Subscribe→reactive reads), and exact .d.ts inspection paths make the guidance executable. A few directives remain abstract ("configure explicit features/row-model slots"), keeping it below the fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The sequence is clear: load core skill → audit adapter checklist → read references for affected areas → verify. A dedicated verification section with type-checking and feature-flow exercise provides checkpoints. Feedback loops on failure are implicit rather than spelled out (no "if type-check fails, fix and re-run"), matching anchor 4.

4 / 5

Progressive Disclosure

The SKILL.md is a lean overview checklist with a well-signaled, condition-gated one-level-deep reference (references/adapter-migration.md, verified present, 51 lines) and scoped cross-links to sibling skills for adjacent topics (getting-started, table-state). Content is appropriately split and navigation is easy.

5 / 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 specific and distinct, correctly scoping Vue-only changes against the shared core skill, but it omits any explicit "when to use" trigger guidance and misses the most natural user keywords (TanStack, upgrade). Adding a Use-when clause with those terms would lift both completeness and trigger quality.

Suggestions

Append a trigger clause such as "Use when upgrading or migrating @tanstack/vue-table (TanStack Table for Vue) from v8 to v9" to satisfy the missing 'when' half of completeness.

Include natural synonyms users would say — "TanStack", "@tanstack/vue-table", "upgrade" — not just "vue Table v8 to v9".

State the shared/core vs Vue-specific split as an explicit action (e.g. "Applies core API changes, then audits Vue adapter construction, rendering, state, and app hooks") so the what-coverage is comprehensive.

DimensionReasoningScore

Specificity

"Audit framework construction, rendering, state, and app hooks" lists several concrete action areas, and "shared API changes in the core migration skill" explicitly delegates the rest. It falls short of anchor 5 because the action vocabulary is limited to migrate/audit without finer-grained capabilities.

4 / 5

Completeness

The description clearly states what it does (migrate v8 to v9, audit construction/rendering/state/app hooks) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Migrate vue Table v8 to v9" covers the core trigger words, but common variations users would actually say are missing: TanStack, @tanstack/vue-table, upgrade. This matches the anchor for some relevant keywords with missing synonyms rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

"Migrate vue Table v8 to v9" carves a clear niche (Vue adapter migration) and explicitly defers shared API changes to the core skill, minimizing overlap. Minor overlap risk remains with the core migration skill and sibling framework adapters, matching anchor 4 rather than the fully distinct anchor 5.

4 / 5

Total

14

/

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