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 placeholder with no substantive content. It only states the skill name and category without explaining what the skill actually does or providing meaningful trigger terms. The duplicate trigger term suggests auto-generated content that was never properly filled in.
Suggestions
Add specific capabilities: describe what the skill does (e.g., 'Generates GraphQL mutations from schema definitions, creates input types, handles nested object mutations, validates mutation syntax').
Add a proper 'Use when...' clause with natural trigger terms like 'create mutation', 'write GraphQL mutation', 'mutation syntax', 'API mutation', 'gql mutation'.
Include file types or contexts that would trigger this skill (e.g., '.graphql files', 'schema.graphql', 'when modifying GraphQL API endpoints').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Graphql Mutation Builder') without describing any concrete actions. There are no specific capabilities listed like 'generates mutations', 'validates schemas', or 'creates input types'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a duplicate of the skill name rather than meaningful trigger guidance. No explicit 'Use when...' clause exists. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('graphql mutation builder, graphql mutation builder'). Missing natural variations users would say like 'create graphql mutation', 'write mutation', 'API mutation', 'gql mutation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'GraphQL mutation' is somewhat specific to a niche, the lack of detail about what specifically this skill does (vs general GraphQL skills or query builders) creates potential overlap with other API or GraphQL-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 an empty template that provides zero actionable content about GraphQL mutations. It consists entirely of meta-descriptions about what the skill supposedly does without any actual implementation guidance, code examples, mutation syntax, or best practices. The content would be completely unhelpful for building GraphQL mutations.
Suggestions
Add executable GraphQL mutation examples showing proper syntax (e.g., `mutation CreateUser($input: CreateUserInput!) { createUser(input: $input) { id name } }`)
Include concrete patterns for common mutation scenarios: create, update, delete, batch operations, with input types and response handling
Provide a clear workflow for building mutations: define input types, write mutation, handle errors, validate responses
Add specific guidance on mutation best practices: naming conventions, input validation, error handling patterns, optimistic updates
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about GraphQL mutations. 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 examples are provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, mutation syntax, or implementation details. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger conditions and vague capabilities without any actual sequence of actions for building GraphQL mutations. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no structure pointing to detailed materials. There are no references to examples, schemas, or advanced topics - just repetitive trigger descriptions. | 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
b8a3b3e
- 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.