google/skills: README-based editorial guide

google/skills describes itself in the README as "Agent Skills for Google products and technologies". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "Agent Skills", the README says: > [!NOTE] > This repository is under active development.. That establishes the project's stated boundary, not a production test.

The README's "Available Skills" section gives a useful starting point for deciding whether the project fits: Gemini Enterprise Agent Platform - Managed Agents API Skill. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Data science workflow with AI agents solution. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Plugins". The source evidence includes: This repo also bundles Google product plugins (Skills + MCP servers) for agent harnesses.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: README 没有给出可直接复制的安装命令。 When the README contains no runnable command, this article does not invent one. Open its "Installation" section and confirm system dependencies, default ports, and first-run initialization before using a public server.

Daily operation depends on the project's own documentation. In "Plugins", the README notes: | Agent harness | Install | | :--- | :--- | | Claude Code | claude plugin marketplace add google/skills, then claude plugin install @google-plugins | | Codex | codex plugin marketplace add google/skills, then install from the /plugins. Configuration files, environment variables, permissions, and data paths are included only when the source makes them explicit. Anything unstated should be tested in an isolated environment with a recoverable configuration copy. The same source also notes: Live bidirectional multimodal streaming agentic AI solution.