Skip to main content
skillsSource-backedReview first Safety Privacy

Google Agents CLI Skills

Google Agents CLI skill suite for coding agents that build, scaffold, evaluate, deploy, publish, and observe ADK agents on Gemini Enterprise Agent Platform, Agent Runtime, Cloud Run, GKE, and Google Cloud.

HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • The skills intentionally guide agents through scaffold, eval, deploy, publish, CI/CD, infrastructure, datastore, and observability workflows that can create or modify cloud resources.
  • Deployment and infrastructure commands may provision service accounts, IAM bindings, Terraform resources, Cloud Run services, Agent Runtime deployments, GKE resources, Artifact Registry images, Secret Manager entries, and CI/CD runners.
  • The workflow skill explicitly requires clarifying goals and writing a spec before scaffolding a new project; skipping that step can create wrong infrastructure or unsafe agent behavior.
  • Evaluation guidance may invoke LLM-as-judge, synthetic datasets, and prompt optimization; treat cost, data exposure, and nondeterminism as production concerns.
  • Do not run deploy, publish, infrastructure, datastore, or CI/CD commands without explicit human approval and a known Google Cloud target.

Privacy notes

  • Agents CLI projects can contain Google Cloud credentials, AI Studio keys, Secret Manager names, service account emails, project IDs, regions, Terraform state, eval traces, prompts, tool outputs, logs, traces, user data, embeddings, and datastore contents.
  • Eval artifacts and observability exports can include full prompts, tool calls, responses, failure rationales, trace IDs, and private application data.
  • Publishing to Gemini Enterprise, deploying to Agent Runtime, Cloud Run, or GKE, and enabling analytics can move agent traffic into Google Cloud services subject to separate terms and access controls.
  • Keep project IDs, credentials, Terraform state, traces, eval datasets, user data, private prompts, and secret names out of public issues, PRs, examples, and screenshots.

Prerequisites

  • Coding assistant or skill host that can consume Agent Skills, or a local terminal where `uvx google-agents-cli setup` can install the CLI plus skills.
  • Python 3.11+, uv, and Node.js for the documented setup flow.
  • Google Cloud project, billing, credentials, APIs, IAM, region, and deployment target decisions when moving beyond local development.
  • Clear agent requirements before scaffolding: purpose, external APIs, tools, safety constraints, data sources, and deployment preference.

Schema details

Install type
package
Reading time
8 min
Difficulty score
82
Troubleshooting
Yes
Breaking changes
No
Source repository stats
Scope
Source repo
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-06-18
Retrieval sources
https://github.com/google/agents-clihttps://raw.githubusercontent.com/google/agents-cli/main/README.mdhttps://google.github.io/agents-cli/reference/skills/https://raw.githubusercontent.com/google/agents-cli/main/gemini-extension.jsonhttps://raw.githubusercontent.com/google/agents-cli/main/skills/google-agents-cli-workflow/SKILL.mdhttps://raw.githubusercontent.com/google/agents-cli/main/skills/google-agents-cli-scaffold/SKILL.mdhttps://raw.githubusercontent.com/google/agents-cli/main/skills/google-agents-cli-eval/SKILL.mdhttps://raw.githubusercontent.com/google/agents-cli/main/skills/google-agents-cli-deploy/SKILL.mdhttps://raw.githubusercontent.com/google/agents-cli/main/LICENSE
Tested platforms
Claude CodeCodexGemini CLIAntigravityGeneric coding agents
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Tool listing metadata
Full copyable content
# Install only the skills
npx skills add google/agents-cli

# Install CLI plus skills
uvx google-agents-cli setup

# Create a prototype ADK agent project
agents-cli scaffold create my-agent --agent adk --prototype

# Run the evaluation loop
agents-cli eval run

About this resource

Google Agents CLI Skills

google/agents-cli packages a CLI and seven Agent Skills for coding agents that build, evaluate, deploy, publish, and observe Google ADK agents. It is designed for Gemini CLI, Claude Code, Codex, Antigravity, and other coding agents that need source-backed Google Cloud and Gemini Enterprise Agent Platform workflows instead of generic agent advice.

The project is the active successor named by Google Cloud Agent Starter Pack's README for new projects. It gives agents a lifecycle path from scaffolded ADK code to evals, deployment targets, Gemini Enterprise registration, and observability.

Knowledge Freshness

The repository is current and the README describes agents-cli as the CLI and skills for building agents on Gemini Enterprise Agent Platform. The skills target Google ADK, Agent Runtime, Cloud Run, GKE, CI/CD, evals, datastore infrastructure, observability, and Gemini Enterprise publishing.

