CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

getting-started

Create and render Table v9 with the vue adapter. Route reusable createTableHook components, Query and Virtual integration, and framework setup; use table-state for reactive ownership.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 exemplary lean overview: complete executable setup code, dense framework-specific constraints, and well-signaled task-based routing into real reference files. The only structural gap is two sibling-skill cross-references that cannot be verified against the provided bundle.

DimensionReasoningScore

Conciseness

The body is lean with zero tutorial padding: no explanation of what Vue or the library is, just a complete setup SFC, dense non-obvious constraints ("Passing `data.value` captures one array and loses later updates"), and task-based routing. Every token carries skill-specific information, matching the 5 anchor.

5 / 5

Actionability

The setup block is a complete, copy-paste-ready Vue SFC (script setup plus template), and the rest gives exact commands (`intent load @tanstack/table-core#core`) and concrete inspection paths (`node_modules/@tanstack/vue-table/dist/index.d.ts`). This matches "fully executable; copy-paste ready".

5 / 5

Workflow Clarity

This is a single-purpose getting-started skill with an explicit ordered entry point ("Before starting, run `intent load ...`"), then setup, constraints, and task-conditioned routing. No destructive or batch operations are involved, so no validation checkpoint is required, and the simple-skill exception applies.

5 / 5

Progressive Disclosure

The "Load by task" section signals each of the three references/ files with clear task triggers, one level deep, and all resolve to real files. It falls short of 5 because the cross-references `../table-state/SKILL.md` and `../migrate-v8-to-v9/SKILL.md` do not resolve within the provided bundle.

4 / 5

Total

19

/

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 well-bounded for its niche, with good keyword coverage and explicit delegation to sibling skills, but it omits any 'Use when' trigger guidance, capping completeness at 3 and leaving natural invocation phrases (TanStack, vue-table, virtualization) unstated.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or rendering TanStack Table v9 tables in a Vue app, or when wiring Query, Virtual, or createTableHook components."

Include the natural names users actually say — "TanStack Table", "vue-table", "@tanstack/vue-table", "virtualization", "pagination" — alongside the current package-oriented terms.

Replace the generic "framework setup" with a concrete capability (e.g. "set up useTable with reactive data in a Vue component") to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Create and render Table v9 with the vue adapter" and "Route reusable createTableHook components, Query and Virtual integration" list several concrete actions across the skill's scope. It falls short of 5 because "framework setup" is generic and several actions are routing/delegation statements rather than concrete capabilities.

4 / 5

Completeness

The "what" is clear (create/render the Vue table, route components and integrations), but there is no "Use when..." clause or equivalent explicit trigger guidance; the routing sentences describe scope, not invocation conditions. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms include "Table v9", "vue adapter", "createTableHook", "Query", "Virtual", and "table-state". A few natural terms users would say are missing ("TanStack", "vue-table", "@tanstack/vue-table", "virtualization", "pagination"), so it fits "good keyword coverage; a few natural terms missing" rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

"vue adapter" pins a clear niche, and explicit delegation ("use table-state for reactive ownership") draws boundaries against the closest sibling skills, minimizing conflict risk. It clearly matches the 5 anchor rather than 4, where overlap with closely related skills would remain unaddressed.

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/vue-table/skills/getting-started/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.