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.
81
76%
Does it follow best practices?
Impact
Pending
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 strong skill description that clearly communicates what the skill does and when to use it. It includes specific actions, relevant frameworks, and natural trigger terms that cover common GraphQL use cases. The explicit 'Use when...' clause with concrete scenarios like REST migration and real-time subscriptions provides excellent trigger guidance.
| 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, and performance optimization using Apollo or Graphene') and when ('Use when creating flexible query APIs, migrating from REST, or implementing real-time subscriptions'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'GraphQL', 'API', 'schema design', 'resolvers', 'REST', 'real-time subscriptions', 'Apollo', 'Graphene', 'query APIs'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | GraphQL is a clear niche distinct from general API skills or REST API skills. The mention of specific frameworks (Apollo, Graphene) and GraphQL-specific concepts (resolvers, subscriptions, schema design) makes it highly distinguishable. | 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 schema design, resolvers, DataLoader, and error handling. However, it lacks a coherent workflow with validation steps, has a duplicated Best Practices section, and doesn't guide Claude through a sequenced process for building and verifying a GraphQL API.
Suggestions
Add a sequenced workflow (e.g., 1. Define schema → 2. Implement resolvers → 3. Add DataLoader → 4. Test with sample query → 5. Verify response) with explicit validation checkpoints like testing a query against the running server.
Remove the duplicate 'Best Practices' section and consolidate into a single concise list, trimming items Claude already knows like 'validate all inputs'.
Add a quick verification step showing how to test the API (e.g., a sample curl or GraphQL playground query with expected output) to close the feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete code examples, but has a duplicated 'Best Practices' section and some items that Claude would already know (e.g., 'Validate all inputs', 'Use descriptive naming conventions'). The Do/Don't list at the end largely repeats the earlier best practices section. | 2 / 3 |
Actionability | Provides fully executable code examples for schema definition, Apollo Server setup, DataLoader usage, and error handling. 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 one well-signaled reference to a separate file for Python Graphene, which is good. However, the main content is somewhat monolithic—the schema definition and Apollo setup could benefit from better organization, and there's no clear overview/quick-start section separating essential from advanced content. | 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
88da5ff
- 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.