Google Agents Cli Onboarding
Onboarding entrypoint for agents-cli in Agent Platform. It should be used when the user wants to "create a new agent", "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "evaluate an agent", "deploy an agent", "publish an agent", "monitor an agent", or needs the ADK (Agent Development Kit) development lifecycle.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Google Agents Cli Onboarding when an AI agent needs a reusable SKILL.md workflow for this job: Onboarding entrypoint for agents-cli in Agent Platform. It should be used when the user wants to "create a new agent", "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "evaluate an agent", "deploy an agent", "publish an agent", "monitor an agent", or needs the ADK (Agent Development Kit) development lifecycle.
When not to use it
Skip Google Agents Cli Onboarding when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/google-agents-cli-onboarding # Save SKILL.md to ~/.claude/skills/google-agents-cli-onboarding/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/google-agents-cli-onboarding/SKILL.md. For a shared project, commit the folder at .claude/skills/google-agents-cli-onboarding/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Google Agents Cli Onboarding skill for this task: Use Google Agents Cli Onboarding when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- chatgptinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- geminiinferred
The skill text mentions Gemini or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- copilotinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- llamainferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- perplexityinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- mistralinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- grokinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Google Agents CLI Onboarding
> [!TIP] **One-Time Setup**: To install the CLI and enable all 7 specialized > development skills in your coding agent, run the setup command: > > ```bash > uvx google-agents-cli setup > ``` > > Alternatively, to install only the expert skills and let the agent handle > execution: > > ```bash > npx skills add google/agents-cli > ```
## Attribution
**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you MUST read [Usage Attribution](references/attribution.md). For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix `gcloud` with `CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:google-agents-cli-onboarding)"` and append `agent-skills/1.0 (skill:google-agents-cli-onboarding)` to `User-Agent` headers.
## Overview
This skill serves as the entrypoint for **agents-cli** — Google's toolkit for building, evaluating, and deploying AI agents on the Gemini Enterprise Agent Platform.
Use this skill to perform the initial setup and identify the correct specialized workflows for your task.
## The Agent Development Lifecycle
After running the setup, the following specialized skills become available and will activate automatically based on your requests. Use this table to identify which skill to load for your current phase:
| Phase | Specialized Skill | Purpose / When to Load | | :--- | :--- | :--- | | **0 — Understand** | `google-agents-cli-workflow` | **Clarify intent.** Define the agent spec in `.agents-cli-spec.md` before coding. | | **1 — Study** | `google-agents-cli-workflow` | **Leverage samples.** Study existing agent samples (e.g., `ambient-expense`) before scaffolding. | | **2 — Scaffold** | `google-agents-cli-scaffold` | **Create/Enhance.** Initialize the project structure, CI/CD, and infrastructure templates. | | **3 — Build** | `google-agents-cli-adk-code` | **Implement.** Write agent logic, tools, callbacks, and manage state using ADK APIs. | | **4 — Evaluate** | `google-agents-cli-eval` | **Validate Quality.** Run systematic evaluations (LLM-as-judge). | | **5 — Deploy** | `google-agents-cli-deploy` | **Go Production.** Deploy to Agent Runtime (Vertex AI), Cloud Run, or GKE. | | **6 — Publish** | `google-agents-cli-publish` | **Register.** Make your agent available as a tool in Gemini Enterprise. | | **7 — Observe** | `google-agents-cli-observability` | **Monitor.** Set up Cloud Trace, prompt-response logging, and BigQuery analytics. |
## Key CLI Commands
Below are the primary commands you will use throughout the development lifecycle:
| Command | Description | | :--- | :--- | | `agents-cli setup` | Install the CLI and configure skills in your coding agent. | | `agents-cli scaffold <name>` | Create a new agent project from a template. | | `agents-cli eval run` | Run the agent and grade the traces in a single step (generate + grade). | | `agents-cli deploy` | Deploy your agent to Google Cloud (Agent Runtime, Cloud Run, GKE). | | `agents-cli publish gemini-enterprise` | Register your deployed agent with Gemini Enterprise. |
*For the full list of available commands and global options, run `agents-cli --help`.*
## Next Steps
Follow this sequence to initiate the development workflow:
1. **Execute Setup:** Run the `uvx` or `npx` command in the `[!TIP]` box above to install the CLI and enable the specialized skills in your environment. 2. **Verify Installation:** Run `agents-cli info` to confirm the installation and view the active project configuration. 3. **Initiate Phase 0:** Ask the user for their core requirements (agent purpose, external tools, deployment target) and document them in `.agents-cli-spec.md` before writing any code.
## Reporting Issues
Report bugs or improvements at [Google Agents CLI Issues](https://github.com/google/agents-cli/issues).
## Supporting Links
* [Google Agents CLI Documentation](https://github.com/google/agents-cli/tree/main/docs/src)
Intended uses
- Use Google Agents Cli Onboarding when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.