Agent skill · Backend & API

apollo-router

Version-aware guide for configuring and running Apollo Router for federated GraphQL supergraphs. Generates correct YAML for both Router v1.x and v2.x. Use this skill when: (1) setting up Apollo Router to run a supergraph, (2) configuring routing, headers, or CORS, (3) implementing custom plugins (Rhai scripts or coprocessors), (4) configuring telemetry (tracing, metrics, logging), (5) troubleshooting Router performance or connectivity issues.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill apollo-router --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Version: 2.2.1
Declared author: apollographql
Allowed tools: Bash(router:*)Bash(./router:*)Bash(rover:*)Bash(curl:*)Bash(docker:*)ReadWriteEditGlobGrep
Requires: Linux/macOS/Windows. Requires a composed supergraph schema from Rover or GraphOS.
Path: skills/api/apollo-router/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Apollo Router Config Generator Apollo Router is a high-performance graph router written in Rust for running Apollo Federation 2 supergraphs. It sits in front of your subgraphs and handles query planning, execution, and response composition. **This skill generates version-correct configuration.** Router v1 and v2 have incompatible config schemas in several critical sections (CORS, JWT auth, connectors). Always determine the target version before generating any config. ## Step 1: Version Selection Ask the user **before generating any config**: ``` Which Apollo Router version are you targeting? [1] Router v2.x (recommended — current LTS, required for Connectors) [2] Router v1.x (legacy — end-of-support announced, security patches only) [3] Not sure — help me decide ``` If the user picks **[3]**, display: ``` Quick guide: • Pick v2 if: you're starting fresh, using Apollo Connectors for REST APIs, or want backpressure-based overload protection. • Pick v1 if: you have an existing deployment and haven't migrated yet. Note: Apollo ended active support for v1.x. The v2.10 LTS (Dec 2025) is the current baseline. Migration is strongly recommended. Tip: If you have an existing router.yaml, y

What's inside
Steps it walks through
  1. Step 1: Version Selection
  2. Step 2: Environment Selection
  3. Step 3: Feature Selection
  4. Step 4: Gather Parameters
  5. CORS
  6. JWT Authentication
  7. Connectors (v2 only)
  8. Operation Limits
  9. Telemetry
  10. Traffic Shaping
  11. Step 5: Generate Config
  12. Step 6: Validate
  13. Required Validation Gate (always run)
  14. Step 7: Conditional Next Steps Handoff
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the apollo-router skill do?

Version-aware guide for configuring and running Apollo Router for federated GraphQL supergraphs. Generates correct YAML for both Router v1.x and v2.x. Use this skill when: (1) setting up Apollo Router to run a supergraph, (2) configuring routing, headers, or CORS, (3) implementing custom plugins (Rhai scripts or coprocessors), (4) configuring telemetry (tracing, metrics, logging), (5) troubleshooting Router performance or connectivity issues.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill apollo-router --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going