building-graphql-server

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

54%

Overall

Validation — 81%

Implementation — 7%

Activation — 100%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

This skill has a fundamental mismatch between its stated purpose (GraphQL server building) and its actual content (generic REST API patterns). It lacks any GraphQL-specific guidance such as schema definition language, resolver implementation, subscription setup, or GraphQL-specific tooling. The content is generic boilerplate that provides no actionable value for building GraphQL servers.

Suggestions

Add concrete GraphQL schema examples using SDL (Schema Definition Language) with type definitions, queries, mutations, and subscriptions

Include executable resolver code examples showing how to connect schemas to data sources (e.g., with Apollo Server or graphql-yoga)

Replace REST-oriented output paths (routes, controllers) with GraphQL-appropriate structure (schema, resolvers, context, dataloaders)

Add validation steps specific to GraphQL such as schema linting, query complexity analysis, and resolver testing patterns

Dimension	Reasoning	Score
Conciseness	Contains significant padding and generic content that Claude already knows. The overview is boilerplate ('automated assistance for graphql server builder tasks'), prerequisites list obvious items, and the content doesn't provide GraphQL-specific value.	1 / 3
Actionability	No executable code examples for GraphQL schemas, resolvers, or subscriptions. Instructions are vague ('Generate boilerplate code', 'Implement endpoint handlers') without concrete GraphQL syntax, schema definitions, or resolver patterns.	1 / 3
Workflow Clarity	Steps are poorly organized with duplicate numbering (two separate lists both starting at 1), no validation checkpoints, and generic REST API steps that don't match the GraphQL focus. Missing feedback loops for schema validation or resolver testing.	1 / 3
Progressive Disclosure	References external files (implementation.md, errors.md, examples.md) which is appropriate structure, but the main content is too thin to serve as a useful overview. The skill title says GraphQL but outputs reference REST patterns (routes, controllers).	2 / 3
	Total	5 / 12 Passed

Activation

100%

This is a well-crafted skill description that clearly communicates specific capabilities (schema design, resolvers, subscriptions), provides explicit trigger guidance with natural user phrases, and occupies a distinct niche around GraphQL technology. The description follows best practices by using third person voice and including both 'Use when' and 'Trigger with' clauses.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Build production-ready GraphQL servers', 'schema design', 'resolvers', and 'subscriptions'. These are distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('Build production-ready GraphQL servers with schema design, resolvers, and subscriptions') and when ('Use when building GraphQL APIs...', 'Trigger with phrases like...'). Explicit trigger guidance is provided.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'build GraphQL API', 'create GraphQL server', 'setup GraphQL', plus technical terms like 'schemas', 'resolvers'. Good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	GraphQL is a specific technology with distinct terminology. The triggers are clearly scoped to GraphQL-specific work and unlikely to conflict with general API or database skills.	3 / 3
	Total	12 / 12 Passed

Reviewed

16 days ago

Table of Contents

Validation Implementation Activation

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.