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 title and category label with no substantive content. It fails to describe what the skill actually does, provides no explicit trigger guidance for when Claude should select it, and repeats the same trigger term twice without covering natural user language variations. It would be nearly indistinguishable from other API development skills in a large skill library.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates GraphQL schema definitions including types, queries, mutations, subscriptions, and input types from data models or requirements.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a GraphQL schema, define SDL types, set up a GraphQL API, or generate .graphql files.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'GraphQL types', 'schema definition language', 'SDL', 'GraphQL API schema', 'resolvers', 'typeDefs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('GraphQL Schema Generator' and 'API Development') but lists no concrete actions like 'generate types', 'define resolvers', 'create queries and mutations', etc. It is essentially a title repeated with no substantive capability description. | 1 / 3 |
Completeness | The 'what' is extremely weak (just a name, no actions described) and the 'when' is missing entirely—there is no 'Use when...' clause or equivalent explicit trigger guidance. Both components are essentially absent. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'graphql schema generator' repeated twice. It misses natural variations users would say such as 'GraphQL types', 'schema definition', 'SDL', 'GraphQL API', 'mutations', 'queries', '.graphql files', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'GraphQL' and 'schema generator' provides some domain specificity that distinguishes it from generic coding skills, but the lack of concrete actions and the broad 'API Development' category label could cause overlap with other API-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 shell with no actual instructional content. It repeatedly describes itself in vague, abstract terms without providing any GraphQL schema examples, SDL syntax, best practices, type definitions, or executable code. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable GraphQL SDL examples showing type definitions, queries, mutations, and subscriptions (e.g., a complete User type with resolvers).
Include a clear workflow for schema design: define types → add relationships → validate with a tool like graphql-inspector → iterate on errors.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content like naming conventions, pagination patterns (Relay connections), error handling patterns, and authentication directive examples.
Add references to supplementary files for advanced topics (e.g., 'See FEDERATION.md for schema federation patterns', 'See AUTH_DIRECTIVES.md for authorization patterns').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea—that this skill helps with 'graphql schema generator'—without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no schema snippets, no commands, no specific patterns. The content describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but includes none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive block with no meaningful structure. There are no references to detailed files, no layered organization, and the sections are superficial headers over redundant content. | 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.