build-data-pipeline

Implements contract-governed lakehouse pipelines with Iceberg, WAP validation, and DLQ quarantine.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/vesviet/agent-skills --skill build-data-pipeline-vesviet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-data-pipeline
Source: https://github.com/vesviet/agent-skills/tree/main/core/skills/security-data/build-data-pipeline
Command: npx skills add https://github.com/vesviet/agent-skills --skill build-data-pipeline-vesviet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building reliable data pipelines often fails silently: upstream schema changes corrupt tables, bad records poison downstream analytics, and retries create duplicates. This Skill enforces data contracts, isolated audit branches, and deterministic upserts so pipelines stay consistent and replayable. ## Core Features & Use Cases - Contract-First Ingestion: Validates payloads against ODCS v3.1.0 schemas at producer boundaries before any data reaches storage. - Write-Audit-Publish (WAP): Stages writes on isolated Iceberg snapshot branches, audits them in-process with DuckDB over Arrow, then atomically publishes to main. - DLQ Quarantine with Circuit Breaker: Routes malformed records to a structured dead-letter queue and halts the pipeline when the quarantine ratio exceeds 2.0%. - Use Case: You ingest high-volume order events into an Iceberg lakehouse. This Skill stages each batch on a wap_audit_<run_id> branch, quarantines contract violations, runs DuckDB audit queries, and only fast-forwards main after all checks pass. ## Quick Start Use the build-data-pipeline skill to design an Iceberg ingestion pipeline with ODCS contract validation, WAP branching, and DLQ quarantine for my orders event stream.

Frequently Asked Questions about build-data-pipeline

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

FAQPage Schema
How do I implement Write-Audit-Publish with Apache Iceberg?▼

Write-Audit-Publish stages validated records on an isolated Iceberg snapshot branch such as wap_audit_<run_id>, runs audit queries against that branch, then atomically fast-forwards the main branch pointer. Failed audits abort without publishing, keeping main clean.

How to handle bad records in a data pipeline without crashing?▼

Route non-conforming records to a Dead-Letter Queue with structured diagnostic envelopes containing the raw payload, error code, and violated rule. A circuit breaker halts the pipeline only when the quarantine ratio exceeds 2.0% with at least 50 records.

What is the ODCS data contract standard used for?▼

ODCS v3.1.0 defines machine-readable contracts specifying schema, SLA, and quality rules between data producers and consumers. Pipelines validate payloads against these contracts at producer boundaries before ingestion, rejecting unannounced schema drift.

Iceberg vs Delta Lake for lakehouse pipelines?▼

This Skill standardizes on Apache Iceberg v3 with deletion vectors and partition evolution, while supporting Delta Lake 4.0 UniForm for Iceberg metadata compatibility. Both provide ACID transactions; the choice depends on your catalog and ecosystem.

Why does my pipeline get S3 503 Slow Down errors?▼

High-volume writes concentrated on single S3 prefixes trigger throttling. Setting the Iceberg table property write.object-storage.enabled = true distributes Parquet files across hashed prefixes, preventing 503 errors.

How do I make pipeline reruns idempotent?▼

Use MERGE INTO operations keyed on composite SHA-256 natural keys with intra-batch deduplication via ROW_NUMBER windowing. A watermark check ensures only newer records update targets, so replays never create duplicates.