graphql-implementation
tessl i github:secondsky/claude-skills --skill graphql-implementationBuilds 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Implementation
88%This is a well-structured GraphQL skill with excellent actionability and conciseness. The code examples are complete and executable, covering schema design, resolvers, N+1 prevention, and error handling. The main weakness is the lack of workflow sequencing - it reads more like a reference than a step-by-step guide, and the 'Best Practices' section is duplicated.
Suggestions
Add a brief workflow section showing the sequence: 1) Define schema, 2) Implement resolvers, 3) Add DataLoader, 4) Test queries - with validation steps
Remove the duplicate 'Best Practices' section (appears twice at the end)
Add a validation step showing how to test the GraphQL API (e.g., sample query and expected response)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, jumping directly into 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 for schema definition, Apollo Server setup, DataLoader implementation, and error handling. All code is copy-paste ready with proper imports and realistic patterns. | 3 / 3 |
Workflow Clarity | Content presents components but lacks explicit sequencing for building a GraphQL API. No validation checkpoints or feedback loops for testing the schema or resolvers. The sections are organized topically rather than as a workflow. | 2 / 3 |
Progressive Disclosure | Main content provides a clear overview with executable examples, and appropriately references the Python Graphene implementation in a separate file with a clear description of what it contains. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities with named frameworks, includes natural trigger terms developers would use, explicitly states both what it does and when to use it, and carves out a distinct niche in the GraphQL space that won't conflict with other API-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'schema design, resolvers, error handling, and performance optimization' with specific frameworks 'Apollo or Graphene'. 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'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'GraphQL', 'APIs', 'query APIs', 'REST', 'real-time subscriptions', 'Apollo', 'Graphene'. Good coverage of terms developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GraphQL with distinct triggers like 'GraphQL', 'Apollo', 'Graphene', 'subscriptions', and 'migrating from REST'. Unlikely to conflict with general API or REST-focused skills. | 3 / 3 |
Total | 12 / 12 Passed |
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.