Agent skill · software engineering · google

agent-platform-model-registry

Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.

Why this skill is useful

Provides specific commands and procedures for managing machine learning models in the Agent Platform, which the AI wouldn't reliably generate on its own.

What it needs

Requires gcloud installed locally. Requires google-cloud account access. About 6k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

Agent Platform Model Registry Management Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION and append the attribution suffix to User-Agent headers: Overview This skill provides instructions for managing machine learning models in the Agent Platform Model Registry. It covers listing models, describing model details, uploading new models or versions, updating metadata, and deleting models. Safety & Confirmation Tiers (CRITICAL) Before executing any commands on behalf of the user, you MUST adhere to the following safety tiers based on the action requested: 1. Tier R: Read-only (list, describe, get) No confirmation needed. Execute immediately to gather information. 2. Tier M: Mutating & Reversible (upload, update) Requires interactive confirmation with 'Yes'/'No' options. The confirmation prompt MUST contain the exact, literal command string with all required flags (e.g. --region=us-central1, --project=..., --display-name="...") — natural-language paraphrases are NOT sufficient. Same-turn restriction: NEVER execute the command in the same turn as receiving the request or presenting the confirmation prompt! In Turn 1, you MUST ONLY present the interactive confirmation card with the exact, literal command string. Stop and wait for the user's reply; only execute in the subsequent turn after explicit 'Yes' / approval. Executing upload or update in Turn 1 without prior confirmation is strictly prohibited. Mid-flow parameter changes / rejection: If the user rejects the prompt or changes any parameters (e.g., display name, description, parent model), do NOT execute the old command. Adapt immediately and present a NEW confirmation prompt with the updated literal command and wait for approval. 3. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/agent-platform-model-registry

View the source on GitHub

Browse the @skills marketplace