Agent skill · google
google-cloud-solution-hybrid-search-alloydb
Discovers requirements and generates architectural, design, and deployment guidance for dynamic hybrid search systems by combining semantic search and keyword search. Optimized for AlloyDB hybrid search use cases in Google Cloud. Use when users need vector search combined with structured SQL filtering, faceted attributes, semantic reranking, in-database AI validation, or serverless hosting across transactional relational databases, analytical data warehouses, or managed database engines. DON'T use this skill for simple keyword-only search, or when a standalone non-relational vector database is required.
What it needs
About 9k tokens when loaded.
What this skill does
Dynamic Hybrid Search using AlloyDB This skill provides a workflow to design and implement secure, low-latency, and high-accuracy hybrid search solutions combining structured dataset filtering, vector search indexing, faceted metadata filtering, semantic reranking, recall evaluation, in-database AI validation, database abstraction layers, and serverless application hosting. Overview of the workflow The workflow consists of the following phases: 1. Requirements discovery. Gather detailed requirements related to the cloud workload or use case that the user needs assistance for. 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. 3. Solution validation. Create a plan to validate the generated solution, generate validation instructions and scripts, and run the validation. 4. Solution packaging 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, cloud services, or component mappings. This prevents premature architecture commitments or hallucinations before the full scope is understood. Halting for approval: For any step where you are instructed to "obtain approval before proceeding", you MUST stop executing, present the completed tasks to the user, and wait for their explicit approval. You MUST NOT proceed to execute any subsequent tasks or generate any further guidance in that response. Ground all generated content: For all tasks across all phases, you MUST first look in the following resources: Product Mapping, Design Recommendations for the required guidance. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/google-cloud-solution-hybrid-search-alloydb