SkillFoxx

Apollo GraphQL Agent Skills plugin

Apollo agent skills: Client, Server, iOS, Kotlin, MCP Server, Rover, GraphQL schemas and operations. Install via npx skills.

  • 130 ★ on the repository
  • Last commit
PluginOfficial

Minimal access

Why this level

  • The skills give the agent instructions and reference files and run nothing themselves.
All reasons and checks

apollographql/skillsAuthor:Apollo GraphQL

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/apollo-graphql-agent-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • The skills give the agent instructions and reference files and run nothing themselves.

This is third-party code. Review the repository files before installing.

What it does

The set from Apollo itself teaches coding agents to work with its tools by the company's conventions. It has skills for Apollo Client 4.x on React (queries, mutations, caching, local state), Apollo Server 4.x (schemas, resolvers, auth, plugins), Apollo iOS in Swift and Apollo Kotlin for Android, plus skills for Apollo MCP Server, Rover, GraphOS Factory, GraphQL schema and operation design and idiomatic Rust. There are three ways to connect the skills: the interactive `npx skills add apollographql/skills` command, as a Claude Code plugin with commands like `/apollo-skills:apollo-client`, or through `gh skill install`. Each skill has its own folder with `SKILL.md` and reference files, for example on caching, fragments and error handling.

Who it is for. Developers building on Apollo GraphQL who want Claude Code, Cursor or Codex to write client, server and schemas by the vendor's guidance.

Good fit when

  • The agent wires Apollo Client 4 into a React app and sets up caching and fragments.
  • A GraphQL schema is being designed: types, naming, pagination, error handling.
  • You need resolvers and plugins for Apollo Server 4.
  • A mobile team works with Apollo iOS or Apollo Kotlin and wants a single code style.

Not a fit when

  • Your project does not use Apollo: the skills are tied to its tools and versions.
  • You need Apollo Connectors work: that skill is deprecated in favor of `graphos-factory`.
  • You need a ready MCP server: the `apollo-mcp-server` skill documents it, and the server itself is installed separately.

Example request

Design a GraphQL schema for a product catalog with pagination and errors following Apollo guidance.

Limitations

The skills are tied to specific versions, for example Apollo Client 4.x and Apollo Server 4.x, and advice may not fit other major versions. The `apollo-connectors` skill is marked deprecated and replaced by `graphos-factory`. Installing through npx opens an interactive wizard where you pick skills, agents (Claude Code, Codex, Cursor, Gemini CLI, Goose, OpenCode), scope and method: symlink or copy. Releases are tagged with semver, and you can pin a version with the `--pin` flag of `gh skill install`. Some skills target Rust, Swift or Kotlin, so the matching dev tooling is installed separately.

How to disable. For Claude Code run `/plugin uninstall apollo-skills@apollo-marketplace`. After an `npx skills` install delete the skill folders from the agent or project directory.

FAQ

How do I install the Apollo skills for Claude Code?

Run `/plugin marketplace add apollographql/skills`, then `/plugin install apollo-skills@apollo-marketplace`. The skills appear as commands like `/apollo-skills:apollo-client`. Another route: `npx skills add apollographql/skills`.

Which agents does the npx skills install support?

The wizard offers Claude Code, Codex, Cursor, Gemini CLI, Goose and OpenCode. `gh skill install --agent` supports more hosts, GitHub Copilot included.

How do I pin the skills version?

Use `gh skill install apollographql/skills --pin v1.0.0 --agent claude-code`. A pinned version is skipped during updates. Without pinning, `claude plugin update` updates the plugin.

What about the apollo-connectors skill?

It is marked deprecated. Use `graphos-factory` instead, which builds and iterates on an Apollo Connectors subgraph over a REST API.

Do I need Apollo MCP Server separately?

The `apollo-mcp-server` skill explains how to connect AI agents with GraphQL APIs through that server, but the server itself is installed separately following Apollo docs.

Discussion

No questions or reviews yet.

Plugins

OpenClaw Agent Skills

openclaw-agent-skills

Official

Shared skills for coding agents that work on OpenClaw projects: review and other workflows. A narrow topic for people who write OpenClaw code

SkillExtended access1.1K

skills-npm links agent skills shipped in your dependencies in node_modules and listed in the skills field of package.json

CLIExtended access582

Softaworks Agent Toolkit

Softaworks Agent Skills

A marketplace of skills, subagents and commands for coding agents: development, documentation, planning and workplace communication

PluginExtended access2.7K

Builder Skills

Skills for agents

A set of small skills from Builder.io for agent work habits: visual plans and diff recaps, docs-first checks, cross-agent review and clean status updates

SkillExtended access4.7K

Over 1,100 ready-made skills for Claude Code, Codex, Gemini CLI and Cursor, plus an MCP server that picks a skill for the task

SkillExtended access200

A vetted skill registry with a CLI that installs into twenty-plus agents and an MCP server for on-demand skill lookup

SkillExtended access7.2K

README in short

The repository describes a set of skills in the Agent Skills format, three install routes, a plugin command table and version release rules. Releases are tagged automatically on every content change in main, and version pinning is available through the GitHub CLI.

README badge

Original SKILL.md

---
name: graphql-schema
description: >
  Guide for designing and changing GraphQL schemas following industry best practices. Use this skill
  whenever you create or edit GraphQL SDL, such as a `schema.graphql` file or `typeDefs`, including when:
  (1) designing a new GraphQL schema or API,
  (2) adding or changing types, fields, arguments, mutations, or descriptions in an existing schema,
  (3) reviewing existing schema for improvements,
  (4) deciding on type structures or nullability,
  (5) implementing pagination or error patterns,
  (6) ensuring security in schema design.
license: MIT
compatibility: Any GraphQL implementation (Apollo Server, graphql-js, Yoga, etc.)
metadata:
  author: apollographql
  version: "1.0.2"
allowed-tools: Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep
---

# GraphQL Schema Design Guide

This guide covers best practices for designing GraphQL schemas that are intuitive, performant, and maintainable. Schema design is primarily a server-side concern that directly impacts API usability.

## Schema Design Principles

### 1. Design for Client Needs

- Think about what queries clients will write
- Organize types around use cases, not database tables
- Expose capabilities, not implementation details

### 2. Be Explicit

- Use clear, descriptive names
- Make nullability intentional
- Document with descriptions

### 3. Design for Evolution

- Plan for backwards compatibility
- Use deprecation before removal
- Avoid breaking changes
- Give every new argument or input field a default value, or make it nullable. Existing clients don't send it, so a required field without a default makes their requests fail validation.

## Quick Reference

Report a problem