CtrlK
BlogDocsLog inGet started
Tessl Logo

graphql-schema

GraphQL queries, mutations, and code generation patterns. Use when creating GraphQL operations, working with Apollo Client, or generating types.

73

Quality

90%

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%Weight 40%Scale 1-3

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

The body is highly actionable and token-efficient, with concrete code and clear step sequencing for queries and mutations. The main gaps are the absence of an explicit validation/verification checkpoint after codegen and the lack of progressive disclosure into separate reference files for its several distinct topics.

Suggestions

Add an explicit validation step after "npm run gql:typegen" (e.g., confirm the .generated.ts file exists and re-run on error) to turn each workflow into a validate-and-retry loop.

Move deeper material such as fetch-policy details, optimistic-update guidance, and fragments into separate reference files (e.g., REFERENCE.md) linked from the main sections to apply progressive disclosure.

Add a brief note on how to verify a generated hook works (e.g., import resolves, types are present) so the multi-step workflows have a concrete success check.

DimensionReasoningScore

Conciseness

The body is lean and efficient: it avoids explaining what GraphQL or Apollo is and jumps straight to rules, file structure, and executable code, with every section earning its tokens.

3 / 3

Actionability

It provides fully executable, copy-paste-ready code (real .gql files, "npm run gql:typegen", complete React hook usage) plus concrete WRONG/CORRECT anti-pattern comparisons and specific commands.

3 / 3

Workflow Clarity

Query and mutation creation are sequenced as Step 1/2/3, but there is no explicit validation checkpoint (e.g., confirm the .generated file was produced or handle codegen failure) after running codegen.

2 / 3

Progressive Disclosure

The document is a single self-contained ~290-line file with no bundle files; while well-organized by section, several topics (fragments, optimistic updates, fetch policies) that could live in separate reference files are kept inline.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A concise, third-person description that names concrete capabilities and pairs them with explicit "Use when" triggers covering natural user phrasing. It is specific, complete, and clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

"GraphQL queries, mutations, and code generation patterns" lists multiple specific concrete actions (queries, mutations, code generation) rather than vague language.

3 / 3

Completeness

It clearly states what the skill does (queries, mutations, code generation patterns) and provides an explicit "Use when..." trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

"Use when creating GraphQL operations, working with Apollo Client, or generating types" gives good coverage of natural terms a user would say, including the named Apollo Client library.

3 / 3

Distinctiveness Conflict Risk

The GraphQL + Apollo Client + codegen niche has distinct triggers and is unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
ChrisWiles/claude-code-showcase
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.