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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill graphql-implementation95
Does it follow best practices?
Agent success when using this skill
Validation for skill structure
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 excels across all dimensions. It provides specific capabilities (schema design, resolvers, error handling, performance optimization), names concrete frameworks (Apollo, Graphene), and includes an explicit 'Use when...' clause with natural trigger scenarios. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'schema design, resolvers, error handling, and performance optimization' along with specific frameworks 'Apollo or Graphene'. This provides clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Builds GraphQL APIs with schema design, resolvers, error handling, and performance optimization') AND when ('Use when creating flexible query APIs, migrating from REST, or implementing real-time subscriptions') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'GraphQL', 'APIs', 'schema', 'resolvers', 'REST', 'subscriptions', 'Apollo', 'Graphene'. Good coverage of both technical terms and use-case language like 'migrating from REST'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GraphQL with distinct triggers like 'GraphQL', 'Apollo', 'Graphene', 'subscriptions'. Unlikely to conflict with general API or REST skills due to specific technology focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent actionability and conciseness - it provides complete, executable code examples without unnecessary explanation. The main weakness is the lack of workflow sequencing; the content reads more like a reference document than a step-by-step guide for building a GraphQL API. There's also a duplicated 'Best Practices' section that should be consolidated.
Suggestions
Add a brief workflow section at the top outlining the sequence: 1) Define schema, 2) Set up server, 3) Implement resolvers, 4) Add DataLoader, 5) Test queries
Include a validation step showing how to test the GraphQL API works (e.g., a sample query and expected response)
Consolidate the two 'Best Practices' sections into one to avoid duplication
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, jumping directly into executable schema definitions and code examples without explaining what GraphQL is or how it works. Every section provides actionable content without padding. | 3 / 3 |
Actionability | Provides fully executable code examples including complete GraphQL schema, Apollo Server setup, DataLoader implementation, and error handling patterns. All code is copy-paste ready with real-world patterns. | 3 / 3 |
Workflow Clarity | Content presents components (schema, server, DataLoader, errors) but lacks explicit sequencing for building a GraphQL API. No validation checkpoints or feedback loops for testing the implementation works correctly. | 2 / 3 |
Progressive Disclosure | Main file provides a complete JavaScript/Apollo overview with clear reference to Python Graphene in a separate file. The reference is one level deep and clearly signals what additional content is available. | 3 / 3 |
Total | 11 / 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.
- 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.