Content
67%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |