rover
Guide for using Apollo Rover CLI to manage GraphQL schemas and federation. Use this skill when: (1) publishing or fetching subgraph/graph schemas, (2) composing supergraph schemas locally or via GraphOS, (3) running local supergraph development with rover dev, (4) validating schemas with check and lint commands, (5) configuring Rover authentication and environment, (6) exploring or searching a graph's schema for agent-driven discovery (rover schema describe / rover schema search), (7) initializing a new graph project or MCP server with rover init, (8) working with Apollo Connectors, contracts, persisted queries, or client operations, (9) managing API keys, plugins, templates, or graph artifacts.
Install
With your agent
Install OMGSkills skill "apollographql/skills:rover" 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/rover ~/.claude/skills/rover
From README
Apollo Rover CLI Guide Rover is the official CLI for Apollo GraphOS. It helps you manage schemas, run composition locally, publish to GraphOS, and develop supergraphs on your local machine. Step 1: Step 2: Authenticate Step 3: Verify Step 4: Initialize a Project (optional) Explore a Graph's Schema (start here for schema questions) To answer "what's in this graph?", find a field, or write a query against a GraphOS graph, fetch the API schema and pipe it into rover schema — this keeps the SDL out of your context and returns only what you need: Three rules that keep this correct: Use rover graph fetch (the API schema) — not rover supergraph fetch (that returns composition SDL with federation internals like join/link). Pipe it in — never run rover graph fetch alone and read the raw SDL (a large schema floods your context; that's exactly what rover schema avoids). The schema commands read piped SDL, not a graph ref — rover schema describe fails; you must fetch first and pipe.