Google Cloud product names, Agent Platform launch stages, CLI commands, deployment defaults, IAM requirements, eval metrics, and ADK APIs can change. Use the skills for lifecycle structure, then verify flags, cloud terms, service availability, pricing, and permissions against the current docs and target project before running infrastructure or deployment commands.

Retrieval Sources

This listing is grounded in:

  • The google/agents-cli repository README.
  • The public Agents CLI documentation and skills reference.
  • The gemini-extension.json package metadata.
  • Representative SKILL.md files for workflow, scaffolding, evaluation, and deployment.
  • The Apache-2.0 license text.
  • Current GitHub repository metadata.

Core Workflow

Install only the skills:

npx skills add google/agents-cli

Install the CLI plus skills:

uvx google-agents-cli setup

Create a prototype ADK agent:

agents-cli scaffold create my-agent --agent adk --prototype

Run the evaluation loop:

agents-cli eval run

Capability Scope

The README lists these seven Agent Skills:

Skill What it teaches the coding agent
google-agents-cli-workflow Full lifecycle, code preservation, model selection, and troubleshooting
google-agents-cli-adk-code ADK Python API, agents, tools, orchestration, callbacks, and state
google-agents-cli-scaffold Project creation, enhancement, upgrade, templates, and deployment choices
google-agents-cli-eval Eval datasets, metrics, LLM-as-judge, adaptive rubrics, and quality flywheel
google-agents-cli-deploy Agent Runtime, Cloud Run, GKE, CI/CD, secrets, service accounts, and rollback
google-agents-cli-publish Gemini Enterprise registration
google-agents-cli-observability Cloud Trace, logging, analytics, and third-party observability integrations

The CLI commands cover setup, login, scaffold, run, install, lint, eval generate/grade/compare/analyze/optimize, deploy, publish, infrastructure, datastore provisioning, data ingestion, project info, and skill updates.

Production Rules

Use these skills as an agent-building lifecycle, not a shortcut around cloud review:

  • Clarify the agent purpose, tools, APIs, data sources, safety constraints, and deployment preference before scaffolding.
  • Prefer prototype-first development until behavior and eval cases are clear.
  • Preserve scaffolded manifests, deployment structure, and guidance files unless the user explicitly approves structural changes.
  • Do not deploy, publish, provision infrastructure, set up CI/CD, or run datastore ingestion without explicit approval and a known Google Cloud target.
  • Treat evals as the validation path for agent behavior; do not write brittle tests that assert exact LLM output text.
  • Review IAM, service accounts, Secret Manager access, Terraform state, regions, billing, and rollback before production deployment.
  • Summarize eval traces, deployment output, and observability data without leaking prompts, credentials, user data, project IDs, or trace details.

Use Cases

  • Ask Codex to create a prototype ADK agent with the right scaffolding and guidance files.
  • Use Claude Code to enhance an existing agent project with Agent Runtime, Cloud Run, or GKE deployment support.
  • Have Gemini CLI build an eval dataset, run traces, grade results, and iterate through a quality flywheel.
  • Use an agent to deploy only after explicit approval, with service account, secret, region, and target checks.
  • Register a deployed agent with Gemini Enterprise and then inspect Cloud Trace, logs, analytics, and observability output.

Source Review

  • The README says agents-cli provides CLI commands and skills for building agents on Gemini Enterprise Agent Platform.
  • The README explicitly lists Gemini CLI, Claude Code, Codex, Antigravity, and other coding agents as supported coding assistants.
  • The setup section documents uvx google-agents-cli setup and a skills-only install path with npx skills add google/agents-cli.
  • The Agent Skills table lists seven skills covering workflow, ADK code, scaffolding, evaluation, deployment, publishing, and observability.
  • The workflow skill requires understanding the agent requirements before code or scaffolding, then routes through scaffold, build, eval, deploy, publish, and observe phases.
  • The deploy skill covers Agent Runtime, Cloud Run, GKE, CI/CD, secrets, service accounts, rollback, and production infrastructure.
  • The evaluation skill documents eval generation, grading, comparison, failure analysis, and prompt optimization.
  • The license file identifies the repository as Apache-2.0.

Duplicate Review

Checked current content/skills/, content/tools/, content/mcp/, open pull requests, and repository-wide content for Google Agents CLI, google/agents-cli, google-agents-cli, agents-cli, ADK agent skills, Agent Runtime deployment skills, and Gemini Enterprise Agent Platform skills. The existing Google Agent Development Kit entry covers google/adk-python as a tool/framework; no dedicated Google Agents CLI skills entry, exact source URL duplicate, target file, or open duplicate PR was found.

