Apollo Client

What it does

The document separates client-rendered applications from streaming and server-rendered framework integrations. It covers queries, mutations, normalized caching and local reactive state. This matters because a working browser-only example can still leak cache state or produce hydration problems when transplanted into a server-rendered application.

Best for

React teams choosing an Apollo Client integration or investigating inconsistent cached GraphQL results.

Tradeoffs and requirements

The reviewed source targets a specific client generation. Imports, suspense behavior and framework adapters must match installed versions. Cache configuration cannot repair an incorrect authorization boundary or an operation that requests unnecessary sensitive fields.

React 18+, React 19 (Suspense/RSC). Works with Next.js, Vite, CRA, and other React frameworks.

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/apollo-client --skill apollo-client

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:*) Bash(node:*) 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

Supporting-file static inspection

Bounded source inspection, not a runtime security audit. This inspection does not execute code.

0 text files inspected at this exact repository snapshot. 13 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.

Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.

Suggested workflow

Identify the framework and rendering mode, select its integration reference and define one representative operation. Configure cache identity and request context deliberately, then add mutation updates only after the initial loading and error states behave correctly.

How to judge the result

Test initial rendering, navigation, failed requests and mutation results, including a fresh session and a different authenticated identity. Inspect actual network requests and cache contents; a rendered success message does not prove that stale or cross-user data is impossible.