CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/graphql-yoga-tests

Tests a GraphQL Yoga server (the-guild.dev runtime) with `yoga.fetch()` for in-process, no-network request simulation of queries and mutations, `@graphql-tools/executor-http` for subscription and incremental-delivery (streaming) tests, auth-header pass-through, and production-config gates for disabled introspection and persisted operations. Use to test a GraphQL Yoga server, write Yoga query, mutation, or subscription tests, or check its production plugin config; for a different runtime harness use apollo-server-tests, mercurius-tests, or hasura-tests instead, not this skill.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, actionable body with executable examples, a validated worked example, and clean one-level-deep reference structure. The only weakness is mild verbosity in prose prefaces and restated explanations.

Suggestions

Drop the repeated 'Per Yoga docs:' / 'Per Yoga docs' preface lines — citing the URL once in the References section is enough and removes redundant tokens.

Tighten the Overview: the two paragraphs restating yoga.fetch's no-network behavior and the Apollo comparison overlap with the 'The URL … is a placeholder' note under Basic test; consolidate to a single concise statement.

Trim the 'Parsing results' section — the response-shape JSON and masked-error note are useful, but the lead-in sentence repeats what the Basic test example already demonstrates.

DimensionReasoningScore

Conciseness

Mostly efficient with copy-paste-ready code and no padding with concepts Claude already knows, but it could be tightened — 'Per Yoga docs:' prefaces repeat three times and the Overview/placeholder prose restates the no-network point already made above.

2 / 3

Actionability

Fully executable throughout: install command, complete TypeScript test snippets, CI YAML, and an anti-pattern table with concrete fixes — copy-paste ready and matching the score-3 anchor.

3 / 3

Workflow Clarity

The Worked example is a clearly numbered sequence (steps 1–4) with explicit assertion checkpoints (assert errors present, assert data.me.id returned, assert error message matches /introspection/i) forming a validation feedback loop.

3 / 3

Progressive Disclosure

A concise overview points to a single well-signaled one-level-deep bundle file ([references/production-config-tests.md]) for the production-config detail, with content appropriately split and a clear References section.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete capabilities, provides an explicit use-trigger, and actively disambiguates from sibling runtime skills. It hits every dimension at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'in-process, no-network request simulation of queries and mutations', 'subscription and incremental-delivery (streaming) tests', 'auth-header pass-through', 'production-config gates for disabled introspection and persisted operations' — matching the score-3 anchor.

3 / 3

Completeness

Clearly answers both 'what' (Tests a GraphQL Yoga server with the listed mechanisms) and 'when' via an explicit 'Use to test a GraphQL Yoga server…' trigger clause.

3 / 3

Trigger Term Quality

Natural user phrasing is well covered — 'test a GraphQL Yoga server', 'write Yoga query, mutation, or subscription tests', 'check its production plugin config' — covering the common variations a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (GraphQL Yoga server) and explicitly disambiguates — 'for a different runtime harness use apollo-server-tests, mercurius-tests, or hasura-tests instead, not this skill' — making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents