CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

Quality

81%

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

78%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.

A well-structured, information-dense skill body: a clear 9-step workflow with concrete values and directives, a defined output tree, and clean one-level-deep references that all resolve. The only meaningful gap is the absence of explicit validation feedback loops in the workflow and executable code living only in the references rather than the body.

DimensionReasoningScore

Conciseness

The body is dense and assumes GraphQL knowledge (no 'what is GraphQL' padding, e.g., steps like 'Implement resolvers... using DataLoader to batch and deduplicate database queries' state specifics without tutorials); minor trims are possible in the 5-item Prerequisites (optional items like 'recommended' codegen, Redis) and the Resources links, keeping it below anchor 5.

4 / 5

Actionability

Concrete, instruction-level guidance throughout with exact specifics — '@auth(requires: ADMIN)', '@constraint(minLength: 1, maxLength: 255)', 'maximum depth of 7, maximum complexity score of 1000', 'graphql-ws protocol', 'executeOperation' — and a defined output tree; no inline executable code in the body itself, so it stops short of the copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Nine clearly sequenced steps from schema design through testing, with type generation (step 8) and integration/WebSocket tests (step 9) acting as end-stage checkpoints; there are no explicit validate-then-proceed feedback loops (e.g., 'run tests before finalizing'), which keeps it below anchor 5 and above the 'checkpoints missing' anchor 3.

4 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled, one-level-deep references ('See references/implementation.md for the full implementation guide', errors, examples) that all exist as real files, with the inline error table kept appropriately concise — matching the anchor-5 structure exactly.

5 / 5

Total

17

/

20

Passed

Description

78%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.

A strong description with an explicit 'Use when' clause, concrete trigger phrases, and a distinct GraphQL-server niche. Its main weakness is that the 'what' enumerates only three feature areas, underselling the authorization, validation, and query-protection capabilities the body actually covers.

Suggestions

Expand the opening 'what' sentence to name two more concrete capabilities the skill provides (e.g., 'field-level authorization and query complexity limiting'), bringing specificity closer to anchor 4-5.

Add one or two more natural trigger variations such as 'add a GraphQL endpoint' or 'Apollo/Strawberry server' to tighten trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('production-ready GraphQL servers') and three concrete components ('schema design, resolvers, and subscriptions'), but these are feature areas under one build verb and omit capabilities the body covers (authorization, input validation, complexity limiting, testing), so gaps exceed the 'minor gaps' of anchor 4.

3 / 5

Completeness

Explicitly answers both what ("Build production-ready GraphQL servers with schema design, resolvers, and subscriptions") and when ("Use when building GraphQL APIs with schemas and resolvers") plus concrete trigger phrases, matching the anchor-5 example structure; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "build GraphQL API", "create GraphQL server", "setup GraphQL" — with build/create/setup synonyms, but misses a few natural variations such as 'add a GraphQL endpoint' or framework names like Apollo, so it falls short of comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear GraphQL-server niche with distinct, specific triggers; minor overlap risk remains with generic API-building or GraphQL-client skills, keeping it just below anchor 5's 'minimal conflict risk'.

4 / 5

Total

16

/

20

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.

Validation — 14 / 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/tons-of-skills-marketplace

Path

plugins/api-development/graphql-server-builder/skills/building-graphql-server/SKILL.md

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.