Content
39%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides useful code snippets for scroll-driven animations across multiple libraries, which is its primary strength. However, it suffers from significant verbosity (repeating the description, explaining obvious concepts), lacks any coherent workflow for building scroll experiences, and references non-existent sections in the Sharp Edges table. The formatting also has structural issues with nested code blocks.
Suggestions
Remove the verbose role description, capabilities list, and tautological 'When to Use' section to improve token efficiency — Claude doesn't need to be told what parallax is.
Add a clear workflow section that sequences the steps for building a scroll experience (e.g., 1. Choose library → 2. Set up smooth scroll → 3. Add animations → 4. Test performance → 5. Verify accessibility), with explicit validation checkpoints for performance and accessibility.
Either create the referenced bundle files (Fixing Scroll Jank, Mobile-Safe Parallax, etc.) or replace the Sharp Edges solution column with inline actionable guidance.
Fix the markdown formatting — code blocks are nested inside pattern code fences, causing rendering issues. Restructure patterns as proper sections rather than code-fenced content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is noticeably verbose with significant padding. The role description repeats the frontmatter description verbatim, the 'Capabilities' bullet list adds no actionable value, the 'When to Use' section is a tautology, and the anti-patterns section explains concepts Claude already understands (e.g., 'users hate losing scroll control'). The library comparison tables add some value but the overall token budget is poorly spent. | 2 / 5 |
Actionability | The skill provides concrete, executable code examples across multiple frameworks (GSAP, Framer Motion, CSS scroll-timeline) that are mostly copy-paste ready. However, some sections like 'Story Beats' and 'Text Reveals' are vague bullet lists rather than executable guidance, and the Sharp Edges table references solutions (e.g., '## Fixing Scroll Jank') that don't exist anywhere in the document. | 4 / 5 |
Workflow Clarity | There is no clear workflow or sequencing for building a scroll experience. The patterns are presented as isolated snippets without a coherent process for combining them. There are no validation steps (e.g., performance testing, accessibility checks) despite the skill involving potentially performance-impacting operations. The anti-patterns hint at concerns but don't integrate into a workflow. | 2 / 5 |
Progressive Disclosure | The content is a monolithic file with no bundle files to reference. The Sharp Edges table references sections ('## Fixing Scroll Jank', '## Mobile-Safe Parallax') that don't exist, creating broken navigation. The code examples are nested inside markdown code blocks that are themselves inside code blocks (triple-backtick nesting issues), and there's no clear separation between overview and detailed reference material. | 2 / 5 |
Total | 10 / 20 Passed |