debug-pipeline

Inspect dlt pipeline traces and load packages to diagnose post-execution errors.

53|5|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/dlt-hub/dlthub-ai-workbench --skill debug-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-pipeline
Source: https://github.com/dlt-hub/dlthub-ai-workbench/tree/main/workbench/rest-api-pipeline/skills/debug-pipeline
Command: npx skills add https://github.com/dlt-hub/dlthub-ai-workbench --skill debug-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you troubleshoot and resolve errors or unexpected behavior in your dlt data pipelines after they have run, whether successfully or with failures.

Core Features & Use Cases

  • Inspect Pipeline State: Examine traces, load packages, schemas, and data to understand what happened during a pipeline run.
  • Diagnose Errors: Identify common issues like missing credentials, failed jobs, or infinite loops.
  • Use Case: After a pipeline fails to load data, use this Skill to inspect the error messages in the load package and identify that a required API key was missing.

Quick Start

Use the debug-pipeline skill to inspect the last run of the 'my_data_pipeline' pipeline.

Frequently Asked Questions about debug-pipeline

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

FAQPage Schema
How do I debug a dlt pipeline that failed to load data?

To debug a failed dlt pipeline, inspect the load package and traces using dlt CLI commands to identify error messages, such as missing credentials or failed jobs, preventing data loading.

Why does my dlt pipeline run fail with missing credentials?

Your dlt pipeline run fails with missing credentials when configuration is incomplete; inspect pipeline traces and load packages to diagnose configuration issues and verify required API keys are present.

How can I inspect the load package of a dlt pipeline after execution?

You can inspect a dlt pipeline load package after execution by using dlt CLI trace, load-package, and info commands, alongside direct file inspection, to analyze schemas and raw data.

What is the best way to diagnose infinite loops in dlt incremental loading?

The best way to diagnose infinite loops in dlt incremental loading is to inspect the pipeline state and traces post-execution to identify data selection issues within your incremental loading configuration.

Do I need the dlt CLI to troubleshoot pipeline errors?

Yes, you need the dlt CLI to troubleshoot pipeline errors because it provides the trace, load-package, and info commands required to inspect pipeline state and diagnose HTTP request failures.

Can I analyze raw data from a dlt pipeline run without CLI commands?

Yes, you can analyze raw data from a dlt pipeline run without CLI commands by performing direct file inspection on the load package contents to examine schemas and loaded data directly.