Agent skill · data analytics · google

google-cloud-solution-agentic-analytics-spark-knowledge-catalog

Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and Iceberg), establishing metadata governance with Knowledge Catalog aspect types, or grounding agentic IDEs (VS Code, Antigravity) by using the Google Cloud Data Agent Kit. Don't use for provisioning borderless data lakehouse infrastructure (use google-cloud-solution-agentic-ai-borderless-data-lakehouse instead).

Why this skill is useful

Adds a comprehensive workflow for designing and implementing a governed analytics solution across multiple cloud environments and data types, including validation scripts and architectural guidance.

What it needs

About 9k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

Agentic analytics across cloud providers and data types This skill provides a workflow to design and implement a governed, secure pipeline for agentic analytics solution across structured and unstructured data that's distributed across Google Cloud, on-premises systems, and other cloud providers. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. Overview of the workflow The workflow consists of the following phases: Phase 1: Requirements discovery. Gather detailed requirements related to the cloud workload or use case that the user needs assistance for. Phase 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. Phase 3: Solution validation. Create a plan to validate the generated solution, generate validation instructions and scripts, and run the validation. Phase 4: Solution packing 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, technical decompositions, cloud services, or component mappings. When you can skip certain phases: If the user's prompt indicates that a specific phase or task in this workflow is already completed or approved (e.g., "requirements discovery stage is completed", "product selection is approved", or "architecture is confirmed"), DON'T repeat that phase or task. Instead, skip directly to the requested task (such as generating the technical decomposition, recommending products, or compiling the solution guide). Phase 1: Requirements discovery and analysis 1. Request the user to describe the functional requirements (business processes, activities, and use cases) of their workload. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/google-cloud-solution-agentic-analytics-spark-knowledge-catalog

View the source on GitHub

Browse the @skills marketplace