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

69

Quality

86%

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

72%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 content is well-organized with strong progressive disclosure and lean conciseness, but it trades inline executable code and mid-process validation checkpoints for a high-level instruction list. Adding a few inline runnable snippets and explicit verify-before-proceeding steps would raise actionability and workflow clarity.

Suggestions

Add one or two inline executable code snippets (e.g., a minimal Apollo Server + resolver setup) so the body is copy-paste ready instead of deferring all code to examples.md.

Insert explicit validation checkpoints between build steps (e.g., "Validate the schema compiles before implementing resolvers") and a validate-fix-retry loop for the test step.

Trim the inline Error Handling table since the same material lives in references/errors.md, keeping the body to a brief pointer.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what GraphQL is or how libraries work — with dense, specific instruction steps; minor duplication between the error table and errors.md keeps it just at efficient rather than padded.

3 / 3

Actionability

Guidance is concrete and specific (named libraries, directive syntax, complexity limits, graphql-ws), but the body contains no inline executable code — all copy-paste examples live in references/examples.md, leaving it at "concrete guidance but incomplete" rather than copy-paste ready.

2 / 3

Workflow Clarity

The nine steps are clearly sequenced, but the multi-step build process has no explicit validation checkpoints or validate-fix-retry feedback loops between steps; checkpoints are missing or implicit.

2 / 3

Progressive Disclosure

The body is a concise overview pointing to three well-signaled, one-level-deep, real references (implementation.md, errors.md, examples.md) with content appropriately split and easy navigation.

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

The description is specific, complete, and well-triggered: it names concrete capabilities and gives explicit natural-language trigger phrases for both what and when. It is a strong, low-conflict description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Build production-ready GraphQL servers with schema design, resolvers, and subscriptions" — naming specific deliverables rather than vague language.

3 / 3

Completeness

Explicitly answers both what (build GraphQL servers with schema/resolvers/subscriptions) and when ("Use when building GraphQL APIs" plus a "Trigger with phrases like" clause).

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would say — "build GraphQL API", "create GraphQL server", "setup GraphQL" — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

GraphQL server building is a clear, distinct niche with GraphQL-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.