dom-size

Use when auditing slow page loads, heavy assets, or rendering delays related to Reduce DOM size and complexity. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/dom-size/SKILL.md

Quality

Content

65%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 well-structured, token-efficient overview that practices good progressive disclosure by deferring detail to a real reference file. Its gaps are in the body itself: no executable code or commands, and only an implicit verify-then-fix workflow.

Suggestions

Add one or two concrete commands to the Check section (e.g., `document.querySelectorAll('*').length` in the DevTools console) so the body is actionable without requiring the reference.

Make the verify-before-fix loop explicit in the body — e.g., a short "Check → confirm bottleneck → Fix → re-measure" sequence with a re-measurement checkpoint — to lift workflow clarity.

Trim the opening sentence restating that large DOMs hurt performance; Claude already knows this, and the Quick Reference thresholds convey the same point more concretely.

Dimension	Reasoning	Score
Conciseness	The body is lean with short sections and tight bullets, but the opening sentence ("An excessive DOM size increases memory usage, slows down style calculations...") restates a concept Claude already knows, a minor instance of over-explanation that keeps it just below 5.	4 / 5
Actionability	Concrete numeric thresholds (1,500 nodes, depth < 32) and named tools/techniques (Lighthouse, DevTools, virtualization) give some actionable guidance, but the body offers no executable commands or code — those live only in the reference file — leaving key details missing.	3 / 5
Workflow Clarity	The Check → Fix ordering implies a verify-before-act sequence, but checkpoints are implicit rather than explicit feedback loops, and the body presents parallel modes (Check/Fix/Explain/Code Review) rather than a numbered workflow.	3 / 5
Progressive Disclosure	The body is a concise overview with clear section structure and a well-signaled one-level-deep pointer — "see references/rule.md" — to a verified bundle file, making navigation easy and content appropriately split.	5 / 5
	Total	15 / 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 solid, third-person description with explicit trigger guidance and concrete tooling, well above the vague-fluff floor. Its main weakness is under-representing the remediation side of the skill and missing a few natural performance synonyms.

Dimension	Reasoning	Score
Specificity	Names concrete actions tied to specific tools — "auditing slow page loads, heavy assets, or rendering delays" and "Verify the actual bottleneck in DevTools, Lighthouse, or field data" — but coverage is diagnostic only, omitting the remediation actions the skill body covers, so it stops short of 5.	4 / 5
Completeness	It has an explicit "Use when..." trigger clause and a concrete "what" (verify the bottleneck before recommending changes), satisfying both requirements; the "what" is narrow relative to the full skill scope (Fix, Explain, Code Review), keeping it below 5.	4 / 5
Trigger Term Quality	Includes natural user-facing phrases ("slow page loads", "heavy assets", "rendering delays") plus tool names (DevTools, Lighthouse), but misses common synonyms like "performance", "lag", "jank", or "scrolling", so it is good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	The "related to Reduce DOM size and complexity" qualifier and the verify-first guidance carve a clear niche, but the trigger terms overlap with sibling frontend performance skills (bundle size, image optimization), so minor overlap risk remains.	4 / 5
	Total	16 / 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/dom-size/SKILL.md
Commit: 30756a7

Reviewed: 23 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.