graphql-resolver-creator
Graphql Resolver Creator - Auto-activating skill for API Development. Triggers on: graphql resolver creator, graphql resolver creator Part of the API Development skill category.
35
Quality
3%
Does it follow best practices?
Impact
92%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/graphql-resolver-creator/SKILL.mdQuality
Discovery
7%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 very weak skill description that appears to be auto-generated boilerplate. It provides no actual information about what the skill does, repeats the same trigger term twice, and lacks any 'Use when...' guidance. The description would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates GraphQL resolver functions for queries, mutations, and subscriptions. Creates type-safe resolvers with proper error handling and data source integration.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks to create resolvers, implement GraphQL endpoints, connect schema to data sources, or mentions resolver functions.'
Include natural keyword variations users would say: 'graphql', 'resolver', 'query resolver', 'mutation resolver', 'schema implementation', 'graphql backend', 'apollo server'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Graphql Resolver Creator') without describing any concrete actions. There are no specific capabilities listed like 'generates resolver functions', 'handles query/mutation resolvers', or 'creates type-safe resolvers'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or explicit trigger guidance. Both the what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('graphql resolver creator, graphql resolver creator'). Missing natural variations users would say like 'resolver', 'graphql api', 'schema resolver', 'mutation handler', or 'query resolver'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'GraphQL Resolver' is somewhat specific to a particular domain, which provides some distinctiveness. However, the generic 'API Development' category and lack of specific triggers could cause overlap with other GraphQL or API-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder template with no actual instructional content. It describes what a GraphQL resolver creator skill would do but provides zero concrete guidance, code examples, or actionable steps for creating resolvers. The entire content could be replaced with a single sentence without losing information.
Suggestions
Add executable code examples showing how to create GraphQL resolvers (e.g., with Apollo Server, graphql-js, or similar frameworks)
Include a concrete workflow: define schema -> create resolver functions -> wire up to data sources -> test queries
Provide specific resolver patterns: query resolvers, mutation resolvers, field resolvers, with actual code snippets
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual resolver implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about GraphQL resolvers. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or resolver code. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger conditions and capabilities without any actual sequence of actions for creating GraphQL resolvers. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, examples, or related documentation. There's nothing to progressively disclose because no substantive content exists. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.