Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
onewave-ai avatar

Data Pipeline Builder

  • 157 installs
  • 237 repo stars
  • Updated July 15, 2026
  • onewave-ai/claude-skills

Design and scaffold ETL/ELT flows—sources, transforms, schedules, and sinks—for analytics, ML features, or operational reporting.

About

data-pipeline-builder plans end-to-end ETL/ELT: choose sources and sinks, define transform stages, scheduling, failure handling, and observability so teams can implement reliable analytics and feature pipelines without ad-hoc scripts.

  • Source-to-sink design
  • Transform steps
  • Scheduling patterns
  • Idempotency notes
  • Monitoring hooks

Data Pipeline Builder by the numbers

  • 157 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #726 of 2,064 Data Science & ML skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/onewave-ai/claude-skills --skill data-pipeline-builder

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs157
repo stars237
Last updatedJuly 15, 2026
Repositoryonewave-ai/claude-skills

What it does

Design and scaffold ETL/ELT flows—sources, transforms, schedules, and sinks—for analytics, ML features, or operational reporting.

Files

SKILL.mdMarkdownGitHub ↗

Data Pipeline Builder

Design and implement production-grade ETL/ELT data pipelines: take data sources, a destination, and transformation requirements, then produce a complete pipeline specification plus all implementation files needed to run it.

Contents

  • references/project-structure.md -- output file layout, architecture pattern selection, component selection.
  • references/python-patterns.md -- Python code standards and base extractor/transformer/loader/retry patterns.
  • references/quality-checks.md -- composable data quality check framework and built-in checks.
  • references/orchestration-config.md -- Airflow DAG, pipeline config YAML, and monitoring/alerting patterns.
  • references/spec-template.md -- the data-pipeline-spec.md output template.

Workflow

1. Gather requirements. If the user gave clear requirements, proceed to design. Otherwise ask targeted questions: data sources (databases, APIs, files, streams); destination (warehouse, lake, database); transformations (joins, aggregations, filters, business rules); freshness requirement (real-time, hourly, daily); technology preferences (Airflow, dbt, Spark, cloud provider); data quality and compliance requirements.

2. Analyze and design. Catalog each source (connection type, auth, schema, volume, CDC availability, rate limits). Define the destination (platform, schema design, partitioning, clustering, access patterns). Map transformations (field mappings, business logic, type conversions, joins, aggregations, deduplication, SCD handling, derived fields). Establish non-functional requirements (freshness SLA, processing window, failure tolerance, retention, compliance). Select an architecture pattern and components per references/project-structure.md.

3. Present the design before generating code. Confirm architecture, sources, destination, schedule, key transformations, and quality gates with the user, then proceed on approval.

4. Generate implementation. Produce all files following the layout in references/project-structure.md, customized to the specific pipeline with no placeholder code requiring manual editing:

  • For each source, generate a concrete extractor inheriting from BaseExtractor (see references/python-patterns.md).
  • For each transformation, generate a concrete transformer class or SQL file.
  • For each destination, generate a concrete loader inheriting from BaseLoader.
  • Generate the Airflow DAG with all task dependencies wired up and the pipeline config YAML (see references/orchestration-config.md).
  • Generate quality checks tailored to the data and monitoring config with appropriate alert thresholds (see references/quality-checks.md and references/orchestration-config.md).
  • Generate tests for all custom business logic.

5. Generate the specification last. Produce data-pipeline-spec.md using references/spec-template.md, referencing all implementation files and incorporating design decisions made during the process.

Operating Rules

  • Design for idempotency -- make every step safely re-runnable.
  • Include watermark/checkpoint tracking for incremental pipelines.
  • Include dead letter handling for records that fail processing.
  • Include schema evolution handling -- sources will change their schemas.
  • Never hardcode credentials -- use environment variables or secret managers.
  • Never skip quality checks -- they are the first line of defense against bad data.
  • Prefer SQL for transformations expressible in SQL; use Python for complex logic that does not map cleanly to SQL.
  • Include a backfill strategy and an operational runbook covering common failure scenarios in the spec.
  • Use structured logging throughout and track data lineage at every transformation step.

Related skills

Data Science & MLpipelinesetl

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.