CtrlK
BlogDocsLog inGet started
Tessl Logo

building-graphql-server

Build production-ready GraphQL servers with schema design, resolvers, and subscriptions. Use when building GraphQL APIs with schemas and resolvers. Trigger with phrases like "build GraphQL API", "create GraphQL server", or "setup GraphQL".

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

Well-structured and token-efficient with good progressive disclosure to real reference files. The main gaps are the lack of executable code in the body and missing validation feedback loops in the workflow.

Suggestions

Add a short executable SDL or resolver code snippet in the body so the core steps are copy-paste ready rather than only described.

Insert an explicit validation checkpoint (e.g. introspect/schema-validate the SDL, then fix and re-validate) into the workflow for schema design and resolver implementation.

Add a validate→fix→retry feedback loop around the integration-test step (step 9) to make error recovery explicit.

DimensionReasoningScore

Conciseness

The body is lean and assumes GraphQL competence — it names libraries and concrete parameters (depth 7, complexity 1000) without explaining basic concepts, so every token earns its place.

3 / 3

Actionability

Steps give specific library and parameter guidance, but the SKILL.md body contains no executable code or copy-paste commands — code lives in referenced files, leaving the main instructions descriptive rather than executable.

2 / 3

Workflow Clarity

A clear 9-step sequence is present, but for complex/batch operations like schema design and authorization there are no explicit validation checkpoints or validate→fix→retry feedback loops in the main flow.

2 / 3

Progressive Disclosure

A concise overview points to one-level-deep, well-signaled references (implementation.md, errors.md, examples.md), all of which are real bundle files, with content appropriately split.

3 / 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.

A strong, specific description with explicit what-and-when guidance and clear triggers. Its only weakness is trigger-term breadth, relying on a narrow set of phrasings.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'schema design, resolvers, and subscriptions' — naming specific capabilities rather than vague abstractions.

3 / 3

Completeness

It answers both 'what' (build production-ready GraphQL servers with schema design, resolvers, subscriptions) and 'when' via an explicit 'Use when building GraphQL APIs...' clause plus trigger phrases.

3 / 3

Trigger Term Quality

It offers relevant natural phrases ('build GraphQL API', 'create GraphQL server', 'setup GraphQL') but coverage is narrow, missing common variations like 'GraphQL endpoints', 'GraphQL subscriptions', or 'GraphQL schema'.

2 / 3

Distinctiveness Conflict Risk

The GraphQL-server niche is clearly defined with distinct triggers ('build GraphQL API', 'create GraphQL server'), making conflict with other skills unlikely.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.