Conciseness

The body is lean and assumes competence — no padding about what GSAP or easing is, and each util gets a compact signature line plus minimal runnable examples. It stops short of anchor 5 because of minor trim opportunities: the clamp example is duplicated (Overview lines 22–29 and its own section lines 37–43), and the "Omit value to get a function" pattern is re-demonstrated in nearly every section after being fully established once. It is well above anchor 3 since there is no genuinely unnecessary explanation.

Actionability

Every util ships copy-paste-ready JavaScript with expected outputs in comments (e.g. `gsap.utils.clamp(0, 100, 150); // 100`, `gsap.utils.snap(10, 23); // 20`), plus integration patterns like the tween string form `x: "random(-100, 100, 5)"` and a complete distribute() config table with both tween and manual usage. This matches the anchor for fully executable examples covering the common cases; nothing is pseudocode.

Workflow Clarity

This is a single-purpose reference skill with no multi-step process, and the single action — pick the right util and apply its documented pattern — is unambiguous: categories are cleanly grouped (Clamping/Ranges, Random/Snap, Units/Parsing, Arrays/Collections), the one tricky convention (omitting the value for the function form, with the explicit "Exception: random()" callout) is stated up front, and 'Best practices'/'Do Not' sections give clear do/don't guidance. No destructive or batch operations exist that would require validation checkpoints, so the anchor-5 simple-skill condition is met; anchor 4 would demand validation gaps that do not apply here.

Progressive Disclosure

Structure is good: clear section headers per category, a well-labeled config table for distribute(), and clearly signaled external references for deeper material ("See [distribute()](https://gsap.com/docs/...) for more", "See [splitColor()]...", and a 'Learn More' link). This fits the anchor for good structure with most content appropriately placed. It does not reach anchor 5 because the full per-util API reference (~275 lines) is inlined in SKILL.md with no bundle split — plausible for 16 small utils, but a leaner overview with the detailed reference in a separate file is the stronger pattern; it is above anchor 3 because organization and signaling are genuinely good, not merely present.

Specificity

The description lists multiple concrete capabilities — "clamp, mapRange, normalize, interpolate, random, snap, toArray, wrap, pipe" — covering the headline utils of the domain, with "helper utilities" as a catch-all. This matches the anchor-5 pattern of enumerating specific, concrete capabilities with comprehensive coverage; there is no vague fluff, and it is not a fit for anchor 4 ('minor gaps') since nine concrete utils plus the domain catch-all go beyond partial enumeration.

Completeness

Both parts are explicit: the 'what' is "Official GSAP skill for gsap.utils — clamp, mapRange, normalize, interpolate, random, snap, toArray, wrap, pipe" and the 'when' is "Use when the user asks about gsap.utils, clamp, ... or helper utilities in GSAP". This mirrors the anchor-5 example (clear what plus an explicit 'Use when...' clause with concrete trigger phrases); anchor 4 would require the 'when' to be less explicit, which it is not.

Trigger Term Quality

The trigger clause "Use when the user asks about gsap.utils, clamp, mapRange, random, snap, toArray, wrap, or helper utilities in GSAP" contains good, natural keyword coverage including the dotted API name and a plain-language synonym ("helper utilities"). It falls short of anchor 5 because several natural terms users would say are absent from the trigger list (e.g. "normalize", "interpolate", "shuffle", "lerp"); it is above anchor 3 because coverage is solid rather than merely 'some relevant keywords'.

Distinctiveness Conflict Risk

The niche is clearly scoped by "gsap.utils" and "helper utilities in GSAP", making conflict with non-GSAP skills unlikely and matching the mostly-distinct anchor. It does not reach anchor 5 because the bare generic words in the trigger list ("clamp", "random", "snap", "wrap") could fire on non-GSAP mentions; it is above anchor 3 because the domain anchoring is explicit rather than merely 'somewhat specific'.