Conciseness

The body is dense and code-forward with essentially no explanation of concepts Claude already knows — no 'what is motion' padding, compact decision tables, and terse one-line principles. It is not a 5 because of verbatim duplication: the drag-to-dismiss sheet appears both standalone and again inside the end-to-end example, and the visibility-pause pattern is repeated nearly identically in both ShimmerSkeleton and PulseDot.

Actionability

Nearly every pattern ships as a complete, copy-paste-ready component with imports, 'use client', token/spring usage, and cleanup — e.g. 'export function BottomSheet', 'export function CursorFollower', 'export function LoadingButton' — covering the common cases named in the Outputs section. The few JSX fragments (draggable card, swipe detection) are idiomatic usage snippets rather than pseudocode, so this sits at anchor 5 rather than 4.

Workflow Clarity

Sequencing and routing are clear: 'Requires motion-foundations to be set up first', 'Use these when motion-patterns is not enough', a 'Choosing the right advanced API' decision table, and numbered Rules cross-referenced from an Anti-Patterns table with fixes. It is not 5 because there is no explicit multi-step workflow with validation checkpoints (acceptable for a non-destructive reference skill, but the anchor-5 feedback-loop structure is absent); not 3 because the ordering, prerequisites, and decision guidance present no real gaps.

Progressive Disclosure

The file has good section structure and no broken or nested references, but there are no bundle files at all — all 14+ full code examples plus an end-to-end example are inlined in a single ~590-line SKILL.md. Content that would fit one-level-deep reference files (loader components, text/SVG examples, the end-to-end sheet) is inline, matching the anchor-3 pattern of 'content that should be separate is inline' despite decent organization.

Specificity

The description lists multiple concrete, named capabilities — 'drag & drop, gestures, text animations, SVG path drawing, custom hooks, imperative sequences (useAnimate), loaders, and the full API decision tree' — comprehensively covering the skill's stated scope. It exceeds the anchor-4 example ('several specific actions; minor gaps') because no meaningful capability from the body is missing.

Completeness

It explicitly answers both questions: the 'what' is the concrete action list, and the 'when' is an explicit 'Use when building drag and drop, gestures, text or SVG animation...' clause with concrete trigger phrases. This matches the anchor-5 example structure exactly; the anchor-4 case ('when' could be more explicit) does not apply.

Trigger Term Quality

'Use when building drag and drop, gestures, text or SVG animation, or imperative animation sequences in React or Next.js' uses natural user phrasing with good coverage, matching the anchor-4 example in tone. It falls short of 5 because common synonyms users would actually say are absent — e.g. 'swipe', 'reorder', 'spinner', 'loading state', 'drag-to-dismiss'.

Distinctiveness Conflict Risk

The description carves a clear niche ('Advanced motion patterns... drag & drop, gestures, SVG path drawing') with distinct triggers and declares the dependency 'Requires motion-foundations'. It is not a 5 because the phrase 'animation in React or Next.js' overlaps with the sibling 'motion-patterns' skill (referenced only in the body, not the description), leaving minor conflict risk between the family members.