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.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/graphql-implementation/skills/graphql-implementation/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly communicates specific capabilities, includes natural trigger terms, and explicitly states both what the skill does and when to use it. The mention of specific frameworks and GraphQL-specific terminology makes it highly distinctive and unlikely to conflict with other API-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: schema design, resolvers, error handling, performance optimization, and names specific frameworks (Apollo, Graphene). | 3 / 3 |
Completeness | Clearly answers both 'what' (builds GraphQL APIs with schema design, resolvers, error handling, performance optimization) and 'when' (creating flexible query APIs, migrating from REST, implementing real-time subscriptions) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'GraphQL', 'schema design', 'resolvers', 'Apollo', 'Graphene', 'REST', 'real-time subscriptions', 'query APIs'. These cover common variations of how users would describe GraphQL-related tasks. | 3 / 3 |
Distinctiveness Conflict Risk | GraphQL is a clear niche distinct from general API development or REST API skills. The mention of specific frameworks (Apollo, Graphene) and GraphQL-specific concepts (resolvers, subscriptions, schema design) makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, executable code examples for GraphQL implementation with Apollo Server, covering key patterns like DataLoader and error handling. However, it lacks a coherent workflow sequence for building a GraphQL API from scratch, has a duplicated Best Practices section, and references a bundle file that doesn't exist. The content reads more like a reference card than an actionable guide.
Suggestions
Add a clear numbered workflow (e.g., 1. Define schema → 2. Implement resolvers → 3. Add DataLoader → 4. Test queries → 5. Add error handling) with validation steps like testing a sample query.
Remove the duplicated 'Best Practices' section and consolidate into a single concise list.
Either provide the referenced `references/python-graphene.md` bundle file or remove the reference to avoid broken navigation.
Add a verification step showing how to test the API (e.g., a sample curl/GraphQL query and expected response) to validate the setup works.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but has a duplicated 'Best Practices' section and some redundancy (DataLoader mentioned in both code and best practices). The schema example is reasonably sized but could be trimmed since Claude knows GraphQL syntax. | 2 / 3 |
Actionability | Provides fully executable code examples for Apollo Server setup, DataLoader usage, error handling, and schema definition. The code is copy-paste ready with real imports and concrete patterns. | 3 / 3 |
Workflow Clarity | There is no clear sequenced workflow for building a GraphQL API. The sections are presented as isolated code snippets without a coherent step-by-step process, no validation checkpoints, and no guidance on how to verify the API works correctly after setup. | 1 / 3 |
Progressive Disclosure | There is a reference to a Python Graphene file which is good progressive disclosure, but the bundle files show no such file exists. The main content includes substantial inline code that could benefit from being split into reference files (e.g., schema patterns, error handling patterns). | 2 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
5e92b71
- 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.