data-client-graphql-setup

Set up @data-client/graphql for GraphQL APIs. Configures GQLEndpoint with auth and custom options. Use after data-client-setup detects GraphQL patterns.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/data-client-graphql-setup/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with complete, copy-paste-ready code across the common GraphQL setup cases and is largely token-efficient. Its main weaknesses are the absence of explicit validation/verification checkpoints in the setup workflow and a broken local reference (auth.md is a stub pointing to a non-existent target).

Suggestions

Add an explicit verification step after configuration (e.g. run a sample query against the endpoint and confirm a response) so the workflow has a validation checkpoint.

Fix or remove the references/auth.md link — either replace the stub with real auth-pattern content or point it at a working file, since it currently resolves to a missing target.

Tighten the opening paragraph to avoid restating the frontmatter description verbatim.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code examples with tight prose and no over-explanation of GraphQL or library basics, but the opening paragraph restates the frontmatter description and a few connective lines could be trimmed, fitting 'efficient; minor instances of over-explanation' rather than the every-token-earns-its-place 5 anchor.	4 / 5
Actionability	It provides copy-paste-ready, executable TypeScript and shell commands covering the common cases (install, basic/auth/async-auth/error-handling endpoint config, query, mutation, collection, component usage), matching 'fully executable; specific examples cover the common cases'.	5 / 5
Workflow Clarity	Sections imply a logical install → configure → define → use sequence, but there are no explicit numbered steps or validation/verification checkpoints (e.g. 'verify the endpoint responds', 'test a query'), matching 'sequence present but checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	Sections are clearly headed and the References block signals one-level-deep links, but the local reference [Authentication Guide](references/auth.md) resolves to a stub file containing only a relative path string ('../../../../docs/graphql/auth.md') with no actual auth content and a missing target, so navigation fails for that path — worse than the 'minor organization gaps' expected at 4.	3 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill does and gives an explicit (if skill-conditioned) usage trigger, with a well-scoped niche. It is held back by only 1-2 concrete actions, somewhat technical keyword choice, and a 'when' clause that lacks natural user-facing trigger phrases.

Suggestions

Add 1-2 more concrete actions to the description (e.g. 'defines queries and mutations') to lift specificity toward the 'several specific actions' anchor.

Reframe the 'when' clause with natural user-facing triggers (e.g. 'Use when the user needs to connect a GraphQL API to data-client') rather than only conditioning on another skill.

Include more natural synonyms users would say (e.g. 'GraphQL queries', 'GraphQL mutations', 'GraphQL schema') alongside the technical 'GQLEndpoint' term.

Dimension	Reasoning	Score
Specificity	Names the domain (@data-client/graphql for GraphQL APIs) and 1-2 concrete actions ("Set up", "Configures GQLEndpoint with auth and custom options"), but does not enumerate several specific actions, so it sits at the anchor for domain + 1-2 actions rather than the 'several specific actions' level above.	3 / 5
Completeness	Both 'what' (set up @data-client/graphql, configure GQLEndpoint with auth/custom options) and 'when' ("Use after data-client-setup detects GraphQL patterns") are explicitly stated, but the 'when' is conditioned on another skill rather than giving concrete user-facing trigger phrases, so it does not reach the 5 anchor.	4 / 5
Trigger Term Quality	Relevant keywords are present ("GraphQL APIs", "auth", "GraphQL patterns") but coverage is incomplete — "GQLEndpoint" is technical jargon and common natural terms (queries, mutations, schema) are missing, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	It targets a clear niche (@data-client/graphql) and is sequenced relative to sibling skills, but the fairly generic "GraphQL" trigger carries minor overlap risk with other GraphQL or data-client-* skills, fitting 'mostly distinct; minor overlap risk' better than the minimal-conflict 5 anchor.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: reactive/data-client
Path: .cursor/skills/data-client-graphql-setup/SKILL.md
Commit: ef4653f

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.