CtrlK
BlogDocsLog inGet started
Tessl Logo

getting-started

Create a Vue TanStack Table v9 table with useTable, explicit tableFeatures, stable columns/features, reactive ref or computed data, and Vue FlexRender without destructuring reactive snapshots.

69

Quality

85%

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 content is highly actionable and concise, with executable examples and a clear Wrong/Correct mistake checklist. Progressive disclosure is good but lacks the one-level-deep reference-file structure that would raise it further.

Suggestions

Consider extracting the API Discovery details (which .d.ts files to inspect and what to look for) into a short reference file so the main body stays a pure overview.

Add a brief 'Prerequisites' note clarifying that the cited @tanstack/table-core#core and table-features skills must be loaded first, so the sequencing is explicit.

Optionally add a quick verification step (e.g., 'Confirm the table re-renders when data ref changes') to make the creation workflow's checkpoint explicit.

DimensionReasoningScore

Conciseness

The body is lean and technical — complete SFC, a focused feature snippet, and a tight Wrong/Correct mistake format — assuming Claude's competence with no padding about what Vue or tables are.

5 / 5

Actionability

All examples are fully executable: a runnable <script setup> SFC, real imports in the tableFeatures snippet, and concrete Wrong/Correct diffs that cover the common v9 mistakes.

5 / 5

Workflow Clarity

As a single-purpose creation skill, the single action is unambiguous and the Common Mistakes section functions as a validation checklist; no destructive or batch operation triggers the cap-3 requirement.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers and a one-level-deep pointer to node_modules type definitions, but there is no separate-file reference split of the kind that characterizes a 5.

4 / 5

Total

19

/

20

Passed

Description

75%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, clearly conveying a niche v9 Vue table skill. Its main weakness is the missing explicit "Use when..." trigger clause, which caps the completeness dimension.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when creating or migrating Vue tables with TanStack Table v9, or when the user mentions Vue + TanStack tables, FlexRender, or useTable').

Include common natural variations and file cues (e.g., 'Vue tables', 'TanStack Table', '.vue table components') to broaden trigger-term coverage.

Reconsider whether the headline verb 'Create' covers the full intent — adding 'migrate' or 'build' verbs would better match how users phrase the request.

DimensionReasoningScore

Specificity

Enumerates multiple concrete v9 actions — useTable, explicit tableFeatures, stable columns/features, reactive ref/computed data, and FlexRender without destructuring — giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

The "what" is clearly and concretely stated, but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes solid domain terms ("Vue TanStack Table", "v9", "FlexRender") but lacks common natural variations or file extensions a user might actually say, so it is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The combined Vue + TanStack Table + v9 scope carves a clear niche with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
TanStack/table
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.