Agent skill · product strategy · google
google-cloud-solution-rag-enterprise-search-gke-sqldb
Discovers requirements, and generates architectural, design, and deployment guidance for a retrieval-augmented generation (RAG)-capable enterprise search system in Google Cloud. Use when users need a vector-enabled SQL database as the store and index for the embedding vectors, an open model and open-source inferencing framework, and Kubernetes containers to host all the application components. DON'T use this skill for fully-managed RAG, or SaaS search services, or when a non-SQL vector database is required.
Why this skill is useful
Provides detailed architectural guidance and validation scripts for implementing a RAG-enabled search system on Google Cloud, which the AI wouldn't reliably generate on its own.
What it needs
Requires gcloud, kubectl installed locally. Requires google-cloud account access. About 8k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
RAG for enterprise search using GKE and AlloyDB This skill provides a workflow to design and implement a secure, low-latency, and high-accuracy RAG-enabled conversational search solution for private enterprise content by using an AlloyDB database, Cloud Storage, and a Google Kubernetes Engine (GKE) cluster to host all the application components, including an open model and an open-source inference framework. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. Overview of the workflow The workflow consists of the following phases: Phase 1: Requirements discovery. Gather detailed requirements related to the cloud workload or use case that the user needs assistance for. Phase 2: Solution architecture. Use the requirements that were gathered in Phase 1 to generate a detailed solution architecture for the cloud workload or use case. Phase 3: Solution validation. Create a plan to validate the generated solution, generate validation instructions and scripts, and run the validation. Phase 4: Solution packing and presentation. Consolidate the generated content and present the solution. Important notes about the workflow: Strict phase separation: During Phase 1 (Requirements discovery), when you ask the user clarifying questions, DON'T recommend, propose, or outline any architectural designs, technical decompositions, cloud services, or component mappings. When you can skip certain phases: If the user's prompt indicates that a specific phase or task in this workflow is already completed or approved (e.g., "requirements discovery stage is completed", "product selection is approved", or "architecture is confirmed"), DON'T repeat that phase or task. Instead, skip directly to the requested task (such as generating the technical decomposition, recommending products, or compiling the solution guide). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/google-cloud-solution-rag-enterprise-search-gke-sqldb