Content
77%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.
A thorough, highly actionable GSAP plugin reference with excellent non-obvious guidance (post-acquisition licensing) and copy-paste examples for every plugin. Its weaknesses are token weight and monolithic structure — large API tables and repeated registration boilerplate live inline rather than in one-level reference files.
Suggestions
Move the large per-plugin config tables (e.g. SplitText's 15-row table and MorphSVG's table) into a references/ file and link from SKILL.md, keeping only a concise example plus the key gotcha inline — this improves both conciseness and progressive_disclosure.
Show the multi-plugin gsap.registerPlugin() pattern once prominently and drop the repeated import/register boilerplate from each per-plugin code block.
Consolidate the 'Best practices' and 'Do Not' guardrails into the relevant plugin sections (or a single short checklist) so the guidance lands next to the code it constrains instead of as a trailing appendix.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and high-value (the licensing/install section is non-obvious and well-targeted), but at ~430 lines it repeats registration/import boilerplate in every code block and inlines large API tables (SplitText's 15-row table, MorphSVG) that could be tightened or split out. | 2 / 3 |
Actionability | Every plugin ships a fully executable, copy-paste-ready code block with specific config — e.g. 'Flip.getState(".item")' then 'Flip.from(state, { duration: 0.5, ease: "power2.inOut" })' and 'SplitText.create(".heading", { type: "words, chars" })'. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced ('Register before using', Flip's getState -> change DOM -> from, 'register after ScrollTrigger' for ScrollSmoother); there are no destructive or batch operations that would require validation checkpoints, so their absence is appropriate. | 3 / 3 |
Progressive Disclosure | Section organization is good (## Scroll, ## DOM/UI, ## Text, etc.) with one-level external 'Learn more' links, but the skill is monolithic — large reference tables are inline and no bundle/reference files exist, so content that should be separate stays in SKILL.md. | 2 / 3 |
Total | 10 / 12 Passed |