Conciseness

The body is a lean reference that explains only GSAP-specific, non-obvious conventions (the 'omit the value to get a function' pattern) and never explains concepts Claude already knows, but that pattern is restated in roughly eight per-function sections after the Overview already establishes it — minor over-explanation that could be trimmed, matching anchor 4 rather than anchor 5.

Actionability

Every util has a signature plus copy-paste-ready executable code with expected outputs (e.g. 'gsap.utils.clamp(0, 100, 150); // 100'), and distribute() gets a full config table with both tween and manual-call usage — fully executable guidance covering the common cases, matching anchor 5.

Workflow Clarity

This is a single-purpose utility reference with no multi-step process and no destructive or batch operations, so no validation checkpoints are needed and usage per function is unambiguous; however, guidance for choosing between overlapping utils (mapRange vs normalize, snap vs random's snapIncrement) is mostly implied rather than explicit, which is the minor gap of anchor 4.

Progressive Disclosure

Sections are well-organized with clear headers and clearly signaled one-level-deep links to official gsap.com docs (no nested references), but ~280 lines of full API reference are inlined in SKILL.md where a split — overview and key patterns here, per-function details in a references/ file — would fit better, matching anchor 4's 'most content appropriately placed; minor organization gaps' rather than anchor 5's appropriate split.

Specificity

The description lists nine concrete API functions ("clamp, mapRange, normalize, interpolate, random, snap, toArray, wrap, pipe") rather than vague language, but omits roughly seven utils documented in the body (getUnit, unitize, splitColor, selector, distribute, shuffle, wrapYoyo), which is more than a minor gap, fitting anchor 4 ('lists several specific actions; minor gaps in coverage') better than anchor 5's 'comprehensive coverage' and well above anchor 3's '1-2 concrete actions'.

Completeness

It clearly answers both questions: what it does ("Official GSAP skill for gsap.utils — clamp, mapRange, normalize, interpolate, random, snap, toArray, wrap, pipe") and when to use it via an explicit "Use when the user asks about gsap.utils, clamp, mapRange, random, snap, toArray, wrap, or helper utilities in GSAP" clause with concrete trigger phrases — an exact match for anchor 5, mirroring the good_overall_example pattern.

Trigger Term Quality

Triggers like "gsap.utils", "clamp", "mapRange", "random", "snap", "toArray", "wrap" are exactly what a GSAP user would type, giving good keyword coverage, but a few natural terms are missing (e.g. 'GSAP utility functions', 'lerp', 'interpolation', 'shuffle'), which matches anchor 4 rather than anchor 5's comprehensive synonym-level coverage.

Distinctiveness Conflict Risk

"Official GSAP skill for gsap.utils" carves out a clear niche with mostly distinct triggers, but generic English trigger words like "clamp", "random", "wrap", and "snap" could fire for non-GSAP contexts (CSS clamp(), generic math), which is the minor overlap risk of anchor 4 rather than anchor 5's minimal conflict risk.