CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

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/dom-size/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured body that puts concrete thresholds and directives in SKILL.md and correctly delegates code examples to a real, clearly signaled one-level-deep reference file. Its weaknesses are minor: a small amount of background Claude already knows, and a Check step that names tools without the exact command or audit to run.

Suggestions

Drop or compress the opening background sentence and merge the thin one-line 'Explain' section into it — Claude already knows why large DOMs are slow.

Add one executable check to the Check section, e.g., the Lighthouse 'DOM Size' audit, the DevTools Elements node count badge, or `document.querySelectorAll('*').length`.

Close the loop after Fix with an explicit re-measure step (re-run the DOM size audit to confirm nodes < 1,500 and depth < 32).

DimensionReasoningScore

Conciseness

The body is tight — a Quick Reference with concrete thresholds, four short directive sections, and a clearly signaled pointer to references/rule.md. Not a 5 because the opening sentence ("An excessive DOM size increases memory usage, slows down style calculations...") and the one-line "Explain" section restate performance concepts Claude already knows and could be trimmed.

4 / 5

Actionability

Concrete numeric targets ("below 1,500" nodes, "maximum depth < 32"), named tools ("Lighthouse or Chrome DevTools"), and specific fix actions ("remove unnecessary wrapper elements", "implement virtualization"), with executable code deferred to a real reference file. Not a 5 because the Check step lacks the exact command or audit name (e.g., Lighthouse 'DOM Size' audit or DevTools node counter) to be copy-paste ready.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review section flow gives a clear measure-first-then-fix sequence, and the Code Review section explicitly requires describing the measurement method used to confirm the issue. Not a 5 because there is no post-fix re-measurement/validation checkpoint to close the loop, and the sequence is implied by section order rather than stated.

4 / 5

Progressive Disclosure

Clean overview structure with a single, clearly signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and the referenced file exists and delivers exactly that (110 lines of code examples). Content is appropriately split: thresholds and directives in SKILL.md, implementation detail in the reference.

5 / 5

Total

17

/

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 description with an explicit 'Use when' trigger clause, concrete verification actions, and named tooling. Its main weakness is an implicit 'what' — it says when to audit and to verify first, but never states the concrete remediation guidance the skill provides, and it lacks the natural synonyms (large DOM, too many nodes) users would actually say.

Suggestions

State the skill's concrete outputs in the description (e.g., 'Simplify HTML structure, remove unnecessary wrappers, and virtualize long lists to keep DOM nodes under ~1,500') so the 'what' is explicit rather than implied by the rule title.

Add natural trigger synonyms: 'DOM too large', 'too many DOM nodes', 'Lighthouse DOM size audit failed', 'page renders slowly'.

Trim broad triggers like 'heavy assets' that fire for unrelated performance skills (image optimization, unused JavaScript) to reduce conflict risk with sibling rules.

DimensionReasoningScore

Specificity

Lists several concrete actions — "auditing slow page loads, heavy assets, or rendering delays", "Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes" — with named tools. Not a 5 because the actual remediation capabilities (simplify HTML, virtualize lists) are absent, so coverage has minor gaps.

4 / 5

Completeness

The 'when' is explicit ("Use when auditing slow page loads, heavy assets, or rendering delays related to...") and a partial 'what' is present ("Verify the actual bottleneck... before recommending changes"). Not a 5 because the 'what' never states what the skill actually delivers — reducing DOM node count, simplifying structure, virtualizing lists — only that it verifies and recommends.

4 / 5

Trigger Term Quality

Good natural terms users would say: "slow page loads", "heavy assets", "rendering delays", "DevTools", "Lighthouse". Not a 5 because common variations like "DOM too large", "too many DOM nodes", or "Lighthouse DOM size audit" are missing, and "Reduce DOM size and complexity" reads as a pasted rule title rather than a natural phrase.

4 / 5

Distinctiveness Conflict Risk

The rule name plus tool-specific verification ("DevTools, Lighthouse, or field data") gives it a mostly distinct niche. Not a 5 because broad triggers like "slow page loads" and "heavy assets" overlap with sibling performance skills (image optimization, unused JavaScript) before the DOM qualifier disambiguates.

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/dom-size/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.