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
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 description is a boilerplate template with no substantive content beyond the skill name and category. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. It would perform very poorly in a multi-skill selection scenario.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates GraphQL resolver functions, scaffolds query and mutation handlers, creates data source connections, and maps schema types to database models.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create GraphQL resolvers, write query/mutation handlers, set up a GraphQL API, or scaffold resolver boilerplate for a schema.'
Replace the duplicated trigger term with diverse natural keywords users would say, such as 'GraphQL', 'resolver', 'mutation', 'query handler', 'schema implementation', 'type resolver', 'Apollo', 'graphql-tools'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Graphql Resolver Creator') and its category ('API Development') but lists no concrete actions like 'generates resolver functions', 'creates schema mappings', or 'scaffolds query/mutation handlers'. It is entirely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the name, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just a duplicate of the skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('graphql resolver creator, graphql resolver creator'). It misses natural user phrases like 'GraphQL', 'resolver', 'mutation handler', 'query resolver', 'schema', 'API endpoint', or 'type definitions' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'GraphQL resolver' does narrow the domain somewhat compared to a fully generic description, but the lack of specific actions or file types means it could overlap with other GraphQL or API development skills without clear differentiation. | 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 an empty template with no actual content about GraphQL resolver creation. It consists entirely of generic boilerplate that repeats the skill name without providing any technical guidance, code examples, patterns, or actionable instructions. It would provide zero value to Claude when attempting to help users create GraphQL resolvers.
Suggestions
Add concrete, executable code examples showing how to create GraphQL resolvers (e.g., with Apollo Server, graphql-yoga, or similar frameworks) including type definitions and resolver functions.
Define a clear workflow for resolver creation: schema definition → resolver implementation → testing → validation, with specific commands and validation steps.
Include specific patterns and best practices such as DataLoader for N+1 prevention, error handling in resolvers, authentication/authorization middleware, and pagination patterns.
Remove all boilerplate meta-descriptions ('This skill provides automated assistance...') and replace with actual technical content that teaches resolver creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'graphql resolver creator' excessively, and provides zero actual technical content about creating GraphQL resolvers. | 1 / 3 |
Actionability | There is no concrete code, no executable examples, no specific commands, and no actual guidance on how to create GraphQL resolvers. The content is entirely abstract meta-description with no actionable instructions. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no validation checkpoints or any process description whatsoever. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no code examples to organize, and no meaningful structure beyond boilerplate headings that contain no real content. | 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
4dee593
- 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.