Skip to content
SkillModel-led1,018 tokens in use

GraphQL Architect

Designs GraphQL schemas and Apollo Federation 2.5 graphs, with DataLoader resolvers, real-time subscriptions and query depth and complexity limits.

12,471 stars on the repository MIT LicenseJeffallan/claude-skills · skills/graphql-architect
/plugin marketplace add jeffallan/claude-skills /plugin install fullstack-dev-skills@fullstack-dev-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing GraphQL Architect costs

37tokens idle
1,018tokens in use
19,219tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter15/15
  • Structure23/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity36
  • Momentum40

GraphQL Architect guides Claude through schema work in six steps: model the domain, design types with federation directives, validate composition, write resolvers with DataLoader, secure the graph and optimize it. Each step has a recovery note, for example what to check when composition fails or a complexity threshold is exceeded.

Six reference files cover schema design, resolvers, federation, subscriptions, security and a guide for migrating a REST API to GraphQL in phases.

What You Get

  • Schema SDL with types, interfaces, unions, enums and input types, documented and deprecated where needed
  • Federation subgraphs with entity keys and shared types, and a gateway configuration
  • Resolvers that batch lookups with DataLoader, with error handling and cursor pagination
  • Subscriptions over WebSocket with Redis pub/sub and filtering
  • Depth limits, complexity rules, rate limiting, field-level authorization and query allowlisting
  • A phased plan for moving a REST API to GraphQL

Common Use Cases

  • Designing a schema for a new product API
  • Splitting a monolithic graph into Apollo Federation subgraphs
  • Removing N+1 queries from resolvers with DataLoader
  • Adding live updates to a graph with subscriptions
  • Hardening a public GraphQL endpoint against expensive queries
  • Wrapping existing REST endpoints behind a GraphQL layer

What Makes It Unique

Most API skills treat GraphQL as one more transport. This one centers on federation: entity keys, shared value types, interface objects and query planning, with recovery steps when composition fails. It also pairs security with design, so depth and complexity limits and field-level authorization are part of the workflow, and it includes a migration guide that says when not to use GraphQL.

Under The Hood

The skill is a SKILL.md with six reference files and no scripts, and the references load by topic. The agent writes schema files, resolvers and server configuration, and the workflow asks it to check that the schema composes. The migration reference shows a wrapper that calls an existing REST API with fetch, and the examples read JWT secrets, Redis host settings and the environment mode from environment variables, verify tokens and hash passwords. The skill does not tell the agent to run shell commands or browse the web.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers