pipeline-design

Designs Medallion architecture ETL/ELT pipelines with mandatory Lakeflow rules for Databricks and Fabric.

4|1|Updated May 22, 2026
One-click install
npx skills add https://github.com/ThomazRossito/ai-data-agents --skill pipeline-design-thomazrossito
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pipeline-design
Source: https://github.com/ThomazRossito/ai-data-agents/tree/main/plugins/ai-data-agents/skills/pipeline-design
Command: npx skills add https://github.com/ThomazRossito/ai-data-agents --skill pipeline-design-thomazrossito

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing ETL/ELT pipelines across Databricks and Microsoft Fabric often leads to inconsistent layer patterns, misuse of streaming tables versus materialized views, and missing quality controls. This Skill enforces a standardized Medallion architecture (Bronze/Silver/Gold) with mandatory per-layer rules so pipelines are built correctly from the start. ## Core Features & Use Cases - Medallion Architecture Rules: Defines mandatory Lakeflow/SDP object types per layer, such as STREAMING TABLE with cloud_files() for Bronze and MATERIALIZED VIEW for Gold, including explicit prohibitions like manual SCD2 window functions. - Cross-Platform Patterns: Provides connectivity strategies between Fabric OneLake and Databricks via ABFSS paths, OneLake shortcuts, or export/upload workflows. - Databricks Job Configuration: Includes a JSON reference for multi-task jobs with dependencies, cron scheduling, and retry policies, plus a 10-point pipeline quality checklist. - Use Case: When asked to design a new sales data pipeline, apply this Skill to produce a Bronze ingestion layer via Auto Loader, a Silver layer using AUTO CDC INTO for SCD Type 2, and a Gold star schema, along with a scheduled Databricks job definition. ## Quick Start Use the pipeline-design skill to design a new ETL pipeline that ingests CSV files from a Fabric Lakehouse into Databricks following the Medallion architecture.

Frequently Asked Questions about pipeline-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a Medallion architecture pipeline in Databricks?▼

Structure the pipeline into three layers: Bronze uses STREAMING TABLE with cloud_files() Auto Loader for raw append-only ingestion, Silver uses STREAMING TABLE with AUTO CDC INTO for SCD Type 2, and Gold uses MATERIALIZED VIEW for star schemas and aggregations.

How to implement SCD Type 2 in Databricks Lakeflow pipelines?▼

Use AUTO CDC INTO with CREATE FLOW on a Silver streaming table to get native SCD Type 2 handling. Manual approaches with LAG/LEAD window functions or SHA2 hashing are prohibited in this pattern.

Can Databricks read data directly from Microsoft Fabric OneLake?▼

Yes, through three strategies: a shared ABFSS path where both platforms access the same Azure Data Lake, a OneLake shortcut mounted as an external Databricks volume, or exporting from OneLake and uploading to a Databricks Volume.

When should I use streaming tables versus materialized views in Lakeflow?▼

Use STREAMING TABLE for Bronze and Silver layers where incremental append and CDC processing are required. Use MATERIALIZED VIEW only in the Gold layer for aggregations and star schema serving; it is prohibited in the Silver layer.

What quality checks should a production Databricks pipeline include?▼

Validate input schemas before transformation, handle nulls and deduplication, avoid inferSchema in production, partition tables over 10GB, schedule OPTIMIZE/ZORDER, configure retries and alerts, and store credentials in a secrets manager.