Apollo Router

What it does

The document organizes configuration around version selection, environment and required features. It covers headers, CORS, authentication, traffic limits and telemetry, with additional version-dependent capabilities. This is useful when examples from different Router releases look similar but rely on incompatible configuration schemas.

Best for

GraphQL operators configuring a federated Router or migrating configuration between supported release generations.

Tradeoffs and requirements

Configuration validity is narrower than correct authorization or operational behavior. Features may depend on release or deployment entitlements. Credentials and forwarded headers need explicit handling, and enabling extra telemetry can disclose request information unless collection is deliberately scoped.

Linux/macOS/Windows. Requires a composed supergraph schema from Rover or GraphOS.

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-router --skill apollo-router

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.

• Network Access — review the source context.

Allowed tools declaration: Bash(router:*) Bash(./router:*) Bash(rover:*) Bash(curl:*) Bash(docker:*) 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

Determine the installed version and deployment target before choosing feature examples. Make a focused configuration change, preserve environment-specific secrets outside version control and validate the file with the matching Router tooling before routing development traffic through it.

How to judge the result

Check startup validation, allowed and denied origins, authentication failures and downstream timeouts. Verify that intended headers reach only the appropriate subgraphs, inspect telemetry for sensitive fields and retain the last working configuration for a controlled rollback.