Agent Platform Prompt Management

Manages and orchestrates prompts in Agent Platform. Use when you need to create, list, retrieve, version, or delete managed prompts in Agent Platform. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform prompts.

Published by @google·0 agent reads / 30d·0 saves·

Usage Guide

To use this skill effectively:

  1. Generate Code: Provide the Python snippets below to the user to help them manage prompts in Agent Platform.
  2. No File System Search: Do not try to find Python files or scripts on the file system for these operations.

Phase 0: Environment Setup

CRITICAL: Before the user runs any of the Python snippets below, you MUST advise them to ensure the environment is correctly initialized by following these steps:

  1. Google Cloud Authentication: Authenticate with your Google Cloud account and configure active Application Default Credentials (ADC) for Agent Platform access:
    gcloud auth login
    gcloud auth application-default login
    
  2. Virtual Environment: Create and activate a dedicated virtual environment:
    python3 -m venv ~/prompt_agent_venv
    source ~/prompt_agent_venv/bin/activate
    
  3. Install Dependencies: Install the required Agent Platform SDKs:
    pip install google-cloud-aiplatform google-genai
    
  4. Execution: Advise the user that every time they execute a Python snippet, they must ensure this virtual environment is activated first.

[!TIP] Placeholder Parameter Replacement: The Python scripts below use uppercase string placeholders (like "PROJECT_ID", "LOCATION_ID", and "PROMPT_ID"). You MUST dynamically replace these placeholders with the actual Project ID, Region, and Prompt ID values provided in the user's prompt (or discovered context) before generating or providing the scripts.

1. Managing Prompts via Agent Platform SDK

The SDK provides a high-level Prompt class in the preview module.

Create a Prompt (Tier M)

Use when you need to create a new managed prompt in Agent Platform.

  • Reference: See create.md for detailed instructions and Python snippets.

List Prompts (Tier R)

import vertexai
from vertexai.preview import prompts

vertexai.init(project="PROJECT_ID", location="LOCATION_ID")

all_prompts = prompts.list()
for p in all_prompts:
    print(f"Name: {p.display_name}, ID: {p.prompt_id}")

Retrieve and Use a Prompt (Tier R)

import vertexai
from vertexai.preview import prompts

vertexai.init(project="PROJECT_ID", location="LOCATION_ID")

retrieved_prompt = prompts.get(prompt_id="PROMPT_ID")
# Versions are supported: prompts.get(prompt_id="PROMPT_ID", version_id="2")

# Assemble with variables (kwargs must match template variable names)
assembled = retrieved_prompt.assemble_contents(text="The quick brown fox...")
print(assembled)

Delete a Prompt (Tier D)

CRITICAL: You must pass the numeric prompt ID (e.g., "1234567890123456789") to prompts.delete(). The SDK constructs the full resource path internally using the project and location from vertexai.init().

Confirmation Required: As a Tier D (Destructive) operation, the agent MUST pause and request explicit, high-friction typed re-confirmation of the prompt ID from the user before generating or providing the deletion code. The action is irreversible.

[!IMPORTANT] NEVER pre-emptively provide or execute any deletion code before receiving the user's response in a new turn. You must never speculate or assume that confirmation will be given. Asking for confirmation and providing the code in a single parallel turn is a severe safety violation.

import vertexai
from vertexai.preview import prompts

vertexai.init(project="PROJECT_ID", location="LOCATION_ID")

prompts.delete(prompt_id="PROMPT_ID")

2. Best Practices

  • Idempotency:
    • Tier R (List, Get): Inherently idempotent.
    • Tier D (Delete): Re-running a delete on a non-existent or already deleted resource returns NOT_FOUND. Treat this as success.
  • Placeholders: Use the standard placeholder syntax (variable name enclosed in double curly braces) in your prompt templates.
  • Versioning: Always tag or record version IDs when making updates to production prompts.
  • Model Reference: Specify the target model ID (e.g., gemini-2.5-pro) when creating the prompt to ensure consistency.
  • Underlying Schema: When using the Dataset API, always use the correct metadata_schema_uri and nested metadata structure to ensure the prompt is recognized by Agent Platform Studio and the Prompts SDK.

Bundled with this artifact

1 file

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL0

Workload Manager Basics

Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.

software-engineering+2
0
SKILL0

Google Cloud Recipe Onboarding

Guides a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resource. Use when a new developer wants to initialize their first Google Cloud project, configure billing, and verify deployment. Don't use for enterprise organization setup (use Google Cloud Setup guided flow for that instead). Don't use for complex multi-project architectures.

software-engineering+2
0
SKILL0

Google Cloud Recipe Auth

Provides expert guidance on authenticating and authorizing to Google Cloud services and APIs, covering human users, service identities, Application Default Credentials (ADC), and best practices for secure access.

software-engineering+2
0