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 endpoints or for running model evaluations.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Agent Platform Endpoint Management when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Agent Platform Endpoint Management when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/agent-platform-endpoint-management # Save SKILL.md to ~/.claude/skills/agent-platform-endpoint-management/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/agent-platform-endpoint-management/SKILL.md. For a shared project, commit the folder at .claude/skills/agent-platform-endpoint-management/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Agent Platform Endpoint Management skill for this task: Use Agent Platform Endpoint Management when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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:
```bash gcloud auth login gcloud auth application-default login ```
2. **Set Project**: Configure the active project for subsequent commands:
```bash 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.
```bash gcloud ai endpoints list \ --region=$LOCATION_ID ```
*(Optional)* To bound the result, use `--limit=$LIMIT`; `--page-size=$PAGE_SIZE` controls API chunking only and does NOT limit the total output. Use `--page-token=$PAGE_TOKEN` to continue from a previous batch.
> [!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.
```bash gcloud ai endpoints describe $ENDPOINT_ID \ --region=$LOCATION_ID ```
The models deployed on an endpoint are its `deployedModels` in this output. In the Python SDK they are `endpoint.gca_resource.deployed_models`; `aiplatform.Endpoint` has no `deployed_models` attribute.
## 3. Creating an Endpoint (Tier M)
Create a new endpoint resource. The parent resource is the location. **Action requires an inline confirmation card before proceeding.**
```bash gcloud ai endpoints create \ --region=$LOCATION_ID \ --display-name="my-endpoint" ```
The command has no `--asynchronous` flag: it waits for the operation and prints the new endpoint's resource name, whose last segment is the endpoint ID.
> [!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.**
```bash 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.**
```bash 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.**
```bash # 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 Exceeded**: Verify the region's endpoint quota in the Cloud Console. - **Resource Busy**: If a deletion fails, check if models are still being undeployed.
Intended uses
- Use Agent Platform Endpoint Management when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.