CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is a tight, highly actionable reference dominated by executable code across the full setup flow. Its weaknesses are the absence of any validation/verification checkpoint in the workflow and a broken bundle reference (dangling auth.md symlink).

Suggestions

Add a validation checkpoint after GQLEndpoint configuration — e.g. run a sample query and confirm a successful response before proceeding — to give the workflow an explicit verify-then-fix feedback loop.

Fix the references/auth.md symlink (or inline the auth content) so the 'Authentication Guide' reference resolves to a real file instead of the missing ../../../../docs/graphql/auth.md target.

Bump the Detection Checklist from passive 'look for' items to a confirm step (e.g. 'verify the detected URL and auth scheme against the working endpoint') so the multi-step setup has a concrete checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and almost entirely executable code with minimal framing prose, assuming Claude's competence without explaining what GraphQL or the libraries are. The only mild redundancy is the parallel npm/yarn/pnpm blocks, which is practical rather than padded, so it stays above the 'mostly efficient but could be tightened' anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript/TSX with specific file paths (src/api/gql.ts) covering config, auth, async auth, error handling, queries, mutations, collections, and component usage — matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Steps are sequenced (install → configure → detect → define → use → next steps) but there are no validation or verification checkpoints — e.g. the Detection Checklist says to scan for patterns with no confirm-the-endpoint-works step, matching the 'sequence present but checkpoints missing or implicit' anchor rather than the validated workflow at level 3.

2 / 3

Progressive Disclosure

Sections are well organized and references are clearly signaled one level deep, but the only bundle reference — [Authentication Guide](references/auth.md) — is a dangling symlink whose target (../../../../docs/graphql/auth.md) does not exist, so navigation to the referenced detail is broken. Good structure with a non-functional reference lands at level 2 rather than the working multi-file navigation of level 3.

2 / 3

Total

10

/

12

Passed

Description

85%

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 is concise, third-person, and clearly states both capabilities and an explicit activation trigger tied to a sibling skill. Its main weakness is trigger-term breadth, covering GraphQL only narrowly without common query/mutation phrasings.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — 'Set up @data-client/graphql', 'Configures GQLEndpoint with auth and custom options' — matching the anchor for enumerating several specific actions rather than naming only a domain and a couple actions.

3 / 3

Completeness

Explicitly answers both what ('Set up @data-client/graphql... Configures GQLEndpoint with auth and custom options') and when ('Use after data-client-setup detects GraphQL patterns'), an explicit trigger clause that satisfies the 'Use when...' requirement rather than capping at 2.

3 / 3

Trigger Term Quality

Contains relevant natural terms ('GraphQL APIs', 'GraphQL patterns') a user might say, but coverage is thin — missing common variations like 'GraphQL queries/mutations', 'GQL', or '.graphql'. It is not jargon-only (level 1) but does not reach the broad coverage of level 3.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — @data-client/graphql setup gated on data-client-setup detecting GraphQL patterns — with triggers unlikely to fire for non-GraphQL skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
reactive/data-client
Reviewed

Table of Contents

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.