google-agents-cli-publish

Name: google-agents-cli-publish
Author: google

bygoogle· 116 skills

Installs

65k

Stars

5.4k

Forks

565

How to install google-agents-cli-publish?

google/agents-cli/google-agents-cli-publish

$npx -y skills add google/agents-cli --skill google-agents-cli-publish

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Use this skill

Run `npx skills use "https://github.com/google/agents-cli" --skill "google/agents-cli/google-agents-cli-publish"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the whole pack

Use the skills in "https://github.com/google/agents-cli" that are relevant to the current task. Run `npx skills add "https://github.com/google/agents-cli"` and select the relevant skills, then follow their instructions.

Files · 1

View on GitHub

SKILL.md

1	# Gemini Enterprise Registration
2
3	> Requires: A deployed agent. For Agent Runtime, `deployment_metadata.json` (created by `agents-cli deploy`) enables auto-detection. For Cloud Run or GKE, provide the agent card URL and flags directly.
4
5	## Prerequisites
6
7	1. Agent must be deployed — the agent must be running and reachable
8	2. Gemini Enterprise app must exist — Create one in Google Cloud Console → Gemini Enterprise → Apps before registering
9	3. `deployment_metadata.json` (Agent Runtime only) — Created automatically by `agents-cli deploy`; contains the agent runtime ID, deployment target, the A2A flag, and the agent directory
10
11	## Required Permissions for A2A on Cloud Run
12
13	- `roles/run.servicesInvoker` granted to the Discovery Engine service account (`service-<PROJECT_NUMBER>@gcp-sa-discoveryengine.iam.gserviceaccount.com`) on the Cloud Run service.
14
15	---
16
17	## Registration Modes
18
19	### A2A Registration (Cloud Run / GKE)
20
21	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`.
22
23	```bash
24	# A2A on Cloud Run / GKE
25	agents-cli publish gemini-enterprise \
26	--agent-card-url https://my-service-abc123.us-east1.run.app/a2a/app/.well-known/agent-card.json \
27	--gemini-enterprise-app-id projects/123456/locations/global/collections/default_collection/engines/my-app
28	```
29
30	Pass `--display-name` / `--description` to override the card defaults. For Agent Runtime, use ADK registration (below).
31
32	### ADK Registration (default on Agent Runtime)
33
34	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. Under the hood, `:streamQuery` dispatches to the `AdkApp`'s `streaming_agent_run_with_events` method — when debugging an ADK invocation, search the runtime's `reasoning_engine_stderr` logs for that method name to trace the failure. 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.
35
36	```bash
37	agents-cli publish gemini-enterprise \
38	--registration-type adk \
39	--agent-runtime-id projects/123456/locations/us-east1/reasoningEngines/789 \
40	--gemini-enterprise-app-id projects/123456/locations/global/collections/default_collection/engines/my-app \
41	--display-name "My Agent" \
42	--description "Handles customer queries" \
43	--tool-description "Answers questions about products"
44	```
45
46	---
47
48	## Programmatic Mode (CI/CD)
49
50	The command is non-interactive by default — pass all required values via flags or environment variables. This makes it safe for CI/CD pipelines.
51
52	### Via flags
53
54	```bash
55	agents-cli publish gemini-enterprise \
56	--agent-runtime-id "$AGENT_RUNTIME_ID" \
57	--gemini-enterprise-app-id "$GEMINI_ENTERPRISE_APP_ID" \
58	--display-name "Production Agent" \
59	--registration-type adk
60	```
61
62	### Via environment variables
63
64	Most flags have an env var alternative (`--metadata-file`, `--interactive`, and `--list` do not):
65
66	```bash
67	export AGENT_RUNTIME_ID="projects/123456/locations/us-east1/reasoningEngines/789"
68	export GEMINI_ENTERPRISE_APP_ID="projects/123456/locations/global/collections/default_collection/engines/my-app"
69	export GEMINI_DISPLAY_NAME="Production Agent"
70	export GEMINI_DESCRIPTION="Handles customer queries"
71
72	agents-cli publish gemini-enterprise
73	```
74
75	---
76
77	## Interactive Mode (`--interactive`)
78
79	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.
80
81	```bash
82	agents-cli publish gemini-enterprise --interactive
83	```
84
85	---
86
87	## Complete Flag Reference
88
89	\| Flag \| Env Var \| Description \|
90	\|------\|---------\|-------------\|
91	\| `--agent-runtime-id` \| `AGENT_RUNTIME_ID` \| Agent Runtime resource name (auto-detected from `deployment_metadata.json`) \|
92	\| `--gemini-enterprise-app-id` \| `ID` or `GEMINI_ENTERPRISE_APP_ID` \| Gemini Enterprise app full resource name \|
93	\| `--display-name` \| `GEMINI_DISPLAY_NAME` \| Display name in Gemini Enterprise \|
94	\| `--description` \| `GEMINI_DESCRIPTION` \| Agent description \|
95	\| `--tool-description` \| `GEMINI_TOOL_DESCRIPTION` \| Tool description (ADK mode only, defaults to description) \|
96	\| `--registration-type` \| `REGISTRATION_TYPE` \| `adk` or `a2a` (defaults to `adk` on Agent Runtime, `a2a` on Cloud Run / GKE) \|
97	\| `--agent-card-url` \| `AGENT_CARD_URL` \| Agent card URL for A2A registration \|
98	\| `--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) \|
99	\| `--project-id` \| `GOOGLE_CLOUD_PROJECT` \| GCP project ID for billing \|
100	\| `--project-number` \| `PROJECT_NUMBER` \| GCP project number (used for Gemini Enterprise lookup) \|
101	\| `--authorization-id` \| `GEMINI_AUTHORIZATION_ID` \| OAuth authorization resource name \|
102	\| `--metadata-file` \| — \| Path to deployment metadata (default: `deployment_metadata.json`) \|
103	\| `--interactive` / `-i` \| — \| Enable interactive prompts \|
104	\| `--list` \| — \| List Gemini Enterprise apps in the current project and exit \|
105
106	---
107
108	## Auto-Detection from Metadata
109
110	When `deployment_metadata.json` exists, the command automatically:
111
112	- Reads the agent runtime ID (`remote_agent_runtime_id`)
113	- 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`.
114	- Determines the deployment target for authentication
115
116	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:
117
118	```bash
119	agents-cli publish gemini-enterprise \
120	--gemini-enterprise-app-id projects/123456/locations/global/collections/default_collection/engines/my-app
121	```
122
123	---
124
125	## SDK Compatibility
126
127	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.
128
129	---
130
131	## Managing Agents in Agent Registry
132
133	Agent Registry (Preview) is the Google Cloud fleet-wide record of your agents.
134	Agents deployed to a managed runtime (Agent Runtime on Gemini Enterprise
135	Agent Platform) are auto-registered — no extra step after `agents-cli deploy`.
136	Manage them with `gcloud` (requires `roles/agentregistry.editor`):
137
138	```bash
139	# List / filter
140	gcloud alpha agent-registry agents list --project PROJECT --location LOCATION
141	gcloud alpha agent-registry agents list --filter="displayName:my-agent"
142
143	# Inspect
144	gcloud alpha agent-registry agents describe AGENT_NAME
145
146	# Update endpoint/metadata — edit the Service resource, not the Agent
147	gcloud alpha agent-registry services update AGENT_NAME \
148	--display-name "..." --description "..." \
149	--interfaces "url=ENDPOINT_URL,protocol=HTTP_JSON"
150
151	# Remove: delete the underlying runtime agent (auto-registered) OR, for
152	# manually registered agents, delete the Service resource
153	gcloud alpha agent-registry services delete AGENT_NAME
154	```
155
156	Docs: https://docs.cloud.google.com/agent-registry/manage-agents
157
158	---
159
160	## Troubleshooting
161
162	\| Issue \| Solution \|
163	\|-------\|----------\|
164	\| "Session not found" after registration \| SDK version issue — upgrade `google-cloud-aiplatform` (see SDK Compatibility above), redeploy, then re-register \|
165	\| `--registration-type is required` \| Non-interactive mode needs `--registration-type` when no `deployment_metadata.json` exists \|
166	\| "Gemini Enterprise App ID is required" \| Provide `--gemini-enterprise-app-id` or set the `ID` / `GEMINI_ENTERPRISE_APP_ID` env var \|
167	\| Re-publishing the same agent \| Registration is idempotent — re-running updates the existing registration in place instead of creating a duplicate \|
168	\| HTTP 403 on registration \| Check that your account has Discovery Engine Editor permissions on the Gemini Enterprise project \|
169	\| Debugging ADK invocation failures on Agent Runtime \| Gemini Enterprise calls the agent via the `AdkApp`'s `streaming_agent_run_with_events` method (the native `:streamQuery` contract). Grep the runtime's `reasoning_engine_stderr` logs for `streaming_agent_run_with_events` to find the underlying error \|
170	\| "Could not fetch agent card" \| Verify the agent is running and the URL is correct; for Cloud Run, ensure `gcloud auth login` is done \|
171
172	---
173
174	## Related Skills
175
176	- `/google-agents-cli-deploy` — Deployment targets, CI/CD pipelines, and production workflows (also covers Agent Gateway governed ingress/egress and Semantic Governance awareness)
177	- `/google-agents-cli-workflow` — Development workflow, coding guidelines, and operational rules
178	- `/google-agents-cli-scaffold` — Project creation and enhancement with `agents-cli scaffold create` / `scaffold enhance`

6 picks

Type

Run `npx skills use "https://github.com/google/agents-cli" --skill "google/agents-cli/google-agents-cli-publish"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the skills in "https://github.com/google/agents-cli" that are relevant to the current task. Run `npx skills add "https://github.com/google/agents-cli"` and select the relevant skills, then follow their instructions.

google-agents-cli-publish

How to install google-agents-cli-publish?

Related

google-agents-cli-publish

How to install google-agents-cli-publish?

Related