engineering-data-engineer

Automate ETL/ELT pipeline and lakehouse architecture design for analytics-ready data.

10|2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Dev-Dennis-040/openclaw-agency-skills --skill engineering-data-engineer-dev-dennis-040
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-data-engineer
Source: https://github.com/Dev-Dennis-040/openclaw-agency-skills/tree/main/skills/engineering/engineering-data-engineer
Command: npx skills add https://github.com/Dev-Dennis-040/openclaw-agency-skills --skill engineering-data-engineer-dev-dennis-040

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Data infrastructures often struggle with unreliable pipelines, inconsistent schemas, and slow delivery of analytics-ready data. This skill provides a clear blueprint for designing resilient data pipelines and lakehouse architectures.

Core Features & Use Cases

  • End-to-end data pipeline design from ingestion to analytical models, enabling reliable Bronze/Silver/Gold data layers.
  • Lakehouse architecture guidance with data contracts, schema governance, and scalable storage patterns.
  • Quality, observability, and governance through data quality checks, lineage tracking, and robust monitoring.

Quick Start

Define a reliable data pipeline that ingests raw data, builds Bronze/Silver/Gold layers, and delivers analytics-ready tables.

Frequently Asked Questions about engineering-data-engineer

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

FAQPage Schema
How do I design a scalable ETL data pipeline with Bronze, Silver, and Gold layers?

Design a scalable ETL data pipeline by ingesting raw data into the Bronze layer, refining it in Silver, and delivering analytics-ready tables in Gold. This approach ensures reliable schema management, data quality checks, and structured lakehouse architecture governance.

What is a lakehouse architecture and when do I need data contracts?

A lakehouse architecture combines scalable storage with analytical modeling, requiring data contracts when you need strict schema governance. You need this setup to enforce reliable ingestion, maintain data quality, and provide consistent lineage tracking across modern cloud data platforms.

Can I build streaming and incremental ingestion workflows for a cloud data platform?

Yes, you can build streaming and incremental ingestion workflows for a cloud data platform. The architecture supports scalable ETL/ELT workflows that process data incrementally, satisfying requirements for reliable ingestion and cost-conscious processing in modern data platforms.

How do I add data quality checks and observability to my dbt and Spark pipelines?

Add data quality checks and observability to dbt and Spark pipelines by implementing automated validation rules, lineage tracking, and robust monitoring. This ensures your data pipeline maintains consistent schemas and delivers reliable, analytics-ready data outputs.

What is the best way to govern schemas and manage data lineage in an ELT workflow?

The best way to govern schemas and manage data lineage in an ELT workflow is through a lakehouse blueprint that enforces data contracts. This method provides structured governance, tracks data transformations across layers, and maintains reliable analytical models.