Agent skill · writing content · google

agent-platform-rag-engine-management

Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google Workspace RAG, or other RAG products like gRAG.

Why this skill is useful

Provides specific commands and workflows for managing RAG Engine corpora using the Google GenAI SDK 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

Agent Platform RAG Engine Management This skill provides instructions on how to interact with Agent Platform RAG Engine using the Agent Platform Python SDK. You MUST use the vertexai Python SDK to perform RAG Engine operations, rather than raw REST calls or MCP tools, because this code is intended to be run by external clients. 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: 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: 1. Tier R: Read-only (listcorpora, listfiles, getcorpus, retrievalquery) No confirmation needed. Execute immediately to gather information or retrieve grounded contexts. 2. Tier RC: Read-only but consumes Compute Resources (client.models.generatecontent) Requires interactive confirmation with 'Yes'/'No' options before executing grounded content generation. The confirmation prompt MUST clearly explain the proposed generation execution and its key parameters (e.g., target corpus ID, query text, target model). Natural-language paraphrases without specifying exact parameters are insufficient, as explicit parameter listing is required to ensure unambiguous user approval of the specific resource and configuration. Same-turn restriction: Do not execute the generation code in the same turn as presenting the confirmation prompt. Stop and wait for the user's reply; only execute after explicit 'Yes' / approval. Gold Standard Example: I will perform grounded content generation with the following parameters. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/agent-platform-rag-engine-management

View the source on GitHub

Browse the @skills marketplace