/agent-platform-endpoint-management
Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to
$ npx -y skills add google/skills --skill agent-platform-endpoint-management --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/agent-platform-endpoint-management
Context preview
The summary Claude sees to decide when to auto-load this skill.
Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to
SKILL.md
agent-platform-endpoint-management.SKILL.mdname: agent-platform-endpoint-management
metadata:
category: AiAndMachineLearning
description: >-
Manages Agent Platform serving endpoints. Use when you need to create, list,
describe, update, or delete serving endpoints for model deployment on Agent
Platform. Also use when troubleshooting endpoint permission, quota, or resource
busy errors. Don't use for deploying models to endpoints or for running
model evaluations.
Agent Platform Endpoint Management
Overview
This skill provides procedural knowledge for managing Agent Platform Endpoints. Endpoints are logical serving hosts that provide a stable URL for online predictions. You must create an endpoint before you can deploy a model to it.
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 (`create`, `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`, `--display-name="..."`) — natural-language paraphrases are NOT sufficient.
- **Same-turn restriction**: NEVER execute the command in the same turn as
presenting the confirmation prompt. Stop and wait for the user's reply; only execute after explicit 'Yes' / approval. 3. **Tier D: Destructive & Irreversible (`delete`)**
- Requires **explicit typed confirmation** (e.g. "I confirm" or "Yes,
delete it"). Ask for confirmation IMMEDIATELY — before any pre-flight checks (don't `describe` first, don't check if the endpoint is empty first).
- **Same-turn restriction**: NEVER execute in the same turn as asking for
typed confirmation. Wait for the user to reply in a new turn.
Phase 0: Environment Setup
**CRITICAL**: Before running any commands, you MUST ensure the environment is correctly initialized by following these steps:
1. **Google Cloud Authentication**: Authenticate with your Google Cloud credentials and configure active Application Default Credentials (ADC) for Agent Platform access:
gcloud auth login
gcloud auth application-default login2. **Set Project**: Configure the active project for subsequent commands:
gcloud config set project $PROJECT_ID
3. **Region**: Always specify `--region=$LOCATION_ID` on each command below. Do NOT use `global`. Ask the user to specify the region if not provided.
1. Listing Endpoints (Tier R)
Use this command to discover existing endpoints in a specific region and retrieve their IDs. No confirmation is required.
gcloud ai endpoints list \
--region=$LOCATION_ID*(Optional)* For pagination, you MUST use `--limit=$LIMIT` to restrict the total number of returned endpoints. You can also append `--page-size=$PAGE_SIZE` to control API chunking, or `--page-token=$PAGE_TOKEN` for next pages.
> [!IMPORTANT] > > Always specify the `--region`. Do NOT use 'global'. Ask the user to specify if > not provided.
2. Describing an Endpoint (Tier R)
Retrieve the full metadata for a specific endpoint. No confirmation is required.
gcloud ai endpoints describe $ENDPOINT_ID \
--region=$LOCATION_ID3. Creating an Endpoint (Tier M)
Create a new endpoint resource. The parent resource is the location. **Action requires an inline confirmation card before proceeding.**
gcloud ai endpoints create \
--region=$LOCATION_ID \
--display-name="my-endpoint"> [!IMPORTANT] > > **You MUST seek interactive confirmation first.** Your confirmation prompt > **MUST** show the literal command string. For example: > > ```bash > gcloud ai endpoints create --region=$LOCATION_ID --display-name="my-endpoint" > ``` > > Or the exact flags. Do not execute this command in the same turn as proposing > the confirmation.
4. Updating an Endpoint (Tier M)
Update endpoint metadata such as display name or labels. **Action requires an inline confirmation card before proceeding.**
gcloud ai endpoints update $ENDPOINT_ID \
--region=$LOCATION_ID \
--display-name="new-display-name"Check if the endpoint exists first by either listing or describing the endpoint.
> [!IMPORTANT] > > **You MUST seek interactive confirmation first.** Your confirmation prompt > **MUST** show the literal command string. For example: > > ```bash > gcloud ai endpoints update $ENDPOINT_ID --region=$LOCATION_ID --display-name="new-display-name" > ``` > > Or the exact flags. **CRITICAL:** You are strictly prohibited from executing > this command in the same turn as asking for confirmation. When you ask for > confirmation, you MUST stop immediately and wait for the user to reply.
5. Deleting an Endpoint (Tier D)
Permanently delete an endpoint resource. **Action requires explicit typed confirmation before proceeding.**
gcloud ai endpoints delete $ENDPOINT_ID \
--region=$LOCATION_ID> [!WARNING] > > All models must be **undeployed** from the endpoint before it can be deleted. > Do not run `describe` until AFTER you have received typed confirmation to > delete.
6. Traffic Splitting (Tier M)
You can manage traffic split between different models deployed on the same endpoint during an update. **Action requires an inline confirmation card before proceeding.**
# Example: Deploying a model with a specific traffic split is usually done
# via 'gcloud ai endpoints deploy-model'.
Refer to the `agent-platform-deploy` skill for instructions on deploying and undeploying models.
Troubleshooting
- **403 Permission Denied**: Ensure `aiplatform.admin` or `owner` role is
assigned.
- **Quota Excee
Read more
name: agent-platform-endpoint-management metadata: category: AiAndMachineLearning description: >- Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to endpoints or for running model evaluations.
Agent Platform Endpoint Management
Overview
This skill provides procedural knowledge for managing Agent Platform Endpoints. Endpoints are logical serving hosts that provide a stable URL for online predictions. You must create an endpoint before you can deploy a model to it.
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 (`create`, `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`, `--display-name="..."`) — natural-language paraphrases are NOT sufficient.
- **Same-turn restriction**: NEVER execute the command in the same turn as
presenting the confirmation prompt. Stop and wait for the user's reply; only execute after explicit 'Yes' / approval. 3. **Tier D: Destructive & Irreversible (`delete`)**
- Requires **explicit typed confirmation** (e.g. "I confirm" or "Yes,
delete it"). Ask for confirmation IMMEDIATELY — before any pre-flight checks (don't `describe` first, don't check if the endpoint is empty first).
- **Same-turn restriction**: NEVER execute in the same turn as asking for
typed confirmation. Wait for the user to reply in a new turn.
Phase 0: Environment Setup
**CRITICAL**: Before running any commands, you MUST ensure the environment is correctly initialized by following these steps:
1. **Google Cloud Authentication**: Authenticate with your Google Cloud credentials and configure active Application Default Credentials (ADC) for Agent Platform access:
gcloud auth login
gcloud auth application-default login2. **Set Project**: Configure the active project for subsequent commands:
gcloud config set project $PROJECT_ID
3. **Region**: Always specify `--region=$LOCATION_ID` on each command below. Do NOT use `global`. Ask the user to specify the region if not provided.
1. Listing Endpoints (Tier R)
Use this command to discover existing endpoints in a specific region and retrieve their IDs. No confirmation is required.
gcloud ai endpoints list \
--region=$LOCATION_ID*(Optional)* For pagination, you MUST use `--limit=$LIMIT` to restrict the total number of returned endpoints. You can also append `--page-size=$PAGE_SIZE` to control API chunking, or `--page-token=$PAGE_TOKEN` for next pages.
> [!IMPORTANT] > > Always specify the `--region`. Do NOT use 'global'. Ask the user to specify if > not provided.
2. Describing an Endpoint (Tier R)
Retrieve the full metadata for a specific endpoint. No confirmation is required.
gcloud ai endpoints describe $ENDPOINT_ID \
--region=$LOCATION_ID3. Creating an Endpoint (Tier M)
Create a new endpoint resource. The parent resource is the location. **Action requires an inline confirmation card before proceeding.**
gcloud ai endpoints create \
--region=$LOCATION_ID \
--display-name="my-endpoint"> [!IMPORTANT] > > **You MUST seek interactive confirmation first.** Your confirmation prompt > **MUST** show the literal command string. For example: > > ```bash > gcloud ai endpoints create --region=$LOCATION_ID --display-name="my-endpoint" > ``` > > Or the exact flags. Do not execute this command in the same turn as proposing > the confirmation.
4. Updating an Endpoint (Tier M)
Update endpoint metadata such as display name or labels. **Action requires an inline confirmation card before proceeding.**
gcloud ai endpoints update $ENDPOINT_ID \
--region=$LOCATION_ID \
--display-name="new-display-name"Check if the endpoint exists first by either listing or describing the endpoint.
> [!IMPORTANT] > > **You MUST seek interactive confirmation first.** Your confirmation prompt > **MUST** show the literal command string. For example: > > ```bash > gcloud ai endpoints update $ENDPOINT_ID --region=$LOCATION_ID --display-name="new-display-name" > ``` > > Or the exact flags. **CRITICAL:** You are strictly prohibited from executing > this command in the same turn as asking for confirmation. When you ask for > confirmation, you MUST stop immediately and wait for the user to reply.
5. Deleting an Endpoint (Tier D)
Permanently delete an endpoint resource. **Action requires explicit typed confirmation before proceeding.**
gcloud ai endpoints delete $ENDPOINT_ID \
--region=$LOCATION_ID> [!WARNING] > > All models must be **undeployed** from the endpoint before it can be deleted. > Do not run `describe` until AFTER you have received typed confirmation to > delete.
6. Traffic Splitting (Tier M)
You can manage traffic split between different models deployed on the same endpoint during an update. **Action requires an inline confirmation card before proceeding.**
# Example: Deploying a model with a specific traffic split is usually done # via 'gcloud ai endpoints deploy-model'.
Refer to the `agent-platform-deploy` skill for instructions on deploying and undeploying models.
Troubleshooting
- **403 Permission Denied**: Ensure `aiplatform.admin` or `owner` role is
assigned.
- **Quota Excee
This repository contains Agent Skills for Google products and technologies, including Google Cloud. This repository is under active development.
Repo: google/skills
Other skills on google-skills.
- /data-manager-api-audience-ingestion
Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its associated client libraries. Use this skill when the user wants to upload audience members, remove specific users, or clear/replace an
Open skill - /data-manager-api-event-ingestion
Guides developers through implementing event and conversion ingestion to Google products using the Data Manager API /v1/events/ingest endpoint and its associated client libraries. Use this skill when the user wants to upload offline conversions, enhanced conversions for leads,
Open skill - /data-manager-api-setup
Guides developers through client library installation and authentication setup steps for the Data Manager API. Use this skill when a user is getting started with the Data Manager API and needs to setup their local environment, install the client library, or setup access to the
Open skill - /google-ads-api-account-diagnostics
Diagnoses Google Ads account performance issues such as conversion loss (value or volume), low lead flow/volume, and lost impression share (opportunities) due to ad rank, bids, or budgets. Use when troubleshooting sudden performance drops, analyzing campaign impression share
Open skill - /google-ads-api-mcp-setup
Guides developers through downloading, configuring, and installing the official open-source Google Ads MCP Server. Use this skill when a user wants to connect their AI assistant (such as Gemini, Claude Code, or Cursor) to their Google Ads account to query campaigns or retrieve
Open skill - /google-ads-api-quickstart
Guides developers through Google Ads API quickstart: credential setup, choosing from 6 client libraries/REST, configuring environments, and running a "retrieve campaigns" script. Troubleshoots common setup errors: USER_PERMISSION_DENIED, login_customer_id issues, and
Open skill

