Conciseness

The body is dense with library-specific, non-obvious knowledge — pk routing via 'argsKey'/'nestKey', 'nonFilterArgumentKeys' matching semantics, exact normalize/denormalize method orders — with no padding and no explanation of concepts Claude already knows. Every bullet carries data-client-specific behavior, so each token earns its place rather than merely being 'mostly efficient'.

Actionability

Mostly concrete and executable — complete snippets for 'new Query(TodoResource.getList.schema, entries => ...)', Collection 'argsKey/nestKey' options, and 'new Collection([Todo], { nonFilterArgumentKeys: /orderBy|sortDir/ })', plus exact API signatures like 'shouldReorder(existingMeta, incomingMeta, existing, incoming)'. However, the Union example elides fields with '/* ... */' and references an undefined 'EventType', leaving minor gaps versus fully copy-paste-ready code.

Workflow Clarity

The sequences that exist are explicitly ordered ('process() → pk() → validate() → visit nested schemas → ... mergeWithStore()') and problem→solution mappings are concrete ('Older data arriving after newer... override shouldReorder(existingMeta, incomingMeta, existing, incoming)'). As a reference skill it has no end-to-end workflow needing validation checkpoints (none of its operations are destructive/batch), and section 6 defers entirely to partial-entities.md, so it sits at 'clear sequence, minor gaps' rather than the full error-recovery structure of a 5.

Progressive Disclosure

The body is a clear overview with well-labeled one-level-deep references — e.g. '[new Collection([Schema])](references/Collection.md) - mutable/growable lists' — and all 20 referenced files exist in references/. Reference files link only to siblings in the same directory (no 2+ level nesting), content is appropriately split between overview, practices, and reference files, and the Vue variant convention ('read `<name>.vue.md` instead of `<name>.md` when it exists') makes navigation across the 40-file bundle easy.

Specificity

Names the domain and concrete actions — 'Model the app's data with @data-client schemas, which normalize responses into one shared cache so an update shows everywhere' — and enumerates covered constructs ('Entity, GQLEntity, Collection, Union and Query'). It exceeds the 1-2 actions of a 3 but describes essentially one capability with its mechanism rather than the multiple distinct actions of a 5.

Completeness

Explicitly answers both what ('Model the app's data with @data-client schemas, which normalize responses into one shared cache so an update shows everywhere') and when ('Use it whenever an endpoint returning data is added or its response changes... when deriving views from loaded data, or when one item looks different in two places') with multiple concrete trigger phrases, matching the 5 anchor.

Trigger Term Quality

Includes genuinely natural trigger phrases users would say — 'an endpoint returning data is added', 'its response changes', 'when one item looks different in two places' — alongside library keywords ('resource, RestEndpoint, GraphQL, Endpoint'). Coverage is good but misses common synonyms such as 'add a resource' or 'type the response', falling short of the comprehensive synonym coverage of a 5.

Distinctiveness Conflict Risk

Tightly scoped to '@data-client schemas' with library-specific triggers (RestEndpoint, GQLEntity, normalization into a shared cache), giving it a clear niche with minimal conflict risk against generic data-fetching or state-management skills.