SKILLEMALL.ai
GitHub ↗ RU Sign in

BF graphql-ts-generator

Automatically generates TypeScript types from GraphQL schema files with CLI integration for developers and AI agents.

modbender/skill-library-mcp Agent Skills author: modbender MIT 9 files body ≈ 1 662 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Automatically generates TypeScript types from GraphQL schema files with CLI integration for developers and AI agents.

As a process F 43/100 · Will not run — References files that are not bundled: references/sample.graphql, references/test-schema.graphql, assets/README.md

IntegrationSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
F
43/100
Will not run
References files that are not bundled: references/sample.graphql, references/test-schema.graphql, assets/README.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/sample.graphql
  • warning missing-ref reference to a missing file: references/test-schema.graphql
  • warning missing-ref reference to a missing file: assets/README.md

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: references/sample.graphql, references/test-schema.graphql, assets/README.md
  • 0Tools and files. 3 referenced file(s) missing: references/sample.graphql, references/test-schema.graphql, assets/README.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (graphql-ts-generator) differs from the folder (neo-graphql-ts-generator)
  • 50When it triggers. No condition that starts the skill
  • 85Steps. 89 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Execution cost. Instruction body is 1662 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 117: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 29 headings
  • +3Step-by-step instructions: 89 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)
  • +3All 4 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.