agentsclimarketplace
Sign in

Graphql schema design

Skill shinzoxD/knackbox/skills/coding/graphql-schema-design

Design and review GraphQL schemas for authz, pagination, N+1 risk, nullability, and evolution. Use whenever the user works on GraphQL types, resolvers, connections, deprecations, query cost, or schema reviews — even when they only paste an SDL snippet.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill graphql-schema-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, 318 tokens by cl100k_base, as published. Nobody here has run it

GraphQL Schema Design

Schema is the product contract. Optimize for client clarity, server efficiency, and safe evolution.

Workflow

  1. Clarify clients, auth model, and write vs read paths.
  2. Model types and relationships; avoid leaking DB tables blindly.
  3. Specify nullability deliberately (every ! is a promise).
  4. Pagination: connections/cursors for lists that can grow.
  5. Authz: field and object level; never rely on "hidden" fields alone.
  6. Evolution: deprecations, additive changes, versioning policy.
  7. Performance: N+1, dataloader, query depth/cost limits.

Output format

## GraphQL design: <api>

### Type overview
…

### Queries / mutations
…

### Authz notes
…

### Pagination & errors
…

### Risks (N+1, breaking changes)
…

### Example operations

Rules

  1. Prefer additive evolution; mark breaking changes explicitly.
  2. Mutations should return clear payloads (errors, viewer, mutated entity).
  3. Do not put secrets in GraphQL types that any authorized client can query casually without field authz.
  4. Lists without bounds need pagination or hard limits.
  5. Document error handling conventions (union vs exceptions).
  6. If SDL is incomplete, state assumptions about resolvers.

Edge cases

  • Subscriptions: auth, fan-out cost, filtering.
  • Federation: ownership boundaries and shared types.
  • File uploads: not always native; call out alternatives.

What ships with it: 1 file

1.4 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.