Conciseness

The body is largely lean with concrete, GSAP-specific guidance, but the 'Best practices' section (lines 67-72) restates stagger, quickTo, and cleanup guidance already covered above, and the 'Do Not' section partially overlaps as well. This is anchor 4's 'minor instances that could be trimmed' rather than anchor 5's every-token-earns-its-place, and not anchor 3 since there is no concept over-explanation or padding beyond the redundant summary sections.

Actionability

Concrete property lists (x, y, scaleX, rotation, opacity), an executable copy-paste quickTo example, a will-change CSS snippet, and named commands (ScrollTrigger.refresh(), stagger) give mostly executable guidance. It falls short of anchor 5 because some guidance stays advisory without the 'how' — 'Pause or kill off-screen or inactive animations' gives no API (e.g. gsap.killTweensOf) or detection method, and stagger usage is named but not shown.

Workflow Clarity

As a best-practices reference rather than a multi-step process, the content is well organized: a clear 'When to Use' entry point, topic sections, and consolidated do/don't lists, with no destructive or batch operations requiring validation. It does not reach 5 because there is no optimization sequence (e.g., measure/profile FPS first, then apply transforms, then re-measure) to guide an actual performance-tuning task.

Progressive Disclosure

The skill is self-contained with clear section headers and a one-level, well-signaled pointer to sibling skills ('for ScrollTrigger performance see gsap-scrolltrigger'). It sits at anchor 4 rather than 5 because the body exceeds 50 lines with the ScrollTrigger section duplicating scope a sibling skill already covers, and the 'Best practices'/'Do Not' sections restate inline content instead of tightening the structure.

Specificity

Lists several concrete items — 'prefer transforms, avoid layout thrashing, will-change, batching' — which is more than the 1-2 items of anchor 3 but falls short of anchor 5's comprehensive coverage (no mention of stagger, quickTo, or cleanup).

Completeness

Explicitly answers both 'what' (prefer transforms, avoid layout thrashing, will-change, batching) and 'when' with a concrete 'Use when...' clause naming multiple trigger scenarios, matching the anchor 5 example structure exactly. Not 4, since the 'when' clause is explicit and specific rather than needing more detail.

Trigger Term Quality

Natural user phrasing is well covered — 'optimizing GSAP animations', 'reducing jank', 'animation performance', 'FPS', 'smooth 60fps' — but common variations like 'lag', 'stuttering', or 'dropped frames' are missing, matching anchor 4 rather than anchor 5's comprehensive synonym coverage.

Distinctiveness Conflict Risk

Clear niche — GSAP-specific performance with explicit 'optimizing GSAP animations' triggers — minimal overlap risk with sibling skills (gsap-core, gsap-timeline, gsap-scrolltrigger) or generic web-performance skills.