graphql-schema-generator
Graphql Schema Generator - Auto-activating skill for API Development. Triggers on: graphql schema generator, graphql schema generator 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-schema-generator/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 minimal useful content. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The repeated trigger term and boilerplate category mention provide almost no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates GraphQL schemas from data models, creates type definitions, defines queries and mutations, validates schema syntax'
Include a 'Use when...' clause with natural trigger terms: 'Use when creating GraphQL APIs, defining SDL schemas, working with .graphql files, or designing type systems'
Add variations of terms users might say: 'GraphQL types', 'schema definition language', 'SDL', 'resolvers', 'GraphQL API design'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('GraphQL Schema Generator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of generating schemas, defining types, creating resolvers, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and the 'when' is only implied through generic trigger phrases. There is no explicit 'Use when...' clause or meaningful guidance on when to select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'graphql schema generator' repeated twice. Missing natural variations users might say like 'GraphQL types', 'schema definition', 'SDL', 'GraphQL API', 'define schema', or file extensions like '.graphql'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'GraphQL' provides some specificity that distinguishes it from general API skills, the vague 'API Development' category and lack of specific triggers could cause overlap with other API-related skills. The GraphQL focus provides moderate distinctiveness. | 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 essentially an empty template with no actual content about GraphQL schema generation. It repeats the phrase 'graphql schema generator' multiple times without providing any executable code, SDL examples, type definitions, or concrete guidance. The skill fails on all dimensions by describing capabilities rather than providing them.
Suggestions
Add concrete GraphQL SDL examples showing type definitions, queries, mutations, and subscriptions with copy-paste ready code
Include a step-by-step workflow for generating schemas from existing data sources or designing schemas from requirements
Provide specific patterns for common GraphQL schema scenarios (pagination, authentication, relationships, error handling)
Remove all generic boilerplate text and replace with actionable, GraphQL-specific guidance
| 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 no actual GraphQL schema content. | 1 / 3 |
Actionability | There is zero concrete guidance - no GraphQL schema examples, no SDL syntax, no code snippets, no specific commands. The skill describes what it claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps for generating a GraphQL schema, no validation checkpoints, and no process to follow. The 'Capabilities' section lists vague promises without any sequence. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no useful organization. It mentions 'Related Skills' but provides no actual references to detailed documentation, examples, or advanced topics. | 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.