des-dlt-ingestion

Translate DES source requirements into dlt ingestion pipelines with evidence.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/DKSang/DES-SKILL --skill des-dlt-ingestion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: des-dlt-ingestion
Source: https://github.com/DKSang/DES-SKILL/tree/main/skills-stack/des-dlt-ingestion
Command: npx skills add https://github.com/DKSang/DES-SKILL --skill des-dlt-ingestion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you design and implement dependable dlt ingestion pipelines that load DES Bronze datasets with correct write behavior, incremental state, schema evolution handling, and evidence for downstream phases.

Core Features & Use Cases

  • dlt-based ingestion design for DES: Converts DES source assessment and ingestion specifications into a source/resource/destination plan.
  • Write disposition + incremental state control: Selects append, replace, or merge, and defines cursor/state behavior including lag windows and backfill strategy.
  • Schema evolution and contract behavior: Documents how dlt should react to drift (new columns, type changes, nested structure changes) and captures resulting evidence.
  • Evidence-driven handoff: Produces load/pipeline evidence artifacts for Phase 08/09/12/13 and routes the work to the next stack skill (DuckDB/dbt/Fabric/Provero/Airflow).

Quick Start

Use the des-dlt-ingestion skill to generate a dlt ingestion plan and evidence for your REST API or SQL database source, aligned to your DES Phase 08 ingestion specification and Bronze layout.

Frequently Asked Questions about des-dlt-ingestion

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

FAQPage Schema
How do I build a dlt ingestion pipeline for REST APIs with incremental loading?

Schema evolution policies in dlt ingestion control how the pipeline reacts to schema drift, capturing new columns, type changes, and nested structure modifications while enforcing data contracts and outputting standardized evidence for downstream handoff.

Can I use dlt to handle schema drift and enforce data contracts during ingestion?

dlt ingestion pipelines handle schema drift by documenting contract behavior for new columns, type changes, and nested structures, capturing resulting evidence to enforce data contracts during Bronze layer loading.

What is the best way to configure write disposition and merge strategies in dlt pipelines?

dlt ingestion pipelines support REST APIs, SQL databases, and filesystem or cloud storage sources, translating DES-defined source specifications into executable loading plans with traceable pipeline evidence across multiple ingestion phases.

How do I generate pipeline evidence for downstream dbt or Airflow handoffs after dlt ingestion?

Incremental loading in dlt ingestion manages cursor state, lag windows, and backfill strategies to control append, replace, or merge write dispositions, ensuring dependable Bronze dataset loads from REST API or SQL database sources.

Does dlt ingestion support both SQL databases and cloud storage filesystem sources?

To configure write disposition and merge strategies in dlt pipelines, select append, replace, or merge modes based on source assessment, then define incremental cursor state, backfill strategies, and dataset naming for Bronze layer loads.

When should I use dlt pipeline evidence artifacts in a data engineering workflow?

dlt ingestion generates pipeline evidence artifacts by producing standardized load records during Bronze dataset ingestion, documenting write disposition, incremental state, and schema evolution behavior for downstream handoff to DuckDB, dbt, Fabric, Provero, or Airflow.