Agent skill · software engineering · google
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.
Why this skill is useful
Adds specific Python snippets and commands for managing prompts in Agent Platform that the AI wouldn't reliably generate on its own.
What it needs
Requires google-cloud-aiplatform, google-genai installed locally. Requires google-cloud account access. About 5k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION and append the attribution suffix to User-Agent headers: Usage Guide To use this skill effectively: 1. Execute Operations via Python: Run the Python snippets below using runcommand in the execution environment to manage prompts in Agent Platform on behalf of the user. Do not delegate execution to the user or claim lack of access once approved. 2. No File System Search: Do not try to find Python files or scripts on the file system for these operations. Safety & Confirmation Tiers (CRITICAL) Before executing any commands or scripts on behalf of the user, you must adhere to the following safety tiers based on the action requested, to prevent accidental mutation or permanent deletion of prompt resources: 1. Tier R: Read-only (list, get) No confirmation needed. Execute immediately to gather information. 2. Tier M: Mutating & Reversible (create) Requires interactive confirmation with 'Yes'/'No' options before executing prompt creation, to prevent unintended resource proliferation or misconfiguration. The confirmation prompt must clearly explain the proposed prompt creation and its key parameters (e.g., display name, template text, target model). Natural-language paraphrases without specifying the parameters are not sufficient. Same-turn restriction: Do not execute the creation code in the same turn as presenting the confirmation prompt. Stop and wait for the user's reply; only execute after explicit 'Yes' / approval. Every parameter in the card must trace back to something the user said. The target model is a user choice, not a default: if the user did not name one, ASK before building the card. Do not carry over the model that appears in the examples here or in references/create.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/agent-platform-prompt-management