Content
57%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.
The body delivers solid, executable pattern code for scroll animations, parallax, and sticky sections, plus useful anti-patterns. Its main weaknesses are padding (duplicated persona text, empty boilerplate sections), a missing implementation workflow with validation checkpoints, and dangling references to solution sections that were never written.
Suggestions
Either write the four solution sections referenced in the Sharp Edges table (Fixing Scroll Jank, Mobile-Safe Parallax, Accessible Scroll Experiences, Content-First Scroll Design) or remove those references and inline one-line fixes.
Delete the duplicated Role/persona block and the empty "When to Use" filler; replace the latter with real trigger guidance and a short sequenced workflow (pick stack → design story beats → implement → test on mobile → verify performance).
Add validation checkpoints for the risky cases the skill itself flags, e.g., verify prefers-reduced-motion support and test scroll performance on a real device before considering a section done.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The code snippets and tables are lean, but the body pads tokens with non-instructing material: the frontmatter description is repeated verbatim as the Role block, filler lines like "Tools and techniques for scroll animations" and "Tell stories through scroll depth" add nothing, and the closing "When to Use" section is empty boilerplate ("This skill is applicable to execute the workflow or actions described in the overview."). Mostly efficient but could be tightened — fits anchor 3, not 4, because the padding is more than minor. | 3 / 5 |
Actionability | Concrete, largely copy-paste-ready code is provided for the common cases: GSAP ScrollTrigger setup, Framer Motion useScroll/useTransform parallax, native CSS scroll-timeline, CSS sticky, GSAP pin, and horizontal scroll sections. Not anchor 5 because key details are missing or broken: the Sharp Edges table's "Solution" column points to sections ("## Fixing Scroll Jank", "## Mobile-Safe Parallax", "## Accessible Scroll Experiences", "## Content-First Scroll Design") that do not exist anywhere in the skill, so the highest-severity fixes have no actionable guidance. | 4 / 5 |
Workflow Clarity | The skill is a pattern reference rather than a workflow: the story-beats sequence (Hook → Context → Journey → Climax → Resolution) gives a rough narrative order, and each pattern has a "When to use" note, but there is no sequenced implementation workflow (choose stack → design beats → implement → verify mobile/performance) and no validation checkpoints. Anchor 3 (sequence present but checkpoints missing) fits better than 4, which requires most checkpoints. | 3 / 5 |
Progressive Disclosure | Section structure exists (## Patterns with ### subsections, anti-patterns, sharp edges) and no bundle files are provided, so everything is inlined — acceptable for a ~250-line skill but the three full pattern guides are candidates for split-out references. The decisive defect is that the Sharp Edges table references four solution sections that don't exist, so navigation fails exactly where it is signaled. Anchor 3 (some structure, could be better organized) rather than 2, since headers and tables do provide real navigable structure. | 3 / 5 |
Total | 13 / 20 Passed |