Claude Code Plugins vs Skills: Inside Google’s 104-Skill Repo

Short answer on Claude Code plugins vs skills: they are different. Google’s google/skills repository contains 104 standalone skills and a separate catalog for 16 external plugins. Those are not the same install set, and three commands produce three different outcomes. I cloned it and counted.

Claude Code plugins vs skills, in one table

Thing	What it is	How it loads
Skill	A folder centered on a SKILL.md instruction file; supporting files are optional	By default its name and description appear in the startup skill listing; full instructions load when invoked
Plugin	A self-contained bundle that can include skills, agents, commands, hooks, and MCP or LSP servers	Installed individually; it can be disabled or uninstalled
Marketplace	A catalog of plugin entries and sources	Adding one registers the catalog but installs zero plugins

That last row is where most of the confusion around Claude Code plugins vs skills starts. Adding a marketplace installs zero plugins.

Use a standalone skill when you need one reusable workflow. Use a plugin when you need to distribute multiple components, such as skills, agents, hooks, commands, or MCP servers, as one managed package.

Testing Claude Code plugins vs skills on a real repo

I cloned google/skills at commit 092e210 (2026-08-07, Apache 2.0) and counted files rather than reading the announcement posts. The repo is a useful case study because it places standalone skills alongside catalog metadata for external plugins.

SKILL.md files                104   (cloud 90 · ads 12 · analytics 2)
plugins in marketplace.json    16   sources are external repos
description text, raw          ~44,600 characters

The two numbers are not the same set. .claude-plugin/marketplace.json is not a wrapper around those 104 skills. It is a separate catalog pointing at 16 plugins that live in other repositories, mostly under gemini-cli-extensions. A second catalog for Codex sits in the same commit with 15 entries.

Three commands, three outcomes

Command	What you get
npx skills add google/skills	A selection from the 104 standalone skills
claude plugin marketplace add google/skills	The Google plugin catalog; zero plugins installed
claude plugin install <plugin>@google-plugins	One selected plugin from the 16-entry catalog

The part I could not measure

I wanted a clean rule like “N skills cost M tokens at startup.” There isn’t a universal one. Active skills contribute their name and description to the startup listing, but that listing has a budget: past it, descriptions get truncated or dropped. disable-model-invocation: true removes a skill’s description from model context, while skillOverrides can reduce an entry to its name or hide it entirely. So the honest statement is narrower than I wanted.

The description text across all 104 skills is about 44,600 characters raw. What that becomes in your session depends on the budget and your settings. Run /context before and after installing and you will know your own number, which is the only one that matters.

I deliberately did not convert that character count into tokens. A generic characters-per-token heuristic cannot reproduce Claude Code’s model-specific count or its applied listing budget, so /context is the cleaner measurement.

Practical takeaways on plugins vs skills

• Adding a marketplace registers a catalog and does not activate any plugin components. Still inspect the source before installing any plugin.
• 90 of the 104 skills target Google Cloud. Outside GCP the operational value is limited, though architecture and review-checklist skills can still be worth reading.
• Only one skill uses allowed-tools. That key pre-approves specific tools rather than restricting them; without it, a skill follows your normal Claude Code permission settings.
• Skills installed through npx skills are filesystem-backed; remove them with npx skills remove <name>. Plugins are managed through Claude Code’s plugin commands and can be disabled without being uninstalled.

Scope and date

Counted at commit 092e210 on 2026-08-10. I did not run the skills against a live Google Cloud project, and I did not record /context figures, so nothing here speaks to how well the skills perform. The repo describes itself as under active development, so counts will move.

I ran the same clone-and-count routine on a tool that turns PDFs into Claude Code skills, where fixed overhead made short chapters uneconomical, and on the Open Design Codex plugin, where the documented install path did not work.

Sources: google/skills · Claude Code skills documentation · plugin and marketplace documentation. Next review November 2026.