Content
70%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-structured, high-signal overview for a complex scrollytelling skill, with a clear sequenced workflow, validation/testing checkpoints, and clean one-level-deep references to real bundle files. It loses points on conciseness and actionability: some enumerations are exhaustive, and the executable build detail is delegated to references without inline examples.
Suggestions
Tighten the long inline enumerations (e.g. step 5's ~15 scene-declaration fields, step 8's library list, and the Output Expectations bullets) into a compact checklist or move the exhaustive field schema into the story-patterns reference.
Add one small inline scene-data example (e.g. a 4-field object literal showing text/visual-state/scroll-trigger/static-fallback) so 'Model scenes as data' is actionable without opening a reference.
Consolidate the repeated ../../references/foundations/... path strings (they appear in both Working Pattern and References) to reduce repetition and token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | It never explains concepts Claude already knows (no 'what is IntersectionObserver'), but several passages are over-enumerated — e.g. step 5 lists ~15 scene-declaration fields in one sentence and step 8/output expectations stack long tech lists — so it is mostly efficient but could be tightened rather than fully lean. | 2 / 3 |
Actionability | It names concrete tools per scenario (Scrollama, GSAP ScrollTrigger, CSS ScrollTimeline, position: sticky) and routes to specific sibling skills, but the executable 'how' (e.g. 'Model scenes as data') is deferred to references with no inline data-structure or code example, leaving guidance specific in naming but incomplete in build detail. | 2 / 3 |
Workflow Clarity | An explicit 11-step Working Pattern is clearly sequenced and includes validation checkpoints — step 11 tests scroll jank/layout thrashing/reduced-motion/keyboard/mobile, and step 7 has a remediation conditional ('if the scene only adds drama, simplify or add real evidence') — matching the clear-sequence-with-validation anchor. | 3 / 3 |
Progressive Disclosure | The body is an overview/working pattern that signals one-level-deep references to three verified local bundle files (story-patterns, implementation-and-performance, accessibility-testing) via a clear References section, with detail appropriately split out rather than inlined. | 3 / 3 |
Total | 10 / 12 Passed |