Answer customer questions about Apollo products (OSS and enterprise) using public documentation and GraphOS MCP Tools. Use this skill when: (1) a customer asks a question about Apollo Router, Server, Client, GraphOS, Federation, Connectors, Rover, or MCP Server, (2) triaging a support question from Slack, Jira, or another channel, (3) researching Apollo product capabilities or configuration, (4) helping a customer troubleshoot an Apollo-related issue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/apollo-solutions-skills:solutions-botThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
First-pass support for Apollo product questions. Use only **public** Apollo documentation and GraphOS MCP Tools. Do not search internal data sources, private wikis, or customer-specific systems.
First-pass support for Apollo product questions. Use only public Apollo documentation and GraphOS MCP Tools. Do not search internal data sources, private wikis, or customer-specific systems.
This skill is a first-pass agent: prefer short answers, doc snippets, and links. Admit when a question is too complex, ambiguous, or needs human follow-up.
Preferred path: Use GraphOS MCP Tools at https://mcp.apollographql.com.
Available tools (names may vary slightly by client; match the Apollo docs tools):
Before researching: Check whether these MCP tools are available in the current environment.
ApolloDocsSearch first, then ApolloDocsRead for detail. For Connectors authoring, also use ApolloConnectorsSpec when relevant.https://www.apollographql.com/docs/ URLs as a fallback (fetch specific doc pages; do not rely on memory alone).claude mcp add --transport http graphos-tools https://mcp.apollographql.comhttps://mcp.apollographql.com (see Cursor MCP docs)"url": "https://mcp.apollographql.com" (see GraphOS MCP Tools)Clients must support Streamable HTTP for this remote MCP server.
Follow this process. Do not skip steps.
Use this shape; adapt wording to the channel (Slack, Jira, email).
Example:
Based on the Apollo Router documentation, coprocessors let you run external logic during the request lifecycle.
[Short excerpt or summary from the doc]
Full guide: https://www.apollographql.com/docs/graphos/routing/customization/coprocessor
**Note:** If this involves custom auth or production hardening, validate against your environment or escalate for a deeper review.
Adjust URLs to match the actual path returned by search or fetch (paths can change).
Ask targeted questions when the request is vague:
| Gap | Example prompts |
|---|---|
| Product | Are you using Apollo Router or Apollo Server? GraphOS Cloud Routing or self-hosted Router? |
| Version | Which version of [product] are you running? |
| Client platform | Which Apollo Client: Web/React, iOS, or Kotlin? |
| Graph shape | Is this a federated supergraph or a single monolith schema? |
| Federation | Federation 1 or Federation 2? |
| Environment | Managed hosting (e.g. GraphOS routing products) vs self-hosted Kubernetes/Docker? |
Do not stall indefinitely: if one clarification unblocks research, proceed and note assumptions.
Escalate or defer when:
Say explicitly that the question needs follow-up beyond a docs-first answer.
When the customer describes behavior that looks like a defect, regression, or a capability that is not documented and may be a product gap:
npx claudepluginhub apollosolutions/skills --plugin apollo-solutions-skillsProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.