Conciseness

The body is dense reference material with executable snippets and config tables rather than padded prose, e.g. 'Register each plugin once so GSAP (and bundlers) know to include it' followed immediately by code. It slips slightly below a 5 because of redundancy like repeated Draggable+Inertia registration examples and prose restating what the tables already say ('Register with Draggable when using inertia: true').

Actionability

Nearly every section ships copy-paste-ready code with a concrete target and vars (e.g. 'Flip.getState(".item")' → DOM change → 'Flip.from(state, { duration: 0.5, ease: "power2.inOut" })'), plus per-plugin option tables and concrete tips like 'use shapeIndex: "log" once to log the auto-calculated value'. Minor plugins (EasePack, CustomWiggle, CustomBounce) have no snippet, but their guidance is trivially executable and the common cases are fully covered.

Workflow Clarity

Multi-step sequences are explicit and ordered: 'Capture state with Flip.getState(), then apply changes..., then use Flip.from()', registration 'before using the plugin in any tween or API call', and the SplitText create → animate → revert lifecycle including autoSplit/onSplit cleanup. No validation checkpoints exist, but nothing here is destructive or batch, so no cap applies; it misses a 5 only because guidance like verifying a plugin is registered before use or checking DrawSVG's stroke prerequisites is implicit rather than a checkpoint.

Progressive Disclosure

The file is well-sectioned (Scroll, DOM/UI, Text, SVG, Easing, Physics) with 'Learn more' links, but there is no bundle at all — references/, scripts/, and assets/ do not exist — so everything is inlined in a ~430-line SKILL.md. Exhaustive option tables like the 16-row SplitText config table and the 12-row MorphSVG table are exactly the bulk API reference material the anchor describes as 'content that should be separate is inline'.

Specificity

It names the domain and enumerates concrete, real capabilities — 'registration, ScrollToPlugin, ScrollSmoother, Flip, Draggable, Inertia, Observer, SplitText, ScrambleText... CustomEase... GSDevTools' — covering the full plugin surface. It sits below the 5 anchor because the items are plugin names with only one action verb ('registration') rather than multiple stated actions like 'animates scroll position' or 'makes elements draggable'.

Completeness

Both halves are explicit: the 'what' is the concrete scope 'Official GSAP skill for GSAP plugins — registration, ScrollSmoother, Flip, Draggable...' and the 'when' is a concrete trigger clause 'Use when the user asks about a GSAP plugin, scroll-to, flip animations, draggable, SVG drawing, or plugin registration', matching the what-plus-when anchor exactly. Not a 4 because the 'when' clause is already specific and enumerates concrete trigger phrases.

Trigger Term Quality

Good natural phrases users would actually say: 'scroll-to', 'flip animations', 'draggable', 'SVG drawing', 'plugin registration', 'GSAP plugin'. It misses common variations users also say for covered plugins — 'text animation'/'split text', 'morph/morphsvg', 'scroll smoother', 'custom ease' — keeping it at 4 rather than the comprehensive-synonym 5 anchor.

Distinctiveness Conflict Risk

The GSAP-plugin niche is clear and triggers like 'ScrollToPlugin', 'Flip', 'GSDevTools' are unmistakable for this skill. There is minor overlap risk with sibling skills it does not disambiguate in the description itself — generic terms like 'draggable' or 'flip animations' could also pull gsap-core or gsap-scrolltrigger in a plugin-question context — keeping it just below the 5 anchor.