CtrlK
BlogDocsLog inGet started
Tessl Logo

with-tanstack-virtual

Virtualize Lit Table final row or column models with @tanstack/lit-virtual VirtualizerController, host lifecycle-aware counts, scroll refs, stable keys, dynamic measurement, sticky CSS, grid/flex sizing, and infinite data. Load for large rendered tables; Virtual is renderer composition, not tableFeatures.

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

87%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.

A tight, highly actionable skill body with executable code and concrete mistake corrections that respects the token budget. Its one weakness is the absence of a sequenced workflow with validation checkpoints for the virtualization lifecycle.

Suggestions

Add a short numbered workflow with an explicit validation checkpoint (e.g. after binding the virtualizer count, confirm rows.length === virtualItems count before rendering).

Include a verify/retry feedback loop for the measurement and scroll-sync operations to satisfy the batch-operation feedback-loop expectation.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: a compact executable setup block plus terse pattern/m mistake entries with no padding and no explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Fully executable copy-paste-ready setup code, concrete Wrong/Correct pairs for each mistake, and precise API-discovery commands pointing at real dist type files — covering the common cases specifically.

5 / 5

Workflow Clarity

The body organizes guidance as patterns and mistakes rather than a sequenced workflow, and provides no explicit validation/feedback-loop steps for the batch scroll-and-measure operations it describes.

3 / 5

Progressive Disclosure

Under 50 lines with no bundle files and well-organized sections (Setup, Core Patterns, Common Mistakes, API Discovery); per the simple-skills note this is appropriately structured for discovery.

5 / 5

Total

18

/

20

Passed

Description

83%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.

A specific, well-scoped description that names concrete capabilities and gives a usable trigger, distinguishing itself clearly from sibling skills. The main gap is the 'when' guidance, which uses 'Load for' instead of an explicit 'Use when…' phrasing.

Suggestions

Add an explicit 'Use when…' clause naming the natural trigger phrases users would say (e.g. 'Use when rendering large Lit tables that need row/column virtualization or infinite scrolling').

Soften the jargon ('host lifecycle-aware counts', 'grid/flex sizing') with a couple of plain-language synonyms so non-expert users match the skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Virtualize Lit Table final row or column models', 'host lifecycle-aware counts', 'scroll refs', 'stable keys', 'dynamic measurement', 'sticky CSS', 'grid/flex sizing', and 'infinite data' — giving comprehensive coverage of capabilities.

5 / 5

Completeness

Provides a clear 'what' (the capability list) and an explicit 'when' ('Load for large rendered tables'), but the trigger is phrased as 'Load for' rather than the canonical 'Use when…' form, so it is not maximally explicit.

4 / 5

Trigger Term Quality

Good domain keywords ('virtualize', 'large rendered tables', 'infinite data') with a usable trigger ('Load for large rendered tables'), but the language is jargon-heavy and missing a few natural phrasings users would actually say.

4 / 5

Distinctiveness Conflict Risk

A clear niche — Lit Table virtualization with @tanstack/lit-virtual — plus the explicit disambiguator 'Virtual is renderer composition, not tableFeatures' makes conflict with other skills minimal.

5 / 5

Total

18

/

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.