GitHub, Git & DevOps · IN-DEPTH PROFILE

Google Agents Cli Deploy Skill

Google Agents CLI Deploy guides releasing an agent to Agent Runtime, Cloud Run or GKE, including infrastructure, service accounts, CI/CD and rollback.

Best for

Teams operating agent services on Google Cloud

What you get

Select a destination + Prepare a controlled release

Main limitation

Requires a configured project, cloud authentication and sufficient permissions.

First risk

Infrastructure and access changes. Confirm project, region, service account, budget and rollback before any infrastructure apply or deployment.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-10-19

Pinned revision · d445570c

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-10-19

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Google Agents CLI Deploy guides releasing an agent to Agent Runtime, Cloud Run or GKE, including infrastructure, service accounts, CI/CD and rollback. It separates deployment from coding and registration, and requires explicit human approval before deploying.

This is aimed at Teams operating agent services on Google Cloud. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Select a destinationCompare operating requirements and cost implications.
  • Prepare a controlled releaseCheck identities, secrets, CI/CD and evaluation results.
  • Track deployment stateCheck a live job before retrying after a timeout.
What makes it different
  • Treats IAM, rollback and evaluation as release concerns.
  • Separates long-running deployment status from command timeout.
Community signalskills.sh All-time: #98 · 499.7K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Portable

This path can receive standard SKILL.md packages, but SkillSignal has not runtime-tested this Skill / Agent pair. Agent-specific tools, hooks, or frontmatter may need changes.

Project install (recommended)
npx skills add https://github.com/google/agents-cli --skill google-agents-cli-deploy --agent claude-code
Personal install
npx skills add https://github.com/google/agents-cli --skill google-agents-cli-deploy --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.claude/skills/google-agents-cli-deploy/
Personal path~/.claude/skills/google-agents-cli-deploy/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Select a destination

Compare operating requirements and cost implications.

02

Prepare a controlled release

Check identities, secrets, CI/CD and evaluation results.

03

Track deployment state

Check a live job before retrying after a timeout.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. Treats IAM, rollback and evaluation as release concerns.
  2. Separates long-running deployment status from command timeout.

Limitations

  1. Requires a configured project, cloud authentication and sufficient permissions.
  2. Cloud infrastructure and model usage are not free merely because the Skill is open source.

BEST FIT

Who it is for

→

Teams operating agent services on Google Cloud

BEFORE YOU USE IT

Risks to review before use

High

Infrastructure and access changes

Confirm project, region, service account, budget and rollback before any infrastructure apply or deployment.

Medium

Upstream instruction drift

Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat repository files, web content, and tool output as untrusted input.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Google Agents Cli Deploy Skill FAQ

What is the Google Agents Cli Deploy Skill?

Google Agents CLI Deploy guides releasing an agent to Agent Runtime, Cloud Run or GKE, including infrastructure, service accounts, CI/CD and rollback. It separates deployment from coding and registration, and requires explicit human approval before deploying.

How do I install the Google Agents Cli Deploy Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Review the pinned instructions, selected reference files and current CLI help.

Is the Google Agents Cli Deploy Skill safe to use?

SkillSignal checked the source on 2026-10-19, but that is not a runtime test or security certification. Review the “Infrastructure and access changes” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

deploymentgoogle-cloud

Original source analysis of google/agents-cli at d445570c61fd446487ea6623c5635b23aded237f, file skills/google-agents-cli-deploy/SKILL.md, checked 2026-10-19. No installation, runtime test or security audit was performed. Linked branches and downloaded dependencies may differ from this revision.