Lean and efficient throughout: it assumes Claude's competence, never explains what a scroll-scrub sequence is, and uses tight lists and short code blocks where every line carries information. Not a level below because there is no padding or redundant explanation.

Provides copy-paste-ready code for the core paths — the `sequence` config object, the normalized `progress` formula, and a complete `ScrollTrigger.create` block — plus specific per-renderer directives. The dependency-free path is described rather than coded, but the bulk is fully executable.

'Build the scroll stage' is a clearly numbered six-step sequence, and a dedicated 'Verify' section acts as an explicit validation checklist ('The same scroll position must always reproduce the same state') covering reverse scrolling, fast flicks, resize, reduced motion, and cleanup.

The body is well-organized and signals one-level-deep references to demo/index.html, demo/PROMPT.md, and REFERENCES.md, but none of those bundle files exist on disk, so the signaled navigation is broken and does not resolve.

Lists multiple concrete capabilities — 'Build reversible scroll-controlled visual transformations with a pinned or sticky stage, normalized progress, and video, image-sequence, canvas, SVG, or DOM renderers' — naming the mechanism and every renderer option rather than vague abstractions.

Explicitly answers both what (build reversible scroll-controlled visual transformations with a pinned/sticky stage, normalized progress, and listed renderers) and when (the 'Use for ... that must move forward and backward with native scrolling' trigger clause).

The 'Use for' clause lists natural user-facing terms — 'hero transformations, product assembly, interface state walkthroughs, object rotation, diagrams, or photo sequences' — that a user would plausibly say when reaching for this skill.

The scroll-scrubbed, reversible, pinned-stage niche with specific renderer types and motion scenarios is a clear, narrow domain unlikely to trigger for unrelated skills.