What problem does it solve? When a dlt data pipeline fails, hangs, or silently loads zero rows, finding the root cause requires digging through traces, load packages, and destination error messages. This Skill provides a structured debugging workflow that increases logging verbosity, runs the pipeline, and inspects every artifact to pinpoint issues like missing credentials, paginator loops, rate limits, or wrong data selectors. ## Core Features & Use Cases - Verbosity Setup: Configures log levels, HTTP error body visibility, and progress logging in .dlt/config.toml and pipeline code before debugging, then reverts changes afterward. - Failure Diagnosis: Interprets common exceptions like ConfigFieldMissingException and PipelineFailedException, and detects infinite paginator loops, HTTP 429 retry stalls, and zero-row loads. - Post-Mortem Inspection: Uses the dlthub CLI to examine pipeline traces, load packages, failed jobs, and raw load files (INSERT VALUES, JSONL, Parquet, CSV) per destination. - Use Case: Your REST API pipeline runs for 20 minutes without finishing. The Skill identifies a JSONResponseCursorPaginator with a wrong cursor_path causing an infinite loop and shows how to fix it. ## Quick Start Ask the AI to debug your dlt pipeline by name, for example: debug my github_pipeline that keeps failing with a 401 error.