Agent skill · product strategy · google
google-cloud-solution-agentic-ai-data-science-workflow
Designs a tailored multi-product agentic data science architecture on Google Cloud that incorporates opinionated best practices. Use when architecting multi-product solutions for agent-based data analytics or ML workloads. Don't use for simple queries, non-agentic pipelines, general cloud reviews, or writing agent code.
Why this skill is useful
Provides a structured workflow for designing multi-product data science solutions on Google Cloud, incorporating specific best practices and terminology updates.
What it needs
Requires google-cloud account access. About 6k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
Data science workflow with AI agents solution This skill guides agents through the workflow to design and implement 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 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. Product Renaming & Terminology When generating solution designs, architecture diagrams, and documentation, check the latest Google Cloud documentation for the most up-to-date product names. The table below provides examples of name mappings to be aware of. Note that underlying APIs, Terraform resources, and IAM roles may retain their legacy identifiers. Legacy Name Updated Name :--- :--- Vertex AI Gemini Enterprise Agent Platform Vertex AI Agent Engine Agent Runtime 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 by asking clarifying questions. You must halt and wait for the user to answer these questions before proceeding to the Identify components step. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/google-cloud-solution-agentic-ai-data-science-workflow