Back to Skills

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.

14,351stars1,100forksUpdated 7/2/2026

Security Assessment

Safe(100/100)
Security Score100/100

About agent-platform-model-registry

Operational guidance for managing machine learning models in the Agent Platform Model Registry through the gcloud command line. It covers the full lifecycle of registry entries: listing models to discover their numeric IDs, describing a model or a specific version for full metadata, uploading new models or versions, updating metadata such as display name, description, and labels, and deleting a model and all of its versions. It is explicitly scoped away from model training, deployment to endpoints, and managing models outside the Agent Platform.

Safety is the organizing principle, expressed as three confirmation tiers. Tier R read-only actions like list and describe run immediately with no confirmation. Tier M mutating but reversible actions like upload and update require an interactive Yes or No confirmation whose prompt must contain the exact literal command string with all required flags, and must never execute in the same turn as the prompt. Tier D destructive actions, meaning delete, require explicit typed confirmation requested immediately, before any pre-flight checks, and also may not run in the same turn. These same-turn restrictions are stated as hard rules.

A required Phase 0 environment setup precedes any command: authenticating with gcloud auth login and configuring Application Default Credentials with gcloud auth application-default login, setting the active project, and always specifying the region on each command rather than using global. The commands themselves are standard gcloud ai models invocations for list, describe (including the model-at-version form), upload with flags such as container image URI and artifact URI, update, and delete. A note reminds that upload is a long-running operation and that all versions must be undeployed from endpoints before a model can be deleted.

FAQ

What model operations are supported?

Listing, describing a model or specific version, uploading new models or versions, updating metadata like display name, description, and labels, and deleting a model with all its versions.

What is explicitly out of scope?

Model training, deploying models to endpoints, and managing models that are not in the Agent Platform Model Registry.

How do the safety confirmation tiers work?

Tier R read-only runs immediately, Tier M upload and update need an interactive Yes or No confirmation showing the exact command, and Tier D delete needs explicit typed confirmation, with neither mutating tier allowed to execute in the same turn as its prompt.

What environment setup is required first?

Authenticate with gcloud auth login and gcloud auth application-default login, set the active project, and always pass the region on each command instead of using global.

What must happen before deleting a model?

All of the model's versions must be undeployed from all endpoints first, since deletion is irreversible and removes every version.

Install agent-platform-model-registry

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

google/skills