Google Cloud AI Agent Builder
Design, implement, deploy, and validate AI agents and multi-agent systems on Google Cloud.
The workflow requires confirmation of requirements, architecture, implementation, and validation, and explicitly mentions least privilege, OIDC, Model Armor, human oversight, encrypted environment variables, and deployment dry runs. However, it lacks concrete IAM boundaries, complete data-flow and sensitive-data lifecycle guidance, and an actionable rollback procedure; IaC and deployment can also cause external changes, so points were deducted.
The four-phase workflow is internally coherent and includes templates, validation checks, and deployment troubleshooting assistance. However, there are no executed tests, pinned dependency versions, complete reproducible command examples, or specific failure-diagnosis and recovery procedures. Much of the workflow depends on external references and placeholders, so the static score remains below 10.
The name, target scenario, and exclusions for general architecture or narrow single-product tasks are reasonably clear, and the skill selects between single-agent and multi-agent patterns based on requirements. Inputs, output contracts, and trigger conditions remain broad; Chinese-language interaction is not addressed, and mainland-China reachability of Google Cloud services is not discussed, so points were deducted.
SKILL.md has a clear phased structure and supplies guidance references, product mappings, design principles, and three output templates. Repository-level installation, Apache-2.0 licensing, contribution channels, and active-development status are documented. The skill lacks its own version, changelog, named maintenance responsibility, pinned dependencies, FAQ, and complete troubleshooting guidance, so points were deducted.
The skill clearly targets usable deliverables including an architecture document, Mermaid diagram, IaC, deployment instructions, and a validation plan. However, the templates are mostly skeletons, exact ADK/MCP code and deployment details must be generated dynamically from external material, and no representative output is verified. The score is therefore conservatively limited by static calibration.
Evidence includes the skill's reference inventory, product mappings, templates, and repository-level license and installation documentation, primarily pointing to official material. There is no supplied test suite, CI coverage, execution log, or independent reproduction evidence, so key paths cannot be statically verified and the score is kept at or below 5.
- IaC and deployment may modify real cloud resources; define the project, region, IAM scope, approval authority, change boundary, and rollback plan before execution.
- Do not treat template placeholders, sample commands, or product recommendations as verified configurations; check current official documentation, API availability, quotas, regional support, and costs.
- Chinese-language support and mainland-China network reachability are not specified; validate access conditions for the relevant Google Cloud, documentation, and CLI services.
- Add workload-specific rules for sensitive-data inspection, log redaction, secret management, and agent-tool permissions.
What does this skill do, and when should you use it?
This skill is for users designing or implementing AI agent systems on Google Cloud. It structures the work into requirements discovery, solution design, implementation planning, and validation. It recommends single-agent or multi-agent patterns based on workload complexity, workflow, latency, and cost, then produces architecture, deployment, and verification materials. Its scope is agentic Google Cloud solutions, not general cloud architecture or narrow single-product tasks.
Collects functional and non-functional requirements, current systems, knowledge sources, and dependencies; identifies ambiguities and requests confirmation; recommends a single-agent or multi-agent pattern; decomposes components and maps them to Google Cloud products; creates Mermaid architecture diagrams; and drafts solution-architecture.md, implementation-instructions.md, and validation-plan.md. The planned materials can include Terraform, Agents CLI, gcloud, curl, Cloud Run scaling guidance, and MCP-based tool registration.
- A cloud architect needs to discover requirements and confirm a technical decomposition for a new AI-agent workload.
- A platform engineer needs Google Cloud product mappings, an architecture diagram, and deployment guidance for an agent system.
- A development team needs implementation instructions containing Terraform or Agents CLI steps.
- An operations team needs checks for routing, IAM enforcement, security policies, and deployed service endpoints.
- A team needs local agent runs, evaluations, and deployment dry runs before production release.
What are this skill's strengths and limitations?
- Covers requirements, architecture, implementation planning, and validation in one workflow.
- Requires confirmation at important design and review stages and supports iteration.
- Specifies Mermaid diagrams, Terraform, Agents CLI, MCP, Cloud Run cost controls, and protected credential handling.
- Accounts for cross-cloud, hybrid, and on-premises components.
- Its full document-generation workflow depends on referenced guidance and template files whose contents are not provided here.
- It does not supply a ready-made architecture for a workload; sufficient requirements and user confirmation are required.
- The source provides no test suite, platform support matrix, or evidence of an actual deployment.
- Implementation and validation depend on Google Agents CLI, Terraform, gcloud CLI, curl, and suitable cloud permissions.
How do you install this skill?
Install the collection with npx skills add google/skills. During installation, select skills/cloud/google-cloud-solution-build-deploy-agents. The source does not document a specific installation directory or separate skill-only command.
How do you use this skill?
In an Agent Skills-compatible client, provide a concrete request such as: Design, implement, and validate a multi-agent system on Google Cloud that accesses an enterprise knowledge base. Include functional requirements, non-functional requirements, existing systems, knowledge sources, and dependencies; the skill requests confirmation at successive phases.
How does this skill compare with similar options?
Unlike the repository's Google Cloud solution-architecture skill, this skill is specifically for AI-agent or multi-agent systems; general Google Cloud solution architecture is directed to that other skill.