Conciseness

The body is lean — nearly every section is executable code with terse annotations and no padding of concepts Claude already knows. Minor trims remain: the 'stale-while-revalidate HTTP cache invalidation strategy' explainer and the time-sensitive version pin '(latest: 2.4.1)', which is penalized outside a deprecated/old-patterns section. This fits anchor 4 ('efficient; minor instances that could be trimmed'), not anchor 5.

Actionability

Every section provides fully executable, copy-paste-ready code: 'npm install swr', useSWR, useSWRMutation, useSWRInfinite, SWRConfig, optimistic-update options, conditional keys, onErrorRetry, and useSWRSubscription — covering the common cases exactly as the anchor-5 example requires. Not below 5: no pseudocode, no missing imports, no gaps in the main usage paths.

Workflow Clarity

This is a reference-style skill with no multi-step pipeline and no destructive or batch operations, so no validation checkpoints are required; sections are well-ordered from installation through core API, configuration, strategies, and advanced hooks, ending with 'Key Rules'. It fits anchor 4 ('clear, well-organized guidance') rather than anchor 5, whose sequence-with-explicit-validation pattern describes a multi-step workflow this skill does not have.

Progressive Disclosure

A single-file skill with no bundle files; content is organized under clear section headers with no buried or nested references, and the ~172-line body (mostly code) is a reasonable size to keep inline. It matches anchor 4 ('good structure; most content appropriately placed') rather than anchor 5, since some advanced sections (useSWRSubscription, error retry) could be split into separate reference files.

Specificity

The description enumerates seven concrete capability areas ('client-side data fetching, caching, revalidation, mutations, optimistic UI, pagination, or infinite loading'), matching the 'lists several specific actions; minor gaps' anchor. It falls short of anchor 5 because the 'what' is framed as 'expert guidance' rather than naming the concrete actions the skill performs.

Completeness

Both halves are present: an explicit trigger clause ('Use when building React apps with... using the SWR library') and a 'what' ('SWR data-fetching expert guidance'). It sits below anchor 5 because the 'what' is slightly generic ('expert guidance') compared to the concrete-action pattern in the anchor-5 example.

Trigger Term Quality

Good keyword coverage with natural user terms: 'SWR', 'React apps', 'data fetching', 'caching', 'revalidation', 'mutations', 'optimistic UI', 'pagination', 'infinite loading'. Missing a few natural synonyms such as 'stale-while-revalidate' or 'useSWR', so it fits anchor 4 rather than the comprehensive anchor 5.

Distinctiveness Conflict Risk

The description is firmly anchored to 'the SWR library', giving it a clear niche with distinct triggers (anchor 4). Minor overlap risk remains with generic React data-fetching or TanStack Query skills through shared terms like 'data fetching' and 'caching'.