CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

graphql-implementation

Builds GraphQL APIs with schema design, resolvers, error handling, and performance optimization using Apollo or Graphene. Use when creating flexible query APIs, migrating from REST, or implementing real-time subscriptions.

66

Quality

83%

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

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

The body delivers lean, largely executable code examples for schema design, resolvers, batching, and errors, with a well-signaled one-level-deep reference for the Python path. Its main weaknesses are a duplicated 'Best Practices' section and the absence of a sequenced workflow with validation checkpoints.

Suggestions

Remove the first '## Best Practices' section (lines 93-99); it duplicates the later Do/Don't version nearly verbatim.

Frame the sections as a sequence (define schema -> implement resolvers -> add DataLoader batching -> add error handling) so the implementation workflow is explicit rather than a topical pattern list.

Complete the Apollo setup example by defining or pointing to typeDefs and actually using the imported startStandaloneServer so the snippet is copy-paste runnable.

DimensionReasoningScore

Conciseness

Mostly lean, code-first sections with no over-explanation of concepts Claude already knows, but the first '## Best Practices' section (lines 93-99) is fully redundant with the later Do/Don't version — a minor padding instance that keeps it below the 5 anchor.

4 / 5

Actionability

Mostly executable guidance (complete GraphQL schema, resolvers, DataLoader, GraphQLError usage), but the Apollo snippet references an undefined typeDefs and imports startStandaloneServer without using it — minor gaps versus copy-paste-ready code.

4 / 5

Workflow Clarity

Content is organized as topical patterns rather than a sequenced process (e.g., schema -> resolvers -> validation -> optimization), with no validation checkpoints and a duplicated section that hurts coherence; fits the 'sequence present but checkpoints missing' anchor.

3 / 5

Progressive Disclosure

Good structure: references/python-graphene.md exists, is one level deep, and is clearly signaled with its contents enumerated. Minor organization gaps from the duplicate 'Best Practices' section keep it below 5.

4 / 5

Total

15

/

20

Passed

Description

88%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 that clearly states what the skill does and when to use it, using third-person voice and concrete trigger phrases. Keyword coverage is good though not exhaustive, and the generic phrase 'creating flexible query APIs' introduces slight overlap risk with general API skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'schema design, resolvers, error handling, and performance optimization' — with comprehensive coverage of the GraphQL API-building domain; no meaningful gaps to place it at the 4 anchor.

5 / 5

Completeness

Explicitly answers both what ('Builds GraphQL APIs with schema design, resolvers, error handling, and performance optimization using Apollo or Graphene') and when ('Use when creating flexible query APIs, migrating from REST, or implementing real-time subscriptions') with concrete trigger phrases. Third-person voice; no penalty applies.

5 / 5

Trigger Term Quality

Good natural keyword coverage including 'GraphQL APIs', 'Apollo', 'Graphene', 'migrating from REST', and 'real-time subscriptions', but a few common user phrasings (e.g., 'schema', 'queries') are missing, placing it between the 3 and 5 anchors.

4 / 5

Distinctiveness Conflict Risk

Clear GraphQL niche with named tools (Apollo, Graphene) and distinct triggers, but 'creating flexible query APIs' is broad enough to create minor overlap with generic API-building skills.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

secondsky/claude-skills

Path

plugins/graphql-implementation/skills/graphql-implementation/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.