Conciseness

Almost entirely executable code with minimal framing prose; no explanations of concepts Claude already knows. Not a 5 because the three inline endpoint variants (basic, sync auth, async auth) plus an 18-line custom error-handling class overlap somewhat with each other and with references/auth.md, and could be condensed. Not a 3 because there is no real padding or unnecessary explanation anywhere.

Actionability

Fully executable, copy-paste-ready guidance throughout: install commands for npm/yarn/pnpm, complete TypeScript endpoint files, query/mutation/collection definitions with real schemas, and a working component example. Covers the common cases (auth, token refresh, error handling, list/push patterns).

Workflow Clarity

Sections form a clear logical sequence (install → detect existing patterns → configure endpoint → define queries/mutations → usage → next steps) and the Detection Checklist provides a checkpoint, plus explicit Next Steps linking follow-on skills. Not a 5 because there is no verification step (e.g., running a test query to confirm the endpoint config works). Not a 3 because the sequence and checkpoints are present and coherent.

Progressive Disclosure

Well-organized sections with a clearly signaled one-level-deep reference (references/auth.md exists and is linked in the References section) plus external docs links. Not a 5 because advanced material (custom fetchResponse error handling) is inlined rather than split out, and only one bundle reference exists to absorb the deeper auth/error content. Not a 3 because the structure and navigation are genuinely good and the referenced file is real and relevant.

Specificity

Names concrete actions — 'Set up @data-client/graphql', 'Configures GQLEndpoint with auth and custom options' — targeting a specific package and class with several specific configuration actions. Not a 5 because coverage stops at endpoint configuration; defining queries/mutations and component usage are absent. Not a 3 because it goes beyond 1-2 generic actions by naming the exact class and both auth and custom options.

Completeness

Answers both explicitly: what — 'Set up @data-client/graphql... Configures GQLEndpoint with auth and custom options'; when — 'Use after data-client-setup detects GraphQL patterns'. Not a 5 because the 'when' is chained to another skill's detection rather than direct user trigger phrases (e.g., 'Use when the project calls a GraphQL endpoint'), so it could be more explicit about user-facing triggers. Not a 3 because the when clause is explicit, not merely implied.

Trigger Term Quality

Good keyword coverage: 'GraphQL', 'GraphQL APIs', 'GQLEndpoint', 'auth', and the prerequisite skill name 'data-client-setup' — terms a user setting up a GraphQL data layer would naturally use. Not a 5 because common variations like 'queries', 'mutations', 'schema', or 'GraphQL client' are missing. Not a 3 because it covers multiple relevant natural keywords rather than a single generic one.

Distinctiveness Conflict Risk

Scopes tightly to the @data-client/graphql package and GQLEndpoint, with a sequencing condition that distinguishes it from the broader data-client-setup skill. Not a 5 because generic 'GraphQL' triggers could overlap with closely related sibling skills (e.g., a REST endpoint setup or schema-definition skill in the same family). Not a 3 because the package name and explicit prerequisite make it mostly distinct.