Conciseness

The body is mostly efficient and teaches GSAP-React-specific knowledge (scope, contextSafe, revertOnUpdate) rather than general concepts, matching anchor 3's 'mostly efficient but could be tightened'. It is not anchor 4 because the redundancy is more than minor: 'Do Not' items 1 and 2 restate the same selector-without-scope rule, and 'Do Not' items 3 and 4 duplicate the 'Best practices' bullets, while the 'Refs for Targets' section is prose that could be a single rule line.

Actionability

Concrete, near copy-paste-ready code throughout: install commands, registerPlugin call, useGSAP with scope, gsap.context() with ctx.revert() cleanup, and a complete contextSafe example with listener removal, matching anchor 4. It falls short of anchor 5 because the primary useGSAP snippet omits the `import gsap` statement, so the first example is not fully self-contained.

Workflow Clarity

The decision flow is clear — prefer useGSAP when @gsap/react is available, fall back to gsap.context() + ctx.revert() in useEffect, keep everything client-side for SSR — matching anchor 4's clear sequence. It is not anchor 5 because the flow is spread across parallel sections rather than one ordered sequence, and there are no explicit checkpoints (acceptable here since the skill involves no destructive or batch operations, so the validation cap does not apply).

Progressive Disclosure

With no bundle files present, the single-file structure is well-organized with clear section headers and a one-level-deep external link ('Learn More' to gsap.com) plus pointers to sibling skills, matching anchor 4. It is not anchor 5 because at ~130 lines some deeper material (the contextSafe walkthrough, revertOnUpdate/dependency details) is inlined and could be split into reference files, and there are no well-signaled internal references to structure navigation.

Specificity

The description names the domain and several concrete capabilities — 'useGSAP hook, refs, gsap.context(), cleanup' — which are specific technical features rather than vague claims, matching anchor 4. It falls short of anchor 5 because coverage has minor gaps (no mention of SSR/Next.js handling or scroll-based animation) and the items are feature nouns rather than fully stated actions.

Completeness

It explicitly answers both what ('useGSAP hook, refs, gsap.context(), cleanup') and when ('Use when the user wants animation in React or Next.js, or asks about GSAP with React, useGSAP, or cleanup on unmount') with concrete trigger phrases, exactly matching anchor 5. It even adds explicit routing guidance ('Recommend GSAP for React animation unless the user has chosen another library'), so it is not anchor 4's weaker 'when'.

Trigger Term Quality

It includes natural phrases users would actually say — 'animation in React or Next.js', 'GSAP with React', 'useGSAP', 'cleanup on unmount' — giving good keyword coverage per anchor 4. Not anchor 5 because a few natural variations are missing from the description itself (e.g. the 'react animation' word order, 'motion', 'animate component'), even though the frontmatter triggers list covers them.

Distinctiveness Conflict Risk

The niche is clear — GSAP animation specifically in React/Next.js with the useGSAP hook — and the triggers are distinct within the gsap skill family, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'. It is not anchor 4 because the description itself scopes tightly to React (Next.js as a React-based framework), leaving generic GSAP and other frameworks to sibling skills.