CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dom-performance

Use when reviewing scripts, client components, bundles, or runtime behavior related to Minimize costly DOM read/write operations. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug. In React, repeated requestAnimationFrame-driven state updates across multiple mounted components are a valid performance smell when visible in the source.

Quality

76%

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

Quality

Content

67%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, mostly lean rule skill: a tight Quick Reference of concrete directives, clearly delineated task modes, and a properly signaled one-level reference file with executable examples and verification steps. The main flaws are the verbatim-duplicated layout-thrashing intro explaining a concept Claude already knows, and the absence of any inline code example or sequenced validation in the body itself.

Suggestions

Delete or condense the opening layout-thrashing paragraph — it explains a concept Claude already knows and duplicates references/rule.md's 'Why It Matters' section verbatim.

Add one minimal before/after read-batching snippet inline in the Quick Reference so the most common case is executable without opening the reference.

Summarize the reference's Verification checklist (e.g., its first two steps) inside the Code Review section so validation checkpoints appear in the body's workflow.

DimensionReasoningScore

Conciseness

The opening paragraph explains layout thrashing — 'the browser must synchronously recalculate layout (reflow)... This is called layout thrashing and is one of the most common causes of janky animations and slow renders' — a concept Claude already knows, and it duplicates the 'Why It Matters' section of references/rule.md verbatim. The Quick Reference bullets and task sections are otherwise tight. Not 2 because only one paragraph is padded; not 4 because that duplicated concept explanation is a clear trim.

3 / 5

Actionability

Concrete directives name specific APIs — 'offsetHeight, getBoundingClientRect', 'requestAnimationFrame', 'DocumentFragment', 'passive listeners for scroll, touch, and wheel' — and Fix gives an explicit refactor strategy ('batch all DOM reads before writes, eliminating forced synchronous layouts'), with fully executable before/after code in references/rule.md. Not 5 because the body itself contains no inline code example; not 3 because the guidance is specific and complete executable examples sit one clearly signaled reference away.

4 / 5

Workflow Clarity

The Check / Fix / Explain / Code Review sections each give unambiguous instructions ('Identify any layout thrashing in this code... Also flag scroll, touch, and wheel listeners that should be passive'), and verification is explicitly demanded ('state how the change should be verified in the browser') with a 5-step Verification checklist in references/rule.md. Not 5 because the body presents parallel task modes rather than a sequenced workflow and the validation steps live only in the reference; not 3 because each mode is unambiguous and verification is required.

4 / 5

Progressive Disclosure

The body is a lean overview with a clearly signaled one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') to a real bundle file containing the promised details. Not 5 because the 'Why It Matters' paragraph is duplicated verbatim between body and reference rather than cleanly split; not 3 because structure and navigation are otherwise exemplary.

4 / 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 description with an explicit 'Use when' trigger clause, concrete inspection actions, and a specific React performance smell example. It never crisply states the skill's outputs and misses natural synonyms like 'reflow' or 'layout thrashing', holding every dimension at 4 rather than 5.

Suggestions

State the skill's outputs explicitly (e.g., 'Flags interleaved DOM read/write loops and non-passive listeners, and refactors to batched reads/writes') so the 'what' does not rely on the embedded rule title.

Add natural synonyms users say for this domain — 'reflow', 'layout thrashing', 'janky animations', 'scroll performance' — to trigger term coverage.

Narrow the opening trigger ('reviewing scripts, client components, bundles') toward DOM/browser-performance contexts to reduce overlap with generic code-review skills.

DimensionReasoningScore

Specificity

Names several concrete actions and targets — 'reviewing scripts, client components, bundles, or runtime behavior', 'Inspect both source code and the browser execution path', and a concrete React smell ('repeated requestAnimationFrame-driven state updates across multiple mounted components are a valid performance smell') — but never states what the skill actually does with the rule (check, fix, explain). Not 5 because 'Minimize costly DOM read/write operations' is a rule title standing in for an action, not a verb phrase; not 3 because well more than 1-2 concrete actions are given.

4 / 5

Completeness

The 'when' is explicit ('Use when reviewing scripts, client components, bundles, or runtime behavior related to...') and the 'what' is present ('Inspect both source code and the browser execution path so fixes target the real bottleneck or bug'). Not 5 because the 'what' leans on the embedded rule name and never states the skill's outputs (flag violations, refactor, explain); not 3 because both what and when are explicitly stated.

4 / 5

Trigger Term Quality

Includes natural review-context keywords users would plausibly say — 'scripts', 'client components', 'bundles', 'runtime behavior', 'React', 'requestAnimationFrame-driven state updates', 'DOM read/write'. Not 5 because common synonyms for this domain are missing ('reflow', 'layout thrashing', 'jank', 'scroll performance'); not 3 because coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

The DOM read/write anchoring and the specific React rAF-state-update smell give it a clear niche distinct from generic review skills. Not 5 because the broad opening 'reviewing scripts, client components, bundles, or runtime behavior' overlaps with any JavaScript code-review skill; not 3 because the DOM-specific triggers keep that overlap minor.

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-performance/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.