Google Cloud Solution Agentic AI Borderless Data Lakehouse
GoogleOfficialPublished by Google
- Skill
- Workflow
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a comprehensive, four-phase workflow to assist users in architecting and implementing borderless open data lakehouse solutions. It guides users through requirements discovery, technical component mapping, architecture design, and the creation of an implementation plan using Infrastructure as Code (IaC). The process is specifically tailored for multi-cloud environments involving Google Cloud, AWS, and Azure, utilizing technologies such as Apache Iceberg, BigQuery, and Managed Service for Apache Spark.
What it does
- Analyzes workload requirements and constraints for multi-cloud data architectures.
- Maps technical components to appropriate Google Cloud products and features.
- Generates architecture diagrams in Mermaid format for data ingestion and serving subsystems.
- Provides guidance on security, reliability, and operational excellence for hybrid environments.
- Produces Infrastructure as Code templates and step-by-step deployment instructions.
- Outlines validation procedures to verify connectivity, security policies, and infrastructure deployment.
When to use it
- When architecting multi-cloud storage infrastructure across Google Cloud, AWS, and Azure.
- When establishing ingestion and AI serving subsystems for distributed data.
- When configuring Cross-Cloud Interconnect for private network connectivity.
- When deploying Gemini Enterprise Agent Platform and BigQuery data agents.
Advantages
- Ensures architectural consistency by following established Google Cloud design patterns.
- Provides a clear, iterative process from initial discovery to final validation.
- Promotes modular network design using transit VPCs and secure connectivity practices.
- Standardizes the use of Terraform for automated resource provisioning.
Usage examples
- “Help me design a multi-cloud data lakehouse that connects AWS S3 and Google Cloud Storage.”
- The agent will initiate the requirements discovery phase to understand your data sources, security needs, and analytical requirements before proposing a technical architecture.
- “I need to deploy a BigQuery data agent for my cross-cloud environment.”
- The agent will guide you through the implementation plan phase, providing the necessary prerequisites and deployment instructions to configure the agent.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/google/google-cloud-solution-agentic-ai-borderless-data-lakehouse/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip google-cloud-solution-agentic-ai-borderless-data-lakehouse.zip -d .agents/skills
Documentation by Google
Borderless open data lakehouse agentic AI system
Follow this workflow to help users design and implement a custom multi-product solution in the cloud for a given workload, use case, or requirement.
Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read and follow the instructions in
Usage Attribution.
Product Renaming & Terminology
When generating solution designs, architecture diagrams, and documentation, use the updated Google Cloud product names. For details on legacy vs. updated product names and terminology, see references/product_renaming.md.
Workflow
The solution design and implementation workflow consists of the following phases:
Phase 1: Requirements discovery and analysis: Analyze the workload's requirements, constraints, dependencies, and current state.
Phase 2: Solution design: Build a technology stack, architecture, and deployment configuration for the workload based on Google Cloud design best practices and recommendations.
Phase 3: Implementation plan: Generate automation and instructions to deploy the solution.
Phase 4: Solution validation: Validate that the deployment meets the requirements of the workload.
Phase 1: Requirements discovery and analysis
[ ] [ ] Step 1: Discover requirements: Understand the functional and non-functional requirements, business goals, and current state (if any) of the workload, including its architecture, dependencies, and constraints. Use the following questions to guide the requirements discovery process:
What are your primary data sources?
How do you manage and federate metadata across your data sources?
What are your security and credential management requirements?
What are the analytical and computational requirements to join and transform this borderless data?
What types of natural language prompts or user queries do you expect AI agents or end-users to execute against this data?
[ ] [ ] Step 2: Identify components: Based on the requirements analysis, identify the components of the workload and their relationships. Also identify any borderless components, hybrid components, or on-prem components that the solution needs to integrate with.
[ ] [ ] Step 3: Generate component decomposition: Generate a technical decomposition of the components of the workload.
[ ] [ ] Step 4: Ask for confirmation: Ask the user to confirm whether the generated technical decomposition matches their workload requirements.
[ ] [ ] Step 5: Iterate: If the user requests changes, then generate an updated technical decomposition, and ask the user to confirm the changes. Continue iterating until the user confirms the technical decomposition.
Phase 2: Solution design
[ ] [ ] Step 1: Retrieve relevant Google Cloud documentation: Use available search or fetch tools to read the content of the following Google Cloud documentation to ground the guidance that you generate in the remaining steps of this phase before proceeding.
Build hybrid and borderless architectures using Google Cloud
Network segmentation and connectivity for distributed applications in Cross-Cloud Network
Patterns for Connecting Other Cloud Service Providers with Google Cloud
Important: Use the content that you retrieve from Google Cloud documentation to ground the guidance that you generate in the remaining steps of this phase.
[ ] [ ] Step 2: Map components to Google Cloud products: For each component in the confirmed technical decomposition, identify the appropriate Google Cloud products and features, based on the guidelines in references/product_mapping.md.
[ ] [ ] Step 3: Create architecture diagram: Create an architecture diagram that shows the components, their relationships, and data/control flows.
The diagram must be in the Mermaid format: https://github.com/mermaid-js/mermaid.
The diagram must show a clear distinction between the products in the data ingestion subsystem and the serving subsystem.
The diagram must show Managed Service for Apache Spark as a shared component for ETL/ingestion processing, bridging the data ingestion and serving subsystems (distinct from interactive IDE analytics workflows).
[ ] [ ] Step 4: Generate design recommendations: Generate design guidance based on the guidelines in references/design_recommendations.md.
[ ] [ ] Step 5: Draft solution architecture: Compile the requirements, technical decomposition, product mapping, architecture diagram, and design recommendations into a single Markdown file named
solution-architecture-guide.md, based on the template in assets/output-template.md.[ ] [ ] Step 6: Request review: Present the generated solution architecture to the user and request their feedback or approval.
[ ] [ ] Step 7: Iterate: If the user requests changes, generate an updated solution architecture and repeat steps 2-6 until the user approves the solution architecture.
Phase 3: Implementation plan
[ ] [ ] Step 1: Retrieve relevant implementation resources:
Terraform Registry documentation for biglake_iceberg_catalog
Create an Apache Iceberg table with metadata in Lakehouse runtime catalog
Accelerate Spark batch workloads and sessions with Lightning Engine
Important: Use these resources as the technical foundation for the IaC and deployment instructions you generate in the remaining steps of this phase.
[ ] [ ] Step 2: Identify deployment prerequisites: Document prerequisites for the deployment, including the following:
Projects and billing associations
Required Google Cloud APIs
Required IAM permissions
Any other prerequisites
[ ] [ ] Step 3: Generate Infrastructure as Code (IaC): Generate code (e.g., Terraform) and deployment scripts to automate the provisioning of the proposed Google Cloud resources.
[ ] [ ] Step 4: Write deployment instructions: Draft sequential, step-by-step deployment instructions to execute the IaC and initialize the workload components.
[ ] [ ] Step 5: Request review: Present the generated deployment instructions to the user for feedback and confirmation.
[ ] [ ] Step 6: Iterate: If the user requests changes, generate an updated implementation plan and repeat steps 2-5 until the user approves the implementation plan.
Phase 4: Solution validation
[ ] [ ] Step 1: Retrieve relevant verification resources (optional): If the resources from Phase 3 are not already in your context, retrieve the same implementation resources as the starting point for the validation checks and verification scripts that you generate in this phase.
[ ] [ ] Step 2: Define validation checks: Outline validation steps to verify that the deployed infrastructure meets the workload requirements:
Deployment dry-run: Commands like
terraform planto preview changes.Connectivity and routing: Verification of network paths, load balancer routing, and service endpoints.
Security policies: Verification of restricted access, firewall rules, and IAM enforcement.
[ ] [ ] Step 3: Generate verification scripts: Draft lightweight scripts or command-line instructions (e.g. using
curlorgcloud) that the user can run to perform these validation checks.[ ] [ ] Step 4: Compile validation report: Document the validation steps, verification scripts, and expected outcomes in a single Markdown file.
[ ] [ ] Step 5: Conduct validation and finalize: Assist the user in executing the validation checks and troubleshooting any deployment issues. After the solution is validated successfully, request final approval from the user.
[ ] [ ] Step 6: Iterate: If the user requests changes, then generate an updated validation plan and repeat steps 2-5 until the user approves the validation plan.
Files
- ATTRIBUTION.mdAdded by AutoGineer934 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md10.1 KiB
- assets/output-template.md6.5 KiB
- references/attribution.md2.0 KiB
- references/design_recommendations.md4.9 KiB
- references/product_mapping.md3.7 KiB
- references/product_renaming.md1.5 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/google-cloud-solution-agentic-ai-borderless-data-lakehouse · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google or Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download google-cloud-solution-agentic-ai-borderless-data-lakehouse.zip