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.
96
93%
Does it follow best practices?
Impact
100%
1.44xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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, uses natural trigger terms that users would actually say, explicitly states both what the skill does and when to use it, and carves out a distinct niche in the GraphQL domain 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 terms users would say: 'GraphQL APIs', 'query APIs', 'REST' (for migration context), 'real-time subscriptions', 'Apollo', 'Graphene'. Good coverage of domain-specific vocabulary. | 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 skills. | 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 executable code examples without unnecessary explanation. The main weakness is the lack of a clear workflow sequence showing how to build and validate a GraphQL API step-by-step. There's also a duplicate 'Best Practices' section that should be consolidated.
Suggestions
Add a numbered workflow section showing the sequence: 1. Define schema → 2. Implement resolvers → 3. Add DataLoader → 4. Test queries → 5. Deploy, with validation checkpoints
Consolidate the duplicate 'Best Practices' sections into a single comprehensive list
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section delivers actionable information 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 real imports and proper syntax. | 3 / 3 |
Workflow Clarity | While individual components are clear, there's no explicit workflow sequence for building a GraphQL API from scratch. Missing validation checkpoints for schema design or testing steps before deployment. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections for different concerns. Appropriately references external file for Python Graphene implementation with clear description of what it contains. One-level-deep reference is properly signaled. | 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.
90d6bd7
Table of Contents
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.