graphql-mutation-builder
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill graphql-mutation-builderGraphql Mutation Builder - Auto-activating skill for API Development. Triggers on: graphql mutation builder, graphql mutation builder 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 no substantive content. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The duplicate trigger term suggests auto-generated content that was never properly customized.
Suggestions
Add specific actions the skill performs, e.g., 'Generates GraphQL mutations from schema definitions, creates input types, validates mutation syntax, and scaffolds resolver functions.'
Add a 'Use when...' clause with natural trigger terms like 'Use when creating GraphQL mutations, writing mutation resolvers, defining input types for APIs, or working with .graphql files.'
Include file type triggers and common user phrases like 'mutation', 'GraphQL API', 'schema mutation', '.graphql', 'gql' to improve discoverability.
| 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 provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 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 mutation', 'GraphQL API', 'mutation query', 'gql mutation', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'GraphQL mutation' is somewhat specific to a niche domain, the lack of detail about what specifically this skill does (vs general GraphQL skills or query builders) creates potential overlap with other API development skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actionable content. It describes what a GraphQL mutation builder skill would do without providing any actual guidance, code examples, mutation patterns, or concrete instructions. The entire content could be replaced with a single sentence and lose nothing of value.
Suggestions
Add executable GraphQL mutation examples showing common patterns (create, update, delete) with proper syntax and variable handling
Include concrete code snippets for mutation builders in at least one language/framework (e.g., Apollo Client, graphql-request)
Provide a clear workflow for constructing mutations: define input types, write mutation, handle response/errors
Remove the generic 'Capabilities' and 'Example Triggers' sections and replace with actual mutation-building guidance
| 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 doesn't need. | 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 mutation syntax. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger conditions and vague capabilities without any actual procedure for building GraphQL mutations. | 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 there's no substantive content. | 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.