data-engineer

Designs and hardens ETL pipelines, orchestration, and warehouse schemas for reliable data delivery.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill data-engineer-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-engineer
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/data-engineer
Command: npx skills add https://github.com/sumitake/agent-collab --skill data-engineer-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Data pipelines often break silently under retries, late-arriving data, and schema drift, corrupting downstream consumers without anyone noticing. This Skill applies senior data-engineering discipline to build pipelines and warehouse structures that preserve correctness, lineage, and data contracts under real operational conditions. ## Core Features & Use Cases - Pipeline and Orchestration Design: Maps source-to-sink flows, designs dependency graphs, retry policies, and backfill mechanics for unattended operation. - Idempotency and Data Quality: Ensures reruns do not duplicate or drop records, and builds completeness, uniqueness, and anomaly checks directly into the pipeline. - Warehouse Modeling: Designs dimensional models, dbt transformation layers, and schema evolution strategies that protect downstream consumers. - Use Case: When a nightly ETL job occasionally double-counts records after a retry, use this Skill to trace the failure mode, implement an idempotent load pattern, and add a dead-letter path for malformed records. ## Quick Start Ask the agent to review this ETL pipeline for idempotency and data-quality gaps and propose the smallest safe fix.

Frequently Asked Questions about data-engineer

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

FAQPage Schema
How do I make an ETL pipeline idempotent?▼

Idempotent pipelines ensure a rerun of a failed job does not duplicate, drop, or double-count records. This Skill analyzes retry and replay behavior under realistic failure scenarios and applies the narrowest fix, such as deterministic keys or upsert-based loads.

How to design dbt models and warehouse schemas?▼

Warehouse design uses dimensional modeling with staging, intermediate, and mart transformation layers in tools like dbt. The Skill covers star and snowflake schema choices, slowly changing dimensions, and partitioning matched to query patterns and cost.

What data quality checks should run inside a pipeline?▼

Pipelines should enforce completeness, uniqueness, referential integrity, and anomaly detection automatically rather than relying on downstream analysts. Bad records route to a dead-letter or quarantine path instead of failing the run or being silently dropped.

How do I handle schema changes without breaking downstream consumers?▼

Schema evolution requires versioning changes to source or warehouse schemas so downstream consumers are not silently broken. Any contract change is versioned or flagged, and backfill paths are checked against existing consumers before running against production data.

When should I not use this data engineering skill?▼

This Skill owns pipeline, orchestration, and warehouse-schema work only. Query performance tuning belongs to a query-tuning skill, and ML model training belongs to a machine-learning skill, even when they touch the same data.