graphql-engineering

v0.1.2

GraphQL-engineering team — agents (graphql-schema-architect, graphql-server-engineer, graphql-security-governance-engineer) for the three engines of a GraphQL surface: schema design & evolution (client-driven type modeling, nullability, Relay pagination, mutation/error shape, schema-first vs code-first, federation vs stitching, non-breaking evolution), server & resolvers (N+1/DataLoader batching + per-request caching, selection-set-aware fetching, subscriptions, APQ/response caching), and security & governance (query cost/depth budgets, field-level authz, persisted operations, introspection hardening, rate/batch limits, error hygiene). Ships skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 reference), best-practices, templates, commands. Engineering judgment, not a security certification; library/federation/spec-feature specifics are volatile — every version carries a retrieval date + [verify-at-use]; no PII. Requires ravenclaude-core@>=0.7.0.

Claude Code4 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes: Claude Code
Parsed components: 4 skill or MCP entries
Source updated: Sep 15, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install graphql-engineering for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install graphql-engineering@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/graphql-engineering/.

Plugin files

plugins/graphql-engineering/

├── .claude-plugin/plugin.json
├── skills/graphql-federation-and-composition/SKILL.md
├── skills/graphql-schema-design-and-evolution/SKILL.md
├── skills/graphql-security-and-governance/SKILL.md
└── skills/resolver-performance-and-n-plus-one/SKILL.md

Included Skills4

graphql-federation-and-compositionskills/graphql-federation-and-composition/SKILL.md

Decide whether to federate, keep a monolithic graph, or stitch — and if federating, design clean subgraph ownership boundaries with entity @key, reference resolvers, and @external/@requires/@provides, then weigh the real operational cost of running a gateway/router. Federation spec and directive specifics verify-at-use.

graphql-schema-design-and-evolutionskills/graphql-schema-design-and-evolution/SKILL.md

Design a GraphQL schema for the clients that consume it — not the database underneath: nullability discipline, Relay cursor-connection pagination, input/payload mutation shape, errors-as-data vs top-level errors — and evolve it without breaking clients via additive change, @deprecated, and staged field rollout. Spec/library specifics verify-at-use.

graphql-security-and-governanceskills/graphql-security-and-governance/SKILL.md

Defend a GraphQL endpoint whose single URL accepts arbitrary nested queries: depth limiting, cost/complexity budgets, field-level authorization (authorize at the field, not the endpoint), introspection hardening in prod, persisted/allow-listed operations, rate and batching limits, and error-message hygiene so internals never leak. Library/spec specifics verify-at-use.

resolver-performance-and-n-plus-oneskills/resolver-performance-and-n-plus-one/SKILL.md

Kill the N+1 problem GraphQL's per-field resolution invites: batch and per-request-cache with DataLoader, be selection-set aware so you fetch only requested fields, bound pagination cost, avoid over-fetching downstream, and layer response caching / APQ. Includes a worked N+1 example and its DataLoader fix. Library specifics verify-at-use.

Plugin manifests1

plugins/graphql-engineering/.claude-plugin/plugin.json

{
  "name": "graphql-engineering",
  "version": "0.1.2",
  "description": "GraphQL-engineering team — agents (graphql-schema-architect, graphql-server-engineer, graphql-security-governance-engineer) for the three engines of a GraphQL surface: schema design & evolution (client-driven type modeling, nullability, Relay pagination, mutation/error shape, schema-first vs code-first, federation vs stitching, non-breaking evolution), server & resolvers (N+1/DataLoader batching + per-request caching, selection-set-aware fetching, subscriptions, APQ/response caching), and security & governance (query cost/depth budgets, field-level authz, persisted operations, introspection hardening, rate/batch limits, error hygiene). Ships skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 reference), best-practices, templates, commands. Engineering judgment, not a security certification; library/federation/spec-feature specifics are volatile — every version carries a retrieval date + [verify-at-use]; no PII. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "graphql",
    "schema-design",
    "apollo-federation",
    "dataloader",
    "n-plus-one",
    "resolvers",
    "relay-pagination",
    "schema-evolution",
    "persisted-queries",
    "query-cost-analysis",
    "field-level-authorization",
    "graphql-security",
    "subgraph",
    "introspection-hardening",
    "graphql-subscriptions"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}