Graphql Operations

What it does

This source focuses on client operations rather than server implementation. It covers queries, mutations, subscriptions, fragment organization and generated types. Its useful discipline is starting from the real schema and selecting the data needed by the consuming view instead of copying broad field selections across files.

Best for

Application developers reviewing GraphQL documents, reducing overfetching or organizing operations alongside components.

Tradeoffs and requirements

A syntactically valid operation can still be expensive or unauthorized. Fragment reuse does not automatically reduce server work, and mutation retries need care because the underlying operation may not be idempotent. Generated types reflect the schema version used during generation.

Any GraphQL client (Apollo Client, urql, Relay, etc.)

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/apollographql/skills/tree/9dda1397730370aeb8df4ff8f2015c34c86b5003/skills/graphql-operations --skill graphql-operations

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

85/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

38/100

38

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Inspect the relevant schema and client conventions, name each operation and place dynamic input in variables. Share stable fragment selections where they clarify ownership, then define expected loading, partial data and error behavior in the consuming component.

How to judge the result

Validate documents against the current schema, regenerate types and test representative variable combinations. Inspect actual response size and resolver cost where available, include null and error cases and check that a mutation updates the intended client state without duplicating effects.