Disclosure

Editorial listing. No paid placement or affiliate link is used. The upstream repository is Apache-2.0 licensed. Google Cloud, Gemini Enterprise Agent Platform, Agent Runtime, Cloud Run, GKE, AI Studio, model providers, and third-party observability or CI/CD services may have separate billing, terms, privacy, and access-control requirements.

Source citations

Add this badge to your README

Show that Google Agents CLI Skills is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/google-agents-cli-skills.svg)](https://heyclau.de/entry/skills/google-agents-cli-skills)

How it compares

Google Agents CLI Skills side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldGoogle Agents CLI Skills

Google Agents CLI skill suite for coding agents that build, scaffold, evaluate, deploy, publish, and observe ADK agents on Gemini Enterprise Agent Platform, Agent Runtime, Cloud Run, GKE, and Google Cloud.

Open dossier
Google Cloud Agent Skills

Google Agent Skills catalog for AI agents working with Google Cloud, Gemini Enterprise Agent Platform, Gemini APIs, Skill Registry, Cloud Run, BigQuery, Firebase, GKE, Cloud SQL, AlloyDB, gcloud, auth, onboarding, and Well-Architected Framework guidance.

Open dossier
Vercel Agent Skills

Vercel Labs' official Agent Skills collection for AI coding agents working on Vercel deployments, React and Next.js performance, React Native, web design guidelines, writing guidelines, composition patterns, view transitions, CLI token workflows, and Vercel optimization audits.

Open dossier
Azure Skills Plugin

Official Microsoft Azure Skills Plugin for coding agents, combining Azure Agent Skills, Azure MCP Server configuration, and Foundry MCP workflows for build, deploy, diagnostics, cost, compliance, AI, Kubernetes, storage, RBAC, and migration scenarios.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Categoryskillsskillsskillsskills
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorGoogleGoogleVercel LabsMicrosoft
Added2026-06-182026-06-182026-06-182026-06-18
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo
Safety notesThe skills intentionally guide agents through scaffold, eval, deploy, publish, CI/CD, infrastructure, datastore, and observability workflows that can create or modify cloud resources. Deployment and infrastructure commands may provision service accounts, IAM bindings, Terraform resources, Cloud Run services, Agent Runtime deployments, GKE resources, Artifact Registry images, Secret Manager entries, and CI/CD runners. The workflow skill explicitly requires clarifying goals and writing a spec before scaffolding a new project; skipping that step can create wrong infrastructure or unsafe agent behavior. Evaluation guidance may invoke LLM-as-judge, synthetic datasets, and prompt optimization; treat cost, data exposure, and nondeterminism as production concerns. Do not run deploy, publish, infrastructure, datastore, or CI/CD commands without explicit human approval and a known Google Cloud target.Google Cloud skills can create, update, delete, deploy, query, or configure cloud resources, datasets, IAM policies, service accounts, APIs, containers, jobs, and networking. The gcloud skill requires command validation and safety guardrails before invoking Google Cloud CLI commands; do not let agents improvise cloud commands from memory. Skill Registry guidance includes skill lifecycle management such as upload, update, and permanent delete operations; validate environment and approval before use. Cloud Run, GKE, BigQuery, Firebase, Cloud SQL, AlloyDB, and Gemini API workflows can create cost, expose endpoints, alter data, or change production behavior. The repository notes active development, so verify exact commands, product names, API availability, and launch-stage limits before production use.The deploy-to-vercel and Vercel CLI token skills can guide agents toward git pushes, preview deployments, Vercel project linking, environment variable changes, and account-scoped CLI calls; keep human approval on those actions. The vercel-cli-with-tokens skill includes token-handling workflows. Prefer environment variables over command-line token flags and avoid echoing secrets into prompts, logs, screenshots, or public PRs. The vercel-optimize skill reads Vercel metrics, usage, project configuration, and code scan results; verify the linked project and team scope before collecting or acting on recommendations. The web-design-guidelines and writing-guidelines skills fetch current upstream rule documents at use time, so review fetched guidance before treating output as policy. React, Next.js, and React Native performance rules are strong defaults, but agents still need local tests, framework-version checks, and product-specific review before broad refactors.Azure Skills can guide agents through live cloud actions including infrastructure generation, validation, deployment, diagnostics, cost analysis, RBAC, Kubernetes, storage, AI services, and migration work. The included MCP configuration starts the Azure MCP server, which can expose structured tools across Azure services when the local account is authenticated. Deployment skills require plan and validation phases before live deployment. Do not skip `azure-prepare` or `azure-validate` steps when the upstream skill requires them. Live Azure changes can create cost, modify production resources, change access control, deploy workloads, query logs, or expose service data. Keep human review around write operations. For sovereign clouds, configure the Azure MCP server cloud argument explicitly instead of assuming Azure Public Cloud.
Privacy notesAgents CLI projects can contain Google Cloud credentials, AI Studio keys, Secret Manager names, service account emails, project IDs, regions, Terraform state, eval traces, prompts, tool outputs, logs, traces, user data, embeddings, and datastore contents. Eval artifacts and observability exports can include full prompts, tool calls, responses, failure rationales, trace IDs, and private application data. Publishing to Gemini Enterprise, deploying to Agent Runtime, Cloud Run, or GKE, and enabling analytics can move agent traffic into Google Cloud services subject to separate terms and access controls. Keep project IDs, credentials, Terraform state, traces, eval datasets, user data, private prompts, and secret names out of public issues, PRs, examples, and screenshots.Google Cloud workflows may expose project IDs, service account emails, OAuth tokens, API keys, ADC credentials, Terraform state, dataset names, table schemas, query text, logs, traces, prompts, model outputs, embeddings, and customer data. BigQuery, Firebase, Cloud SQL, AlloyDB, GKE, and Agent Platform workflows may process regulated or proprietary data; review data residency, IAM, retention, audit logging, and sharing rules before use. Gemini API and Agent Platform skills can send prompts, files, images, audio, video, tool inputs, structured outputs, cached contexts, and batch datasets to Google services. Keep credentials, project IDs when sensitive, private queries, logs, trace payloads, Terraform state, customer data, and generated datasets out of public prompts, issues, PRs, and screenshots.Deployment and optimization workflows may expose project names, team slugs, deployment URLs, routes, metrics, usage details, billing signals, source paths, build configuration, environment variable names, and CLI account context. Keep VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID, API keys, environment values, claim URLs, deployment logs, and private preview URLs out of public artifacts unless intentionally disclosed. Design, writing, React, and performance reviews can reveal proprietary UI, product copy, documentation strategy, source code, routes, and business priorities to the configured model provider.Azure work can expose subscription IDs, tenant IDs, resource group names, resource inventories, cost data, log queries, Application Insights telemetry, storage paths, RBAC assignments, model deployment names, and cloud architecture details. Authenticated MCP tools can read or operate on live Azure and Foundry resources according to the local account's permissions. Keep Azure credentials, service principals, connection strings, keys, SAS tokens, deployment outputs, logs with customer data, and private topology details out of prompts, commits, issue comments, screenshots, and shared reports. Review Microsoft, MCP host, model provider, and organization retention policies before routing production telemetry, cost data, or customer-sensitive resource context through an agent.
Prerequisites
  • Coding assistant or skill host that can consume Agent Skills, or a local terminal where `uvx google-agents-cli setup` can install the CLI plus skills.
  • Python 3.11+, uv, and Node.js for the documented setup flow.
  • Google Cloud project, billing, credentials, APIs, IAM, region, and deployment target decisions when moving beyond local development.
  • Clear agent requirements before scaffolding: purpose, external APIs, tools, safety constraints, data sources, and deployment preference.
  • AI coding assistant or skill host compatible with the Agent Skills standard and the skills CLI.
  • Google Cloud project, credentials, billing, enabled APIs, IAM roles, and target region when a selected skill touches cloud resources.
  • Current gcloud, bq, kubectl, Terraform, SDK, or product-specific tooling required by the selected Google Cloud workflow.
  • Clear approval boundary before any agent runs cloud deployment, IAM, data, billing, registry, or destructive operations.
  • An Agent Skills compatible host or local installer that can install GitHub-hosted skills.
  • A Vercel, React, Next.js, React Native, design-review, writing-review, or deployment task where Vercel's guidance applies.
  • Vercel CLI and an authenticated account or token only for skills that deploy, inspect, or optimize a Vercel project.
  • Explicit approval before an agent commits, pushes, deploys, links a project, modifies environment variables, or runs account-scoped Vercel commands.
  • Azure account or subscription appropriate for the target work.
  • Node.js 18 or newer with `npx` available, because the included MCP configuration launches `@azure/mcp` through npx.
  • Azure CLI installed and authenticated with `az login` for live Azure resource work.
  • Azure Developer CLI installed and authenticated with `azd auth login` for azd deployment workflows.
Install
npx skills add google/agents-cli
npx skills add google/skills
npx skills add vercel-labs/agent-skills
apm install microsoft/azure-skills
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.