graphql-operations
Guide for writing GraphQL operations (queries, mutations, fragments) following best practices. Use this skill when: (1) writing GraphQL queries or mutations, (2) organizing operations with fragments, (3) optimizing data fetching patterns, (4) setting up type generation or linting, (5) reviewing operations for efficiency.
Install
With your agent
Install OMGSkills skill "apollographql/skills:graphql-operations" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/apollographql/skills /tmp/skills && ln -s /tmp/skills/skills/graphql-operations ~/.claude/skills/graphql-operations
From README
GraphQL Operations Guide This guide covers best practices for writing GraphQL operations (queries, mutations, subscriptions) as a client developer. Well-written operations are efficient, type-safe, and maintainable. Start From the Schema Write every operation against the project's schema, not against the examples in this guide. Find the schema before you write anything. Check the schema entry in codegen.ts, graphql.config., or apollo.config., then look for .graphql SDL files. Use only the fields, arguments, and enum values that the schema defines. Field names in this guide, such as updatedAt or orderBy: { field: CREATEDAT, direction: DESC }, are illustrations. Save the operation as a document next to the client's existing operations. Leave the server schema unchanged unless the user asks for a schema change.
