CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

list-virtualization

Use when reviewing dashboards, admin tables, search results, or feeds with many repeated items. Confirm the bottleneck is DOM or rendering cost before introducing virtualization because small lists usually do not need the added complexity.

Quality

77%

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 ./skills/list-virtualization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 clean, well-structured overview body: concise sections, a coherent check/fix/review workflow with a before-and-after measurement checkpoint, and exemplary one-level progressive disclosure to references/rule.md. The main gap is actionability — the body stays at the directive level with no concrete thresholds, tooling, or code, deferring all executable specifics to the reference file.

Suggestions

Inline the concrete decision thresholds from references/rule.md into the Check section (e.g., 'roughly 100-200 repeated items' or '~1,500 total DOM nodes') so 'large enough' is actionable without hopping to the reference.

Name the measurement method for the before/after checkpoint (e.g., a devtools performance trace while scrolling, and an inspector DOM node count) so the validation step is executable rather than aspirational.

Since the reference's code examples are incomplete (the tsx snippets are missing imports, component names, and the virtualization setup), add one minimal working virtualization snippet — or a named library pattern — in the body or repair the reference so the 'framework-specific guidance' the body promises actually exists.

DimensionReasoningScore

Conciseness

The body is lean and sectioned for purpose ("Render only what is visible plus a small overscan buffer instead of the entire list"; "Measure scroll smoothness, memory use, and DOM node count before and after the change"), with only minor trimmable fat: the intro paragraph ("Rendering hundreds or thousands of rows at once wastes memory...") explains a concept Claude already knows, and the Quick Reference bullets partially restate the Check/Fix sections. Anchor 5's 'every token earns its place' is not quite met.

4 / 5

Actionability

The guidance is directive and names concrete concerns (overscan buffer, keyboard navigation, screen-reader semantics, sticky headers, selection behavior), but the body contains no thresholds, library names, commands, or code — "Flag views where the number of mounted rows or cards is large enough" leaves 'large enough' undefined, and the executable specifics (100-200 items, ~1,500 nodes, code) live only in the reference file. This fits anchor 3's 'concrete guidance but incomplete; missing key details' better than anchor 4's mostly-executable guidance.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent review sequence, and a validation checkpoint is present ("Measure scroll smoothness, memory use, and DOM node count before and after the change"; Code Review verifies semantics and interactions are preserved). It falls short of anchor 5 because there is no explicit validate-and-retry loop after a fix, only minor validation gaps per anchor 4.

4 / 5

Progressive Disclosure

The body is a clear overview with a single, well-signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists in the bundle. Content is appropriately split between overview and detail with no nested-reference chains, matching the anchor 5 structure.

5 / 5

Total

16

/

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.

A well-crafted description: it pairs an explicit, concrete 'Use when' trigger with specific, conditional guidance (confirm DOM/rendering bottleneck before virtualizing) that both scopes the skill and disambiguates it from general performance advice. Its only weaknesses are a guidance-styled rather than declarative capability statement and a few missing natural synonyms like 'long lists' or 'scroll jank'.

DimensionReasoningScore

Specificity

Lists several specific actions — "Confirm the bottleneck is DOM or rendering cost before introducing virtualization" and skipping it because "small lists usually do not need the added complexity" — rather than generic filler. It stops short of anchor 5 because coverage is narrow (no mention of measuring, implementing, or verifying virtualization), but it exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Both what and when are present: an explicit "Use when reviewing dashboards, admin tables, search results, or feeds..." trigger clause, and the what ("Confirm the bottleneck is DOM or rendering cost before introducing virtualization"). Not anchor 5 because the what is phrased as conditional guidance rather than a declarative capability statement (e.g., 'Virtualizes long lists and tables').

4 / 5

Trigger Term Quality

Natural user-facing terms are well covered: "dashboards", "admin tables", "search results", "feeds", "many repeated items", "DOM", "rendering cost". A few natural phrases users would say are missing (e.g., "long lists", "grids", "scroll jank", "thousands of rows"), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (list virtualization with a confirm-bottleneck-first guard) is distinct and the trigger surfaces are concrete, so it is unlikely to fire for unrelated skills. Minor overlap risk remains with sibling frontend-performance or dashboard-review skills that share the "reviewing dashboards" trigger, keeping it below anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/list-virtualization/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.