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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 a clean, well-structured review skill: concise sections, concrete directives, a measurement checkpoint, and a single clearly signaled reference file for depth. The only meaningful gap is the absence of an explicit measurement-failure feedback loop and copy-paste executable examples.

Suggestions

Add an explicit feedback loop after the measurement step (e.g., 'If scroll smoothness or DOM node count does not improve, revert and reconsider whether virtualization is the right fix').

Include a small concrete example of the measurement command or metric thresholds (e.g., target DOM node count or FPS) to push actionability toward copy-paste ready.

Optionally show a minimal before/after node-count snippet so reviewers can apply the checkpoint directly.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — tight Quick Reference bullets and focused Check/Fix/Explain/Code Review sections with no padded concept explanations, so every token earns its place per the 'lean and efficient' anchor.	5 / 5
Actionability	Directives are concrete and actionable ('Render only what is visible plus a small overscan buffer', 'Measure scroll smoothness, memory use, and DOM node count before and after'), but as an instruction-only skill it lacks copy-paste executable artifacts, so it sits at 'mostly executable guidance with minor gaps' rather than the fully copy-paste 5.	4 / 5
Workflow Clarity	Check → Fix → Explain → Code Review form a clear sequence with an explicit measurement checkpoint ('Measure... before and after the change'), but there is no error-recovery feedback loop (e.g., 'if metrics do not improve, revert'), keeping it below the explicit-loop anchor 5.	4 / 5
Progressive Disclosure	The SKILL.md is a well-organized overview with clearly signaled one-level-deep navigation to the existing references/rule.md for full details, matching the 'clear overview with well-signaled one-level-deep references' anchor.	5 / 5
	Total	18 / 20 Passed

Description

78%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 strong: it states a clear trigger ('Use when reviewing...'), names concrete UI surfaces, and includes a useful guardrail that sharpens when the skill applies. Its main weakness is an indirect 'what' framed as a precondition rather than a direct capability statement.

Suggestions

Lead with a direct capability statement (e.g., 'Reviews large repeated-item lists/tables/feeds and recommends virtualization') before the 'Use when' clause so the 'what' is unambiguous.

Add natural synonyms users might say — 'long lists', 'grids', 'infinite scroll', 'windowing' — to broaden trigger coverage.

Consider naming the concrete outputs (e.g., 'flags views that mount too many rows and prescribes overscan/windowing') to lift specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain (repeated-item UIs) and several concrete actions — 'reviewing dashboards, admin tables, search results, or feeds' and 'Confirm the bottleneck is DOM or rendering cost before introducing virtualization' — with only minor coverage gaps, matching the 'lists several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	Both halves are present — an explicit 'Use when...' trigger and a 'what' (confirm the DOM/rendering bottleneck before virtualizing) — but the 'what' reads as a conditional guardrail rather than a clean capability statement, leaving it just below the explicit-both anchor 5.	4 / 5
Trigger Term Quality	'dashboards, admin tables, search results, or feeds with many repeated items' are natural phrases users say, giving good keyword coverage, but common synonyms like 'long lists', 'grids', or 'infinite scroll' are missing so it stops short of the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The trigger is narrowly scoped to 'many repeated items' in dashboards/tables/feeds and the guardrail that 'small lists usually do not need' the complexity carves a clear niche with minimal overlap risk, matching the distinct-triggers anchor.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/list-virtualization/SKILL.md
Commit: 30756a7

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.