graphql-resolver-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill graphql-resolver-creatorGraphql Resolver Creator - Auto-activating skill for API Development. Triggers on: graphql resolver creator, graphql resolver creator Part of the API Development skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with minimal useful content. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The duplicate trigger term suggests auto-generation without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Generates GraphQL resolver functions for queries, mutations, and subscriptions with proper type definitions and error handling'
Include a 'Use when...' clause with natural trigger terms like 'Use when creating GraphQL APIs, writing resolver functions, handling GraphQL queries/mutations, or setting up a GraphQL server'
Add relevant file types and frameworks as triggers, e.g., 'Apollo Server, type-graphql, .graphql files, schema resolvers'
| 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 guidance on when Claude should select this skill. 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 'create resolver', 'graphql api', 'resolver function', 'mutation handler', or 'query resolver'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'GraphQL resolver' is a specific enough domain that it wouldn't conflict with most skills, the lack of detail about what specifically it does (vs other GraphQL tools) and the generic 'API Development' category creates some overlap risk. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actual instructional content. It describes what a GraphQL resolver creator skill would do without providing any concrete guidance, code examples, or actionable steps. The entire content could be replaced with a single sentence: 'This skill helps with GraphQL resolvers' and convey the same (lack of) information.
Suggestions
Add concrete, executable resolver code examples showing common patterns (query resolvers, mutation resolvers, nested resolvers with DataLoader)
Include a clear workflow: 1) Define schema type, 2) Create resolver function, 3) Wire to schema, 4) Test with sample query
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific GraphQL resolver patterns and anti-patterns
Add references to related files for advanced topics like authentication in resolvers, N+1 query prevention, and error handling patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually create a GraphQL resolver - no schema examples, no resolver function patterns, no executable code. | 1 / 3 |
Workflow Clarity | No workflow is defined. The content mentions 'step-by-step guidance' but provides none. There are no steps, no sequence, and no validation checkpoints for creating resolvers. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no structure beyond generic headings. No references to detailed materials, no examples file, no API patterns documentation - just empty promises of capabilities. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.