graphql-mutation-builder
Graphql Mutation Builder - Auto-activating skill for API Development. Triggers on: graphql mutation builder, graphql mutation builder Part of the API Development skill category.
35
3%
Does it follow best practices?
Impact
94%
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-mutation-builder/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 essentially a title repeated as a trigger term with no substantive content. It fails to describe any concrete capabilities, provides no meaningful trigger terms beyond the skill name itself, and lacks any 'Use when...' guidance. It would be nearly indistinguishable from other API or GraphQL-related skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates GraphQL mutation operations, constructs input types and variables, handles nested object mutations, and builds mutation queries with proper argument structures.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to create, write, or debug GraphQL mutations, mutation resolvers, or when working with GraphQL APIs and mutation operations.'
Include natural keyword variations users might say, such as 'GraphQL', 'GQL', 'mutation query', 'write a mutation', 'API mutation', 'mutation resolver', 'mutation schema', '.graphql files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('GraphQL mutation builder') but describes no concrete actions. There are no specific capabilities listed like 'generates mutation queries', 'handles input types', or 'builds nested mutations'. It's essentially just a label. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant restatement of the skill name rather than explicit trigger guidance. There is no 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'graphql mutation builder' repeated twice. It misses natural variations users would say like 'GraphQL mutation', 'write a mutation', 'create mutation query', 'GQL', 'mutation schema', or 'API mutation'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'GraphQL mutation builder' is somewhat specific to a niche (GraphQL mutations vs queries vs schemas), but the lack of detail about what it actually does means it could overlap with a general GraphQL skill or API development skill. | 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/placeholder with no actual content about building GraphQL mutations. It contains no code, no examples, no concrete guidance, and no workflow—just repetitive meta-descriptions of what the skill claims to do. It provides zero value to Claude in performing GraphQL mutation tasks.
Suggestions
Add concrete, executable GraphQL mutation examples including schema definition, mutation type definition, resolver patterns, and input types (e.g., a createUser mutation with variables).
Include a clear workflow for building mutations: 1) Define input types, 2) Define mutation in schema, 3) Implement resolver, 4) Test with a sample query, with validation at each step.
Remove all the meta-content about triggers, capabilities, and 'when to use' sections—these waste tokens and provide no actionable guidance.
Add specific patterns and best practices such as error handling in mutations, optimistic responses, nested input objects, and return type conventions (e.g., returning the mutated object plus errors).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, code, or concrete details about GraphQL mutations. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero actionable content—no code examples, no mutation syntax, no schema patterns, no concrete commands. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The bullet 'Provides step-by-step guidance' is ironic given that no steps are actually present. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no meaningful structure, no references to detailed materials, and no navigation to deeper content. The sections exist but contain no real information to organize. | 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.