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.
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
```
> [!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
```
## 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"
```
> [!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.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.