Google Cloud Solution Build Deploy Agents

GoogleOfficialPublished by Google

Skill
Workflow
Cloud and DevOps
Apache-2.0
No issues found

From the author

Designs, builds, and deploys AI agents or multi-agent systems on Google Cloud. Provides an interactive workflow to gather requirements, recommend a tailored architecture, and generate deployment instructions. Use when designing or implementing agentic systems on Google Cloud. Don't use for general Google Cloud solution architecture (use google-cloud-solution-architecture instead) or for narrow tasks targeting a single product without agent context.

— the description by Google

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured, four-phase workflow to assist in the end-to-end lifecycle of AI agent development on Google Cloud. It guides the user through requirements discovery, architectural design, implementation planning, and validation. By leveraging specific Google Cloud best practices, it ensures that agentic systems are built with security, scalability, and operational excellence in mind, while providing clear paths for infrastructure provisioning and testing.

What it does

Analyzes functional and non-functional requirements for AI agent workloads.
Recommends appropriate agent design patterns, such as single-agent or multi-agent systems.
Generates technical decompositions and architecture diagrams in Mermaid format.
Maps workload components to specific Google Cloud products and services.
Produces Infrastructure as Code (IaC) and deployment scripts for cloud resources.
Defines validation plans, including local testing and deployment dry-runs.

When to use it

When you need to design a new AI agent or multi-agent system on Google Cloud.
When you require a structured plan to move an agentic workload from concept to production.
When you need to ensure your agent architecture follows Google Cloud best practices.
When you need to generate deployment instructions and infrastructure code for agentic services.

Advantages

Ensures architectural consistency by following established Google Cloud design principles.
Reduces deployment risk through structured validation and dry-run procedures.
Promotes operational excellence with built-in logging, tracing, and monitoring guidance.
Provides a clear, repeatable process for complex multi-agent system deployments.

Usage examples

“I need to build a multi-agent system for customer support on Google Cloud. Can you help me design the architecture?”: The agent will initiate the requirements discovery phase, asking about your specific customer support use cases, security constraints, and existing knowledge bases to propose a tailored architecture.
“Help me create an implementation plan for my agentic workload that uses Cloud Run.”: The agent will guide you through identifying prerequisites, generating Terraform scripts, and providing step-by-step deployment instructions optimized for Cloud Run scaling.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/google/google-cloud-solution-build-deploy-agents/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip google-cloud-solution-build-deploy-agents.zip -d .agents/skills

Documentation by Google

Build and deploy AI agents on Google Cloud

This skill guides agents through the workflow of designing and implementing a tailored 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.

Workflow

The solution design and implementation workflow is divided into 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.

Copy this checklist into your active task/plan artifact to track progress across the four phases:

[ ] Phase 1: Requirements discovery and analysis completed & confirmed.
[ ] Phase 2: Solution architecture generated & approved.
[ ] Phase 3: Implementation plan generated & approved.
[ ] Phase 4: Solution validation generated & approved.

Phase 1: Requirements discovery and analysis

Discover requirements: Gather and understand the functional and non-functional requirements, business goals, and current state (if any) of the workload, including its architecture, dependencies, and constraints.
Important: First, check whether the user's initial prompt has already answered the following questions or whether the prompt explicitly asks you to propose a solution architecture/diagram from a given set of parameters.
- If the user's prompt provides sufficient requirements and it explicitly requests an architecture proposal or diagram, then skip asking the questions below, and instead proceed to the step Recommend agent design pattern.
- If the user's prompt doesn't provide sufficient requirements, then complete these steps to gather missing information:
  1. Ask the user to describe the functional requirements of their workload: business processes, activities, and use cases.
  2. Ask the user to describe the non-functional requirements (security, privacy, compliance, reliability, disaster recovery, cost, operations, performance, and sustainability) of their workloads.
  3. Ask the user what existing systems, knowledge bases, product documentation, or other documentation the AI agents need to access for grounded guidance.
  4. Ask the user to describe dependencies, if any, on other workloads, products, or tools.
  5. Review the input that the user has provided so far, and check whether there are any ambiguities or contradictions in the input.
    If you identify any ambiguities or contradictions in the requirements that the user has provided, then do the following for each ambiguity or contradiction that you identify:
    - Describe the ambiguity or contradiction.
    - Ask the user how they wish to resolve the ambiguity or contradiction.
      - If the user delegates the choice to you (e.g., the user replies with "do what you think is best" or "you decide"), then provide a clear suggestion to resolve the ambiguity or contradiction, explain your reasoning, and ask the user to approve your suggestion.
    Critical: Until all the ambiguities and contradictions that you identify are resolved according to the preceding guidance, you must NOT recommend or generate any architecture design, technical decomposition, or Google Cloud product recommendations.
Recommend agent design pattern: Evaluate the complexity, workflow, latency, and cost requirements of the workload to recommend an agent design pattern:
- Single-agent system: Recommend for simpler tasks, acting as an effective starting point to refine core logic and tools.
- Multi-agent system: Recommend for complex problems requiring multiple specialized agents to collaborate on a workflow.
Identify components: Based on the requirements analysis, generate a technical decomposition of the workload. The technical decomposition must identify the logical components of the workloads and their relationships. Also identify any cross-cloud components, hybrid components, or on-premises components that the solution needs to integrate with.
Ask for confirmation: Ask the user to confirm whether the recommended design pattern and technical decomposition match their workload requirements.
Iterate: If the user requests changes, generate an updated technical decomposition, and ask the user to confirm the changes. Continue iterating until the user confirms the technical decomposition. Proceed to the next phase only after the user provides confirmation of the technical decomposition.

Phase 2: Solution design

Retrieve relevant Google Cloud guidance from references/related-guidance.md.
Important: Use the content that you retrieved from references/related-guidance.md to ground the guidance that you generate in the remaining steps of this phase.
Map components to Google Cloud products: For each component in the confirmed technical decomposition, identify the appropriate Google Cloud products and features by consulting product-mappings.md for detailed recommendations, trade-offs, and alternatives across networking, frontends, agent/model runtimes, memory stores, and tools.
Create architecture diagram: Create an architecture diagram in Mermaid format: https://github.com/mermaid-js/mermaid. The diagram should show the components, their relationships, and data/control flows.
Generate design recommendations: Generate design guidance based on the following Google Cloud best practices and recommendations. Use the information in references/related-guidance.md, with an emphasis on the guidance in references/design-principles.md.
Draft solution architecture: Compile the requirements, technical decomposition, product mapping, architecture diagram, and design recommendations into a single Markdown file adhering to the format in solution-template.md. Save this document in the workspace as solution-architecture.md.
Request review: Present the generated solution architecture (including the complete fenced mermaid code block for the diagram) directly to the user in your response, and explicitly request their feedback or approval. When you present the architecture, ask the user to provide approval for you to proceed with an implementation plan.
Iterate: If the user requests changes, generate an updated solution architecture and repeat the steps from "Map components to Google Cloud products" through "Request review" until the user approves the solution architecture.

Phase 3: Implementation plan

Retrieve relevant implementation resources:
Important: Use the resources in references/related-guidance.md as the technical foundation for the Infrastructure as Code (IaC) and the deployment instructions that you generate in the remaining steps of this phase.
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
Generate Infrastructure as Code (IaC): Generate code (e.g., Terraform) and deployment scripts to automate the provisioning of the proposed Google Cloud resources.
- Where appropriate, alongside or instead of raw infrastructure scripts, instruct the user to use Agents CLI commands (agents-cli scaffold create or agents-cli scaffold enhance) to set up or enhance the project structure, deployment configuration, and CI/CD pipelines.
Write deployment instructions: Draft sequential, step-by-step deployment instructions to execute the IaC and initialize the workload components. Compile the deployment prerequisites, IaC, and deployment instructions into a single Markdown file adhering to the format in implementation-template.md. Save this document in the workspace as implementation-instructions.md.
- The instructions MUST provide the exact ADK code to define a stateful agent node that takes a prompt, calls a model, and returns a tool execution request.
- The instructions MUST demonstrate how to register tools like database readers by using Model Context Protocol (MCP) standards.
- If deploying the agent to Cloud Run, the instructions MUST show how to configure Cloud Run to scale to zero when the agent is idle, reducing runtime costs.
- The instructions MUST recommend using encrypted environment variables to store model parameters or private API credentials. Encryption helps to prevent the exposure of sensitive credentials in plain-text container log streams.
- Where appropriate, the instructions MUST specify using the Agents CLI agents-cli deploy command (alongside or instead of raw infrastructure/deployment scripts) to run the deployment.
Request review: Present the generated deployment instructions to the user and explicitly request their feedback and confirmation.
Iterate: If the user requests changes, generate an updated implementation plan and repeat the steps from "Generate Infrastructure as Code (IaC)" through "Request review" until the user approves the implementation plan.

Phase 4: Solution validation

Retrieve relevant verification resources:
Important: Use the resources in references/related-guidance.md and their verification patterns as the starting point for the validation checks and verification scripts that you generate in the remaining steps of this phase.
Define validation checks: Outline validation steps to verify that the deployed infrastructure meets the workload's requirements:
- Deployment dry-run: Commands like terraform plan to preview changes. Include instructions to run agent deployment in dry-run mode (e.g., using agents-cli deploy --dry-run or -n) to preview steps and Terraform executions before pushing to production.
- Local testing and quality verification: Recommend using the Agents CLI to run and test agent logic locally (agents-cli run) and conduct systematic evaluations (agents-cli eval run) to verify agent quality and performance before deploying.
- Connectivity and routing: Verification of network paths, load balancer routing, and service endpoints.
- Security policies: Verification of restricted access, firewall rules, and IAM enforcement.
Generate verification scripts: Draft lightweight scripts or command-line instructions (e.g. using curl, gcloud, or agents-cli) that the user can run to perform these validation checks.
- The validation plan MUST include instructions using the Agents CLI for local runs, evaluations, and post-deployment validation checks (e.g., agents-cli run --url <service-url> to test the deployed service endpoint).
Compile validation plan: Document the validation steps, verification scripts, and expected outcomes in a single Markdown file adhering to the format in validation-template.md. Save this document in the workspace as validation-plan.md.
Request review: Present the validation plan to the user and explicitly request their feedback or approval on the validation plan.
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.
Iterate: If the user requests changes, generate an updated validation plan and repeat the steps from "Define validation checks" through "Request review" until the user approves the validation plan.

References & Supporting Links

For the complete list of Google Cloud architectural documentation, product manuals, development kits, and checklists used by this skill, see related-guidance.md.

Files

ATTRIBUTION.mdAdded by AutoGineer900 B
LICENSELicence file added by AutoGineer11.1 KiB
SKILL.md13.7 KiB
assets/implementation-template.md800 B
assets/solution-template.md4.9 KiB
assets/validation-template.md2.1 KiB
references/attribution.md1.9 KiB
references/design-principles.md3.9 KiB
references/product-mappings.md10.4 KiB
references/related-guidance.md5.1 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.

Needs: Needs Node.js

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

Google

Publisher

Google (Official)

Source

google/skills · skills/cloud/google-cloud-solution-build-deploy-agents · commit 2194d3b

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

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-build-deploy-agents.zip