How to Integrate Google Agent Skills with Claude Code Using Plugins

You can integrate Google Agent Skills with Claude Code by registering the google/skills marketplace, installing skill plugins via the CLI, and restarting Claude Code to load the MCP server components into the agent's runtime.

The Google Skills repository contains reusable agent-skills—markdown-defined workflows that Claude Code consumes through a dedicated plugin marketplace. These skills extend Claude Code's capabilities by exposing new commands through the Model Context Protocol (MCP) framework, allowing the agent to execute complex workflows like Firebase management or Google Cloud IAM operations.

Understanding the Three-Layer Architecture

The integration relies on a specific architecture defined in the google/skills source code. Understanding these layers helps troubleshoot installation issues and clarifies how Claude Code interprets skill commands.

Skill Definitions (Markdown Manifests)

At the core of the system are skill definitions—Markdown files (*.md) that describe Customer Use Journeys (CUJ) and include a SKILL.md manifest. For example, skills/cloud/firebase-basics/SKILL.md defines the skill's metadata, entrypoints, and required permissions. These manifests are parsed by the skills runtime and exposed as invokable commands within Claude Code.

Plugin Packages

The repository bundles skills into plugin packages located under the plugins/ directory (or generated on-demand). Each plugin contains the skill manifests from skills/<category>/<skill>/ plus any MCP-server binaries required for backend execution. According to plugins/cloud/data-agent-kit/README.md, these packages ship with pre-compiled server components that handle authentication and API calls to Google services.

Claude Code Plugin Manager

Claude Code includes a built-in plugin manager that acts as a marketplace client. This component reads the plugin manifest from index.json (the auto-generated skill index), downloads the appropriate plugin package, and registers the skill set with Claude's MCP framework. The manager handles path resolution and binary placement automatically.

Step-by-Step Integration Process

Integrating a specific skill requires executing a sequence of CLI commands. The following steps use the Firebase skill as an example, but the pattern applies to any skill in the repository—simply replace firebase with your target skill name.

1. Add the Google Skills Marketplace

First, register the repository as a valid plugin source. This command updates Claude Code's configuration to recognize the google/skills repository:

claude plugin marketplace add google/skills

As documented in README.md at line 183, this step is performed once per machine and enables access to all skills within the repository.

2. Install the Specific Skill Plugin

Install the desired skill using the plugin install command. The syntax follows claude plugin install <plugin>@google-plugins:

claude plugin install firebase@firebase

According to skills/cloud/firebase-basics/references/setup/claude_code.md (lines 31-42), this command pulls the plugin package and places both the skill files and MCP binaries into Claude's plugin directory under the user's configuration path.

3. Verify Installation

Confirm that both the skill definitions and MCP server are properly registered:

npx skills list --agent claude-code
claude mcp list -s user

The first command displays available skills like firebase-basics, while the second verifies the MCP server entry. These verification steps are specified in claude_code.md (lines 13-22).

4. Restart Claude Code

Plugins are loaded during Claude Code's startup sequence. Close all Claude Code instances (both UI and terminal) and relaunch the application. As noted in claude_code.md at line 49, this step is mandatory—the plugin manager does not hot-load new skills in running sessions.

5. Execute Skill Commands

Once restarted, invoke skills through the skills CLI:

npx skills run firebase-basics login

This command triggers the login sub-command defined in the skill's manifest. Claude Code routes this request to the corresponding MCP server, which handles the actual Google Cloud authentication flow behind the scenes.

Key Source Files and Their Roles

Several files in the google/skills repository govern the integration behavior:

• README.md (repository root): Lists supported agent harnesses and provides the one-line marketplace registration command at line 183.
• skills/cloud/firebase-basics/references/setup/claude_code.md: Contains the definitive Claude Code-specific setup guide, including verification commands and restart requirements (lines 13-22, 31-42, 49).
• skills/<category>/<skill>/SKILL.md: Individual skill manifests defining name, description, and entrypoint URLs. Example: skills/cloud/firebase-basics/SKILL.md.
• plugins/cloud/data-agent-kit/README.md: Documents plugin package structure and how agents consume bundled MCP servers.
• index.json: Auto-generated index mapping skill names to entrypoint URLs, used by the plugin installer to resolve package locations.

Summary

• Google Agent Skills are markdown-defined workflows stored in the google/skills repository that extend Claude Code via the MCP framework.
• Plugin packages bundle skill manifests with MCP-server binaries under the plugins/ directory.
• Integration requires four CLI steps: adding the marketplace (claude plugin marketplace add), installing the plugin (claude plugin install), verifying with npx skills list, and restarting Claude Code.
• Skills are invoked via npx skills run <skill-name> <sub-command>, with the MCP server handling backend authentication and API calls.
• Source accuracy depends on specific files like SKILL.md manifests and claude_code.md setup guides.

Frequently Asked Questions

What distinguishes a skill definition from a plugin package?

A skill definition is the markdown documentation and manifest (SKILL.md) describing what the skill does, while a plugin package is the distributable unit containing both the skill definition and the compiled MCP-server binary required for execution. The plugin package is what Claude Code actually downloads and installs.

Why must I restart Claude Code after installing a plugin?

Claude Code loads its plugin registry and MCP server configurations during the startup sequence. As implemented in the plugin manager (documented in claude_code.md line 49), the system does not support hot-reloading of MCP servers or skill manifests for security and stability reasons.

Can I install multiple Google Skills simultaneously?

Yes. After adding the google/skills marketplace once, you can install multiple skill plugins in sequence using claude plugin install <skill>@google-plugins for each desired skill. Each installation places files into separate subdirectories within Claude's plugin folder without conflicts.

Where does Claude Code store the installed plugin files?

Claude Code places installed plugins in the user-scoped plugin directory, with skill manifests copied from paths like skills/cloud/firebase-basics/ and MCP binaries extracted from the plugins/ directory structure. The exact filesystem location depends on your operating system and Claude Code's configuration, but you can verify installation using claude mcp list -s user.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}