agent-platform-endpoint-management — Claude Code skill
Manages Agent Platform serving endpoints: create, list, describe, update, and delete resources. Useful for permission, quota, and resource-busy errors.
npx skills add google/skills --skill agent-platform-endpoint-management -a claude-codeWhat agent-platform-endpoint-management does
This skill guides endpoint administration in Agent Platform. It covers listing resources, reading endpoint metadata, creating endpoints, changing display names or labels, and deleting resources. An endpoint provides a stable host for online predictions before a model is deployed.
The procedures use gcloud ai endpoints list, describe, create, update, and delete. They also define confirmation rules for mutating and destructive actions. You need Google Cloud credentials, Application Default Credentials, an active project, and a region; commands use --region, and models must be undeployed before an endpoint is deleted. Troubleshooting covers 403 permission errors, quota limits, and busy resources.
Install it when your agent needs to administer endpoints. It is not the right fit for model deployment or model evaluations.
What it helps with
- create a serving endpoint in Agent Platform
- list endpoints in a specific region
- inspect endpoint metadata and deployedModels
- change an endpoint display name or labels
- troubleshoot permission, quota, or busy-resource errors
Example prompts for the agent
- List Agent Platform endpoints in `us-central1` with `gcloud ai endpoints list`.
- Describe endpoint `$ENDPOINT_ID` and explain the models shown in `deployedModels`.
- Prepare the command to create an endpoint with display name `my-endpoint`, then ask for confirmation first.
How to install agent-platform-endpoint-management
1Skills CLI (Vercel)
npx skills add google/skills --skill agent-platform-endpoint-management -a claude-code2Manually: put the files in place
~/.claude/skills/agent-platform-endpoint-management/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/agent-platform-endpoint-management/
1Skills CLI (Vercel)
npx skills add google/skills --skill agent-platform-endpoint-management -a codex2Manually: put the files in place
.agents/skills/agent-platform-endpoint-management/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/agent-platform-endpoint-management/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install google/skills agent-platform-endpoint-management2Manually: put the files in place
.github/skills/agent-platform-endpoint-management/SKILL.md1Skills CLI (Vercel)
npx skills add google/skills --skill agent-platform-endpoint-management -a gemini-cli2Platform CLI
gemini skills install https://github.com/google/skills --path skills/cloud/agent-platform-endpoint-managementManually: put the files in place
.devin/skills/agent-platform-endpoint-management/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set172
The whole set →Similar
Questions about agent-platform-endpoint-management
How do I install agent-platform-endpoint-management in Claude Code?
Run npx skills add google/skills --skill agent-platform-endpoint-management -a claude-code. The skill file is installed at ~/.claude/skills/agent-platform-endpoint-management/SKILL.md.
What does agent-platform-endpoint-management do?
It guides agents through creating, listing, describing, updating, and deleting Agent Platform serving endpoints. It also covers permission, quota, and resource-busy troubleshooting.
Which platforms support this skill?
The skill targets Claude Code, Gemini CLI, and Codex. Google Cloud credentials, an active project, and a region are required for the commands.
Source text
SKILL.md · Apache-2.0
---
name: agent-platform-endpoint-management
metadata:
version: "1.0.1"
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:
```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.
© google · Apache-2.0 · google/skills