data-pipeline-builder

Generates ETL/ELT pipeline code, Airflow DAGs, quality checks, and monitoring configuration.

1|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/th-efool/SKILLS --skill data-pipeline-builder-th-efool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-pipeline-builder
Source: https://github.com/th-efool/SKILLS/tree/main/data-pipeline-builder
Command: npx skills add https://github.com/th-efool/SKILLS --skill data-pipeline-builder-th-efool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing a production data pipeline from scratch requires coordinating extractors, transformers, loaders, orchestration, quality checks, and monitoring, which is slow and error-prone when done manually. ## Core Features & Use Cases - End-to-End Pipeline Generation: Produces concrete Python extractor, transformer, and loader classes plus SQL files with no placeholder code. - Orchestration & Monitoring Setup: Generates a wired Airflow DAG, pipeline config YAML, alert rules, and metrics collection utilities. - Data Quality Framework: Creates composable checks (not-null, unique, freshness, referential integrity, schema) with severity levels and thresholds. - Use Case: You need to move daily orders from Postgres into BigQuery with deduplication and freshness SLAs. Describe the sources and destination, approve the design, and receive the full project layout, DAG, tests, and a data-pipeline-spec.md runbook. ## Quick Start Ask the assistant to design and build an ETL pipeline from your Postgres orders database into BigQuery with daily scheduling and data quality checks.

Frequently Asked Questions about data-pipeline-builder

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

FAQPage Schema
How do I build an ETL pipeline with Airflow and Python?▼

Define your sources, destination, and transformations, then generate concrete extractor, transformer, and loader classes inheriting from base patterns. The Airflow DAG wires extraction, quality checks, transformation, and loading task groups with retries and dependencies.

What is the difference between ETL and ELT architecture?▼

ETL transforms data before loading into the warehouse, suiting complex business logic and freshness SLAs of an hour or more. ELT loads raw data first and transforms with SQL in the warehouse, which fits frequent schema evolution and strong warehouse compute.

How do I add data quality checks to a data pipeline?▼

Use composable checks such as not-null, unique, range, freshness, row count, referential integrity, and schema validation, each with warn, error, or critical severity. Run them pre-transform, post-transform, and after loading with configurable failure thresholds.

Can the pipeline handle incremental extraction and schema changes?▼

Yes, incremental pipelines use watermark and checkpoint tracking to resume from the last extraction point. Schema evolution handling and schema checks detect when sources change their columns, and every step is designed to be idempotent and safely re-runnable.

When should I use streaming ETL instead of batch?▼

Choose streaming ETL with Kafka or Kinesis and Flink or Spark Streaming when the freshness SLA is under five minutes or the architecture is event-driven. For one-to-fifteen-minute freshness, micro-batch with short Airflow intervals is simpler to operate.