How to Install Google Skills for AI Agents: CLI, Direct Path, and Plugin Methods
Google Skills install via npx skills add google/skills — an interactive CLI that copies Markdown-based skill packages into your agent's runtime folder.
Google Skills provides a modular system for extending AI agents with pre-built capabilities. Each skill is a Markdown-based package containing prompts, context, and tooling instructions that agents load at runtime. This article covers the three installation methods documented in the repository, based on the source code in google/skills.
Installing Google Skills with the skills CLI
The recommended approach for most agents uses the skills CLI via npx.
npx skills add google/skills
As implemented in google/skills, this command:
- Downloads the
skillshelper tool - Parses the repository tree
- Prompts you to select specific skill directories
- Copies the chosen Markdown files into your agent's skill folder (referenced in
README.mdlines 13-18)
The interactive selection lets you avoid installing unused skills. For example, you might select only cloud authentication recipes while skipping GKE-specific tooling.
Installing a Specific Skill by Direct Path
For targeted installations, pass the full path to a single skill directory:
npx skills add google/skills/skills/cloud/gke-workload-scaling
This bypasses the interactive prompt and copies only that skill's SKILL.md and supporting files. The source code shows each skill follows the pattern skills/<category>/<skill-name>/SKILL.md.
Installing via the skills.sh Shortcut
For browser-based workflows, the repository provides a one-click badge that launches the same installer. The skills.sh shortcut is referenced in README.md lines 3-5 and offers identical functionality without terminal access.
Installing Plugins for Agent-Specific Harnesses
Beyond core skills, Google Skills includes optional plugins for specific agent harnesses. For Claude Code:
claude plugin marketplace add google/skills
claude plugin install @google-plugins
These plugins extend the agent's execution capabilities separate from the Markdown skill definitions (documented in README.md lines 55-64).
Using Installed Skills in Prompts
After installation, invoke any skill with @ notation:
@google-cloud-recipe-auth
The agent loads the authentication recipe defined in skills/cloud/google-cloud-recipe-auth/SKILL.md and executes its prompt template with your provided context.
Architecture: How Google Skills Installation Works
| Component | Purpose | Source Location |
|---|---|---|
skills CLI |
Repository parser, interactive selector, file copier | README.md |
SKILL.md files |
Skill definitions (prompts, context, tooling) | skills/**/SKILL.md |
| Plugins folder | Harness-specific extensions (Claude, Codex, etc.) | README.md |
| Agent harness | Runtime environment that loads Markdown skills | README.md |
This separation of concerns — Markdown definitions independent of execution engines — enables versioned skill updates without agent code changes.
Key Files for Installation Reference
README.md— Primary installation instructions and skill catalogskills/**/SKILL.md— Individual skill definitionsplugins/cloud/data-agent-kit/README.md— Plugin documentation for various harnessesopencode.json— Metadata for Opencode tooling integration
Summary
- Primary method:
npx skills add google/skillswith interactive selection - Direct install: Append full path to skill directory for single-skill deployment
- Alternative:
skills.shbrowser shortcut for non-terminal workflows - Plugin support: Separate
claude/codexcommands for harness-specific features - Usage:
@skill-namesyntax triggers loaded skills in agent prompts
Frequently Asked Questions
What is a Google Skill technically?
A Google Skill is a directory containing a SKILL.md file that defines prompts, context variables, and optional tooling instructions. The agent harness parses this Markdown at runtime to execute the skill's behavior.
Do I need to install the entire repository?
No. The npx skills add command presents an interactive picker allowing selection of specific skill directories. You can also install individual skills directly by path.
What's the difference between skills and plugins?
Skills are Markdown-based prompt templates loaded by any compatible harness. Plugins are harness-specific extensions (e.g., Claude Code integrations) that provide additional runtime capabilities beyond the core skill definitions.
Can I use Google Skills with agents other than Claude?
Yes. The architecture is harness-agnostic — the Markdown skill files work with any agent that supports the @skill-name invocation pattern. Dedicated plugins exist for Claude, Codex, and Antigravity as documented in README.md lines 59-64.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →