What problem does it solve? After deploying an ADK agent, connecting it to Gemini Enterprise requires choosing the right registration mode (ADK vs A2A), supplying the correct resource names, and handling authentication and SDK compatibility issues. This Skill guides the entire agents-cli publish gemini-enterprise workflow so registration succeeds on the first attempt. ## Core Features & Use Cases - Dual Registration Modes: Covers ADK registration (native :streamQuery on Agent Runtime) and A2A registration (agent card URL on Cloud Run or GKE), including when each applies. - Programmatic and Interactive Usage: Supports CI/CD pipelines via flags and environment variables, plus an --interactive mode that prompts for missing values and lists available Gemini Enterprise apps. - Auto-Detection and Fleet Management: Reads deployment_metadata.json to auto-detect the agent runtime ID and registration type, and documents Agent Registry management with gcloud alpha agent-registry commands. - Use Case: You deployed an agent to Agent Runtime and want it visible in your Gemini Enterprise app. This Skill walks you through running agents-cli publish gemini-enterprise with just the app ID, then troubleshooting any SDK or permission errors. ## Quick Start Ask the assistant to publish your deployed ADK agent to Gemini Enterprise using agents-cli with your Gemini Enterprise app ID.