Deploying
GoogleCloudPlatform/race-condition
Guides deployment of Race Condition to a GCP project. An agent skill from GoogleCloudPlatform/race-condition.
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the…
Install Google Agents CLI Publish
$ npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pifferologo/cloud-agents-cli google-agents-cli-publish --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pifferologo/cloud-agents-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/google-agents-cli-publish .claude/skills/google-agents-cli-publish && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "google-agents-cli-publish" agent skill from https://github.com/pifferologo/cloud-agents-cli/tree/main/skills/google-agents-cli-publish into .claude/skills/google-agents-cli-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-agents-cli-publish", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pifferologo/cloud-agents-cli/tree/main/skills/google-agents-cli-publishType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pifferologo/cloud-agents-cli google-agents-cli-publish --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pifferologo/cloud-agents-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/google-agents-cli-publish .agents/skills/google-agents-cli-publish && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "google-agents-cli-publish" agent skill from https://github.com/pifferologo/cloud-agents-cli/tree/main/skills/google-agents-cli-publish into .agents/skills/google-agents-cli-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-agents-cli-publish", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pifferologo/cloud-agents-cli google-agents-cli-publish --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pifferologo/cloud-agents-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/google-agents-cli-publish .cursor/skills/google-agents-cli-publish && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "google-agents-cli-publish" agent skill from https://github.com/pifferologo/cloud-agents-cli/tree/main/skills/google-agents-cli-publish into .cursor/skills/google-agents-cli-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-agents-cli-publish", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pifferologo/cloud-agents-cli.git --path skills/google-agents-cli-publish--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pifferologo/cloud-agents-cli google-agents-cli-publish --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pifferologo/cloud-agents-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/google-agents-cli-publish .gemini/skills/google-agents-cli-publish && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "google-agents-cli-publish" agent skill from https://github.com/pifferologo/cloud-agents-cli/tree/main/skills/google-agents-cli-publish into .gemini/skills/google-agents-cli-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-agents-cli-publish", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pifferologo/cloud-agents-cli google-agents-cli-publishInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pifferologo/cloud-agents-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/google-agents-cli-publish .github/skills/google-agents-cli-publish && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "google-agents-cli-publish" agent skill from https://github.com/pifferologo/cloud-agents-cli/tree/main/skills/google-agents-cli-publish into .github/skills/google-agents-cli-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-agents-cli-publish", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pifferologo/cloud-agents-cli google-agents-cli-publish --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pifferologo/cloud-agents-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/google-agents-cli-publish .opencode/skills/google-agents-cli-publish && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "google-agents-cli-publish" agent skill from https://github.com/pifferologo/cloud-agents-cli/tree/main/skills/google-agents-cli-publish into .opencode/skills/google-agents-cli-publish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-agents-cli-publish", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
google-agents-cli-publish- GitHub stars
- 129
- Used in
- 1 other repo
- Token cost
- ~2.4k tokens
- SKILL.md length
- 768 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the…
- Works in 3 steps: Agent must be deployed — the agent must… → Gemini Enterprise app must exist —… → deployment_metadata.json (Agent Runtime…
- Wants to publish an agent
- SKILL.md covers Prerequisites, Required Permissions for A2A…, Registration Modes and Programmatic Mode (CI/CD), plus 7 more sections
- Calls gcloud
What it does
Google Agents CLI Publish is an agent skill from pifferologo/cloud-agents-cli. This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the agents-cli publish gemini-enterprise command. Also use when the user wants to "manage agents in Agent Registry" or "list/update/delete registered agents". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Deployment. It works with Cloud Run, Google Kubernetes Engine and Google Cloud. The repository describes itself as: google cloud agent cli for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from piffer labs. The licence is Apache-2.0.
When your agent uses it
- Wants to publish an agent
- Publish my ADK agent
- Register an agent with Gemini Enterprise
- Publish to Gemini Enterprise
Example prompts
- “publish an agent”
- “publish my ADK agent”
- “register an agent with Gemini Enterprise”
- “/google-agents-cli-publish”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Agent must be deployed — the agent must be running and reachable
- Gemini Enterprise app must exist — Create one in Google Cloud Console → Gemini Enterprise → Apps before registering
- deployment_metadata.json (Agent Runtime only) — Created automatically by agents-cli deploy; contains the agent runtime ID, deployment…
What it can do on your machine
Read from SKILL.md and the folder at commit 5957f5a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gcloud
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.cloud.google.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Google Agents CLI Publish loads about 2.4k tokens when it runs. Until then it costs about 170 tokens; SKILL.md has 768 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pifferologo/cloud-agents-cli at commit 5957f5a, republished under its Apache-2.0 licence (© pifferologo). 768 words, ~2,398 tokens.
Download SKILL.mdSave it as
.claude/skills/google-agents-cli-publish/SKILL.md (or your agent's skills folder).- name
- google-agents-cli-publish
- description
- This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the agents-cli publish gemini-enterprise command. Also use when the user wants to "manage agents in Agent Registry" or "list/update/delete registered agents". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the Google ADK (Agent Development Kit) skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
- metadata.author
- metadata.license
- Apache-2.0
- metadata.version
- 0.6.1
Gemini Enterprise Registration
Requires: A deployed agent. For Agent Runtime,
deployment_metadata.json(created byagents-cli deploy) enables auto-detection. For Cloud Run or GKE, provide the agent card URL and flags directly.
Prerequisites
- Agent must be deployed — the agent must be running and reachable
- Gemini Enterprise app must exist — Create one in Google Cloud Console → Gemini Enterprise → Apps before registering
deployment_metadata.json(Agent Runtime only) — Created automatically byagents-cli deploy; contains the agent runtime ID, deployment target, the A2A flag, and the agent directory
Required Permissions for A2A on Cloud Run
roles/run.servicesInvokergranted to the Discovery Engine service account (service-<PROJECT_NUMBER>@gcp-sa-discoveryengine.iam.gserviceaccount.com) on the Cloud Run service.
Registration Modes
A2A Registration (Cloud Run / GKE)
Every scaffolded agent serves the Agent-to-Agent protocol. A2A is the default — and only — registration type on Cloud Run and GKE, which have no reasoning engine, so Gemini Enterprise registers them over A2A. Pass the agent card URL and the command fetches the card and registers it; display name and description default to the card's name/description.
# A2A on Cloud Run / GKE
agents-cli publish gemini-enterprise \
--agent-card-url https://my-service-abc123.us-east1.run.app/a2a/app/.well-known/agent-card.json \
--gemini-enterprise-app-id projects/123456/locations/global/collections/default_collection/engines/my-appPass --display-name / --description to override the card defaults. For Agent Runtime, use ADK registration (below).
ADK Registration (default on Agent Runtime)
This is the default and recommended registration for Agent Runtime deployments: Gemini Enterprise invokes the agent natively via :streamQuery on its reasoning engine resource, authenticating end-to-end. It's also the path to use when the agent needs an OAuth authorization (--authorization-id). The agent is registered directly via its reasoning engine resource name; no agent card URL is needed.
agents-cli publish gemini-enterprise \
--registration-type adk \
--agent-runtime-id projects/123456/locations/us-east1/reasoningEngines/789 \
--gemini-enterprise-app-id projects/123456/locations/global/collections/default_collection/engines/my-app \
--display-name "My Agent" \
--description "Handles customer queries" \
--tool-description "Answers questions about products"Programmatic Mode (CI/CD)
The command is non-interactive by default — pass all required values via flags or environment variables. This makes it safe for CI/CD pipelines.
Via flags
agents-cli publish gemini-enterprise \
--agent-runtime-id "$AGENT_RUNTIME_ID" \
--gemini-enterprise-app-id "$GEMINI_ENTERPRISE_APP_ID" \
--display-name "Production Agent" \
--registration-type adkVia environment variables
Most flags have an env var alternative (--metadata-file, --interactive, and --list do not):
export AGENT_RUNTIME_ID="projects/123456/locations/us-east1/reasoningEngines/789"
export GEMINI_ENTERPRISE_APP_ID="projects/123456/locations/global/collections/default_collection/engines/my-app"
export GEMINI_DISPLAY_NAME="Production Agent"
export GEMINI_DESCRIPTION="Handles customer queries"
agents-cli publish gemini-enterpriseInteractive Mode (--interactive)
Pass --interactive (or -i) to be guided through any missing values with interactive prompts. The command will list available Gemini Enterprise apps, offer to auto-detect the agent runtime ID from metadata, and prompt for display name and description.
agents-cli publish gemini-enterprise --interactiveComplete Flag Reference
| Flag | Env Var | Description |
|---|---|---|
--agent-runtime-id | AGENT_RUNTIME_ID | Agent Runtime resource name (auto-detected from deployment_metadata.json) |
--gemini-enterprise-app-id | ID or GEMINI_ENTERPRISE_APP_ID | Gemini Enterprise app full resource name |
--display-name | GEMINI_DISPLAY_NAME | Display name in Gemini Enterprise |
--description | GEMINI_DESCRIPTION | Agent description |
--tool-description | GEMINI_TOOL_DESCRIPTION | Tool description (ADK mode only, defaults to description) |
--registration-type | REGISTRATION_TYPE | adk or a2a (defaults to adk on Agent Runtime, a2a on Cloud Run / GKE) |
--agent-card-url | AGENT_CARD_URL | Agent card URL for A2A registration |
--deployment-target | DEPLOYMENT_TARGET | agent_runtime, cloud_run, or gke (sets the default registration type — ADK on Agent Runtime, A2A on Cloud Run / GKE — and the A2A auth method) |
--project-id | GOOGLE_CLOUD_PROJECT | GCP project ID for billing |
--project-number | PROJECT_NUMBER | GCP project number (used for Gemini Enterprise lookup) |
--authorization-id | GEMINI_AUTHORIZATION_ID | OAuth authorization resource name |
--metadata-file | — | Path to deployment metadata (default: deployment_metadata.json) |
--interactive / -i | — | Enable interactive prompts |
--list | — | List Gemini Enterprise apps in the current project and exit |
Show full SKILL.md (297 more words)Show less
Auto-Detection from Metadata
When deployment_metadata.json exists, the command automatically:
- Reads the agent runtime ID (
remote_agent_runtime_id) - Determines the registration type: defaults to ADK (native
:streamQuery) on Agent Runtime, and A2A on Cloud Run / GKE (which have no reasoning engine). Override with--registration-type. - Determines the deployment target for authentication
This means that for the simplest case (an agent on Agent Runtime, registered as ADK), you only need to provide the Gemini Enterprise app ID:
agents-cli publish gemini-enterprise \
--gemini-enterprise-app-id projects/123456/locations/global/collections/default_collection/engines/my-appSDK Compatibility
Agent Runtime deployments may encounter "Session not found" errors with google-cloud-aiplatform versions <= 1.128.0. In interactive mode (--interactive), the command checks the SDK version from uv.lock and offers to upgrade. In programmatic mode, ensure your SDK is up to date before registering.
Managing Agents in Agent Registry
Agent Registry (Preview) is the Google Cloud fleet-wide record of your agents.
Agents deployed to a managed runtime (Agent Runtime on Gemini Enterprise
Agent Platform) are auto-registered — no extra step after agents-cli deploy.
Manage them with gcloud (requires roles/agentregistry.editor):
# List / filter
gcloud alpha agent-registry agents list --project PROJECT --location LOCATION
gcloud alpha agent-registry agents list --filter="displayName:my-agent"
# Inspect
gcloud alpha agent-registry agents describe AGENT_NAME
# Update endpoint/metadata — edit the Service resource, not the Agent
gcloud alpha agent-registry services update AGENT_NAME \
--display-name "..." --description "..." \
--interfaces "url=ENDPOINT_URL,protocol=HTTP_JSON"
# Remove: delete the underlying runtime agent (auto-registered) OR, for
# manually registered agents, delete the Service resource
gcloud alpha agent-registry services delete AGENT_NAMEDocs: https://docs.cloud.google.com/agent-registry/manage-agents
Troubleshooting
| Issue | Solution |
|---|---|
| "Session not found" after registration | SDK version issue — upgrade google-cloud-aiplatform (see SDK Compatibility above), redeploy, then re-register |
--registration-type is required | Non-interactive mode needs --registration-type when no deployment_metadata.json exists |
| "Gemini Enterprise App ID is required" | Provide --gemini-enterprise-app-id or set the ID / GEMINI_ENTERPRISE_APP_ID env var |
| Re-publishing the same agent | Registration is idempotent — re-running updates the existing registration in place instead of creating a duplicate |
| HTTP 403 on registration | Check that your account has Discovery Engine Editor permissions on the Gemini Enterprise project |
| "Could not fetch agent card" | Verify the agent is running and the URL is correct; for Cloud Run, ensure gcloud auth login is done |
Related Skills
/google-agents-cli-deploy— Deployment targets, CI/CD pipelines, and production workflows/google-agents-cli-workflow— Development workflow, coding guidelines, and operational rules/google-agents-cli-scaffold— Project creation and enhancement withagents-cli scaffold create/scaffold enhance
© pifferologo, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/google-agents-cli-publish of pifferologo/cloud-agents-cli.
Open the folder on GitHubat commit 5957f5a
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in pifferologo/cloud-agents-cli, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Google Agents CLI Publish next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Google Agents CLI Publish this skillpifferologo/cloud-agents-cli | 129 | 1 repos | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| DeployingGoogleCloudPlatform/race-condition | 234 | — | ~3k | Automated safety check: Pass | Custom licence | |
| Google Cloud Solution Guided Gke AI Migrationgoogle/skills | 21k | — | ~8.3k | Automated safety check: Pass | Apache-2.0 | |
| Google Cloud Agent SDK Masterjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Devopsnicepkg/auto-company | 194 | 2 repos | ~814 | Automated safety check: Pass | MIT | |
| Broccoli Oss GCP Deploybesimple-oss/broccoli | 286 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Google Cloud Solution Guided Gke AI Migration
google/skills
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl.
Google Cloud Agent SDK Master
jeremylongshore/tons-of-skills-marketplace
Build, evaluate, deploy, publish, or modernize Google ADK agent applications with Google's maintained agents-cli workflow.
Devops
nicepkg/auto-company
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm).
Broccoli Oss GCP Deploy
besimple-oss/broccoli
Deploy this repository to a new Google Cloud project using the repo's existing Cloud Run, Cloud Run Jobs, Cloud SQL, Secret Manager, and Artifact Registry scripts.
Kcli Cluster Deployment
karmab/kcli
Guides deployment and management of Kubernetes clusters with kcli.
More from pifferologo/cloud-agents-cli
Google Agents CLI Adk Code
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management", or needs ADK (Agent…
Google Agents CLI Observability
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "set up tracing", "monitor my ADK agent", "configure logging", "add observability", "debug production traffic", or needs guidance on monitoring…
Google Agents CLI Scaffold
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or…
Google Agents CLI Deploy
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud…
Google Agents CLI Eval
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs…
Google Agents CLI Workflow
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "deploy an agent", "publish an agent"…
Related
Categories
Questions about Google Agents CLI Publish
What does Google Agents CLI Publish do?
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the…. Google Agents CLI Publish is an agent skill from pifferologo/cloud-agents-cli. This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the agents-cli publish gemini-enterprise command.
When should I use Google Agents CLI Publish?
Google Agents CLI Publish fits situations like: wants to publish an agent; publish my ADK agent; register an agent with Gemini Enterprise; publish to Gemini Enterprise.
How do I install Google Agents CLI Publish in Claude Code?
Run `npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a claude-code`. Or copy the skill folder (skills/google-agents-cli-publish in pifferologo/cloud-agents-cli) into .claude/skills/google-agents-cli-publish in your project. Claude Code loads it when a task matches its description.
How do I install Google Agents CLI Publish in Codex?
Run `npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a codex`. Or copy the skill folder (skills/google-agents-cli-publish in pifferologo/cloud-agents-cli) into .agents/skills/google-agents-cli-publish in your project. Codex loads it when a task matches its description.
Can I use Google Agents CLI Publish in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pifferologo/cloud-agents-cli --skill google-agents-cli-publish -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-agents-cli-publish, .gemini/skills/google-agents-cli-publish, .github/skills/google-agents-cli-publish and .opencode/skills/google-agents-cli-publish in your project.
What does Google Agents CLI Publish need to run?
Going by SKILL.md and its folder, Google Agents CLI Publish needs the command-line tools its instructions call (gcloud).
Does Google Agents CLI Publish access the network?
SKILL.md names 1 domain. As links in the text: docs.cloud.google.com. This is read from the text; nothing was executed.
Is Google Agents CLI Publish safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Google Agents CLI Publish use?
Google Agents CLI Publish is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Google Agents CLI Publish use?
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Google Agents CLI Publish?
Skills that share tags, products or a category with Google Agents CLI Publish: Deploying (GoogleCloudPlatform/race-condition, 234 stars), Google Cloud Solution Guided Gke AI Migration (google/skills, 21k stars), Google Cloud Agent SDK Master (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Devops (nicepkg/auto-company, 194 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Google Agents CLI Publish?
pifferologo (a GitHub user) maintains it in pifferologo/cloud-agents-cli, which has 129 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 3, 2026.
Source: pifferologo/cloud-agents-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.