How do I install the GRAPHQL skill?

Run npx skillmds@latest add majiayu000/graphql-7 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is GRAPHQL safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with GRAPHQL?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is GRAPHQL free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published GRAPHQL?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

GRAPHQL by majiayu000 — Agent Skill

Name: GRAPHQL
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

GRAPHQL

Provides GraphQL API schema design and implementation expertise. Ensures proper type definitions, query/mutation patterns, pagination strategies, and error handling standards. Specializes in schema-first design, resolver implementation, DataLoader for N+1 prevention, subscription patterns, and federation architecture. Implements Relay cursor connections and Apollo best practices. Use when: designing GraphQL schemas, defining types and interfaces, implementing queries and mutations, creating resolvers, designing pagination with connections and edges, solving N+1 query problems with DataLoader, implementing subscriptions for real-time updates, handling errors and nullability, setting up GraphQL federation, or integrating with Apollo Server/Client or other GraphQL libraries.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

GraphQL API Standards

Naming Conventions

Field Naming

Boolean: Require is/has/can prefix
Date: Require ~At suffix
Use consistent terminology throughout the project (unify on either "create" or "add")

Date Format

ISO 8601 UTC
Use DateTime type

Pagination

Relay Connection Specification

type UserConnection {
  edges: [UserEdge!]!
  pageInfo: PageInfo!
}

type UserEdge {
  node: User!
  cursor: String!
}

type PageInfo {
  hasNextPage: Boolean!
  endCursor: String
}

Parameters: first, after

Sorting

orderBy: [{ field: "createdAt", order: DESC }]

Type Naming

Input: {Verb}{Type}Input
Connection: {Type}Connection
Edge: {Type}Edge

Input

Separate creation and modification (required for creation, optional for modification)
Avoid nesting - IDs only

Errors

extensions (default)

code, field in errors[].extensions

Union (type safety)

User | ValidationError

N+1

DataLoader is mandatory

Documentation

"""description""" is required
Explicitly state Input constraints

Deprecation

@deprecated(reason: "...")
Never delete types

---name: graphql-7description: Provides GraphQL API schema design and implementation expertise. Ensures proper type definitions, query/mutation patterns, pagination strategies, and error handling standards. Specializes in schema-first design, resolver implementation, DataLoader for N+1 prevention, subscription patterns, and federation architecture. Implements Relay cursor connections and Apollo best practices. Use when: designing GraphQL schemas, defining types and interfaces, implementing queries and mutations, creating resolvers, designing pagination with connections and edges, solving N+1 query problems with DataLoader, implementing subscriptions for real-time updates, handling errors and nullability, setting up GraphQL federation, or integrating with Apollo Server/Client or other GraphQL libraries.--- # GraphQL API Standards ## Naming Conventions ### Field Naming - Boolean: Require `is/has/can` prefix - Date: Require `~At` suffix - Use consistent terminology throughout the project (unify on either "create" or "add") ## Date Format - ISO 8601 UTC - Use DateTime type ## Pagination ### Relay Connection Specification ```graphql type UserConnection { edges: [UserEdge!]! pageInfo: PageInfo! } type UserEdge { node: User! cursor: String! } type PageInfo { hasNextPage: Boolean! endCursor: String } ``` - Parameters: `first`, `after` ## Sorting - `orderBy: [{ field: "createdAt", order: DESC }]` ## Type Naming - Input: `{Verb}{Type}Input` - Connection: `{Type}Connection` - Edge: `{Type}Edge` ## Input - Separate creation and modification (required for creation, optional for modification) - Avoid nesting - IDs only ## Errors ### extensions (default) - `code`, `field` in `errors[].extensions` ### Union (type safety) - `User | ValidationError` ## N+1 - DataLoader is mandatory ## Documentation - `"""description"""` is required - Explicitly state Input constraints ## Deprecation - `@deprecated(reason: "...")` - Never delete types

Frequently asked questions