CtrlK
BlogDocsLog inGet started
Tessl Logo

with-tanstack-virtual

Virtualize Vue Table final row or column models with reactive counts and scroll targets, stable keys, measurement, spacer geometry, sticky CSS, grid/flex widths, and infinite server data.

60

Quality

71%

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/with-tanstack-virtual/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 concise and actionable with executable Setup and Common Mistakes examples, and it is well-organized into clear sections. It would benefit from explicit validation checkpoints in its workflow and slightly fuller code for the Core Patterns.

Suggestions

Add an explicit validation/checkpoint step (e.g. verify the virtual range updates on sort/filter changes, confirm getTotalSize() drives the spacer) to lift workflow clarity above 3.

Expand the "Implement the geometry" and "Coordinate infinite fetching" Core Patterns with a short executable snippet each so the guidance is fully copy-paste ready rather than descriptive.

DimensionReasoningScore

Conciseness

The body is lean and assumes Vue/TanStack competence, never explaining what virtualization is or how the libraries work; every line (intro, patterns, mistakes) earns its place.

5 / 5

Actionability

The Setup block and the wrong/correct Common Mistakes examples are executable TypeScript/Vue, but the Core Patterns (e.g. "Implement the geometry") stay partly descriptive instead of giving full code, leaving minor gaps.

4 / 5

Workflow Clarity

A sequence is present (derive from models -> implement geometry -> coordinate infinite fetching), but there are no explicit validation checkpoints or feedback loops; steps are listed with implicit checkpoints.

3 / 5

Progressive Disclosure

The single file is well-sectioned (Setup, Core Patterns, Common Mistakes, API Discovery) with no nested references, but at ~96 lines the under-50-line simple-skill exception does not apply and no bundle files split the content further.

4 / 5

Total

16

/

20

Passed

Description

67%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, naming a clear niche and many concrete capabilities. Its main weakness is the absence of an explicit "Use when..." trigger clause and a reliance on technical jargon over natural user phrasing.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases, e.g. "Use when virtualizing rows or columns of a Vue TanStack Table, or when handling infinite scroll over server data."

Soften jargon with user-facing synonyms such as "scroll virtualization", ".vue files", and "tanstack virtual" so the description matches phrases users actually say.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities ("reactive counts and scroll targets, stable keys, measurement, spacer geometry, sticky CSS, grid/flex widths, and infinite server data"), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

The "what" is clear, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural terms like "Virtualize", "Vue Table", and "infinite" appear, but the bulk ("spacer geometry", "sticky CSS", "grid/flex widths") is technical jargon and common synonyms (e.g. "scroll virtualization", ".vue", "tanstack virtual") are missing.

3 / 5

Distinctiveness Conflict Risk

"Virtualize Vue Table" pins a narrow niche tied to a specific library and framework, so it is clearly distinguishable with minimal conflict risk.

5 / 5

Total

16

/

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.