Skill UI

This skill provides production patterns for implementing robust data quality validation using Great Expectations, dbt tests, and formal data contracts. It is essential for building reliable, automated, and verifiable data pipelines, ensuring data integrity throughout the entire ETL/ELT process, and establishing clear data governance rules.

Guides you through generating dbt models inside data pipelines, covering setup, code generation, configuration, and validation while following best practices for ETL, orchestration, and streaming workloads.

Automates dbt test creation within data pipelines, offering guided best practices, code generation, and validation to keep ETL, transformation, and streaming workflows reliable.

A guide to production-ready patterns for dbt (data build tool). It covers essential practices for robust data pipeline development, including model organization (staging, intermediate, marts), implementing advanced testing strategies, ensuring data quality, and optimizing incremental processing for large datasets.

Comprehensive Snowflake development assistant covering SQL best practices, dynamic tables, streams, tasks, Snowpipe, Cortex AI functions/agents, Snowpark Python, dbt integration, performance tuning, and security hardening for production data platforms.

Surfaces Monte Carlo data observability insights—health, lineage, alerts, and monitors-as-code—before developers edit dbt models or SQL pipelines, ensuring risk-aware code changes.

This skill automatically generates an interactive SQL Notebook designed to validate changes in dbt models or snapshots. It processes changes identified from a GitHub PR or local repository, generating comparison queries that compare 'before' (production) and 'after' (development) data states. It is essential for embedding data observability and quality checks into CI/CD pipelines.

This skill helps diagnose performance bottlenecks, slow jobs, and expensive queries across various data platforms (Airflow, dbt, Databricks). It uses a tiered investigation approach, starting with broad discovery to pinpoint problematic jobs or queries, bridging to affected tables, and finally drilling down to identify root causes, latency trends, and change-related regressions.