CtrlK
BlogDocsLog inGet started
Tessl Logo

tanstack-virtual

Headless UI for virtualizing large element lists at 60FPS in TS/JS, React, Vue, Solid, Svelte, Lit & Angular.

60

Quality

68%

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

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable reference skill: lean, executable code, complete option/API tables, and useful pitfalls/best-practices checklists. Its main weakness is that it is a monolithic 370-line catalog with no progressive disclosure into separate reference files.

DimensionReasoningScore

Conciseness

The body is lean reference material with no concept-padding (the Overview is two sentences and never explains what virtualization is), and nearly every token is API/options/code that Claude would not already know. Not level 2 because there is no discernible fluff or redundant explanation that could be cut without losing value.

3 / 3

Actionability

It provides complete, copy-paste-ready components (core pattern, dynamic heights, grid, window, horizontal) plus typed options tables and concrete API signatures. Not level 2 because the examples are executable rather than pseudocode; the few comment placeholders (infinite scroll render, sticky styling) are minor and do not undermine overall executability.

3 / 3

Workflow Clarity

The few multi-step patterns (infinite scroll detection, dynamic measurement) are sequenced with explicit do/don't notes, but the skill is fundamentally an API/options catalog rather than a workflow, and validation feedback loops (validate → fix → retry) are absent. Not level 1 because patterns are clearly laid out; not level 3 because there are no integrated validation checkpoints and the bulk is reference, not a sequenced validated process.

2 / 3

Progressive Disclosure

Sections are well-organized, but the ~370-line skill is a monolith with no bundle files and no one-level-deep references, so content that could be split (API reference, full examples) sits inline. Not level 1 because the section structure is clear, not nested-maze; not level 3 because for a skill this size, well-organized sections alone are insufficient without splitting into reference files.

2 / 3

Total

10

/

12

Passed

Description

57%

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 distinctive about its virtualization niche and supported frameworks, but it omits any explicit "when to use" trigger guidance and lacks common trigger-term variations like "virtual scroll" or "windowing". This leaves it competent but incomplete as an invocation signal.

Suggestions

Add a "Use when..." clause with explicit triggers, e.g. "Use when rendering large lists, grids, or tables that need virtualization/windowing for performance, or when the user mentions virtual scroll, windowing, or thousands of rows."

Broaden trigger terms to natural phrasings users actually say: "virtual scroll", "windowing", "infinite list", "large list performance", "render thousands of rows".

Surface concrete actions beyond the single capability — e.g. "virtualize lists, grids, and tables; measure dynamic/variable heights; horizontal scrolling; infinite loading".

DimensionReasoningScore

Specificity

It names a concrete capability — "virtualizing large element lists at 60FPS" — plus the supported frameworks, but describes essentially one action rather than the multiple concrete actions the level-3 anchor requires (e.g. "extract, fill, merge"). Not level 1 because the action and domain are specific, not vague.

2 / 3

Completeness

It clearly states what the skill does ("Headless UI for virtualizing large element lists at 60FPS in TS/JS, React, Vue, Solid, Svelte, Lit & Angular") but has no "Use when..." clause or equivalent explicit trigger guidance, which the guidelines say caps completeness at 2. Not level 1 because the "what" is strong; not level 3 because the "when" is entirely absent.

2 / 3

Trigger Term Quality

"virtualizing large element lists" and the framework names (React, Vue, Solid, Svelte, Lit, Angular) are relevant, but common natural variations users would say — "virtual scroll", "windowing", "infinite list", "large list performance" — are missing. Not level 3 due to that coverage gap; not level 1 because the terms present are natural and on-topic.

2 / 3

Distinctiveness Conflict Risk

"Headless UI for virtualizing large element lists at 60FPS" is a clear, narrow niche with a distinctive multi-framework headless framing, unlikely to trigger for the wrong skill. Not level 2 because it is far more specific than "Works with document files"; the niche is distinct enough to avoid overlap.

3 / 3

Total

9

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
udecode/plate
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.