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.
- License 许可
- Apache-2.0
- 所属仓库
- google/skills
- 最近更新
- 2026-11-14
- Stars
- ★ 2.4w
- Forks
- 2.0k
01 前言 Front Matter
- name
- google-agents-cli-onboarding
- metadata
- { "version": "1.0.1", "category": "DevOps" }
- description
- 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.
02 资源文件 1
- 参考文档references/attribution.md1.9 KB
03 SKILL.md 正文
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:
uvx google-agents-cli setupAlternatively, to install only the expert skills and let the agent handle execution:
npx skills add google/agents-cli
Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read Usage Attribution. 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:
- Execute Setup: Run the
uvxornpxcommand in the[!TIP]box above to install the CLI and enable the specialized skills in your environment. - Verify Installation: Run
agents-cli infoto confirm the installation and view the active project configuration. - Initiate Phase 0: Ask the user for their core requirements (agent
purpose, external tools, deployment target) and document them in
.agents-cli-spec.mdbefore writing any code.
Reporting Issues
Report bugs or improvements at Google Agents CLI Issues.
Supporting Links
04 同仓库更多 Skills
sign-in-with-google-web
Implement, configure, and secure Sign In With Google (SiwG) using Google Identity Services (GIS / `https://accounts.google.com/gsi/client`) across web architectures. Use when creating Google sign-in buttons, implementing Google One Tap with FedCM, integrating GIS in React/Next.js/Angular/HTML, verifying ID tokens on backend runtimes (Python/Node.js/Go/Java), enforcing Google Workspace domain restrictions (`hd`), securing client-side ID tokens via WebCrypto nonces or encrypted IndexedDB, embedding in cross-origin iframes via the Intermediate Iframe API (`https://accounts.google.com/gsi/intermediate`), configuring Content Security Policy (CSP), COOP, and Permissions Policy (`identity-credentials-get`) headers, or handling sign-out and revocation. Don't use for legacy Google Sign-In (`gapi.auth2`), Google Cloud IAM service accounts, or Android/iOS native Credential Manager.
dpop-adoption
Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com/token. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM / service account authentication.
retrieving-developer-knowledge
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
migrate-to-rust
Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure/fix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.
finding-google-skills
Google platform decision and setup guidance, loaded on demand from Google's skill catalog. Use when a developer is choosing or setting up part of their stack, such as where to run a service, a database, storage, messaging, authentication, analytics, ads, or AI model serving, and a Google product is a reasonable candidate - whether or not a vendor is named - or when a request names a Google product or API. Brings in the matching Google skill so the answer can weigh Google options, their trade-offs, and when they are not the right fit. Skip when the stack is already settled on another provider and no Google product is named, or the task involves no platform choice.
workload-manager-basics
Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.