explore-data

Profiles dlt pipeline data and plans altair charts in an analysis_plan.md artifact.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/aminojagh/LLMZC --skill explore-data-aminojagh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: explore-data
Source: https://github.com/aminojagh/LLMZC/tree/main/05_02_dlt_workshop/.claude/skills/explore-data
Command: npx skills add https://github.com/aminojagh/LLMZC --skill explore-data-aminojagh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dlt, altair, ibis, and includes references (resource) components.

What problem does it solve? Analysts working with dlt pipelines often need to understand unfamiliar datasets and turn business questions into charts without manually writing SQL and visualization code from scratch. This Skill connects to a pipeline, profiles its tables, and produces a validated chart plan that a notebook builder can consume. ## Core Features & Use Cases - Pipeline Discovery and Profiling: Connects to dlt pipelines via dlthub MCP tools or Python fallback, listing tables, schemas, row counts, anomalies, and PII flags. - Chart Planning: Translates a business question into a chart spec (type, axes, aggregation, time grain) with validated SQL and altair code, one chart per invocation. - Structured Artifact Output: Writes or appends to a dated analysis_plan.md file with connection info, profile summary, questions, data gaps, and chart blocks for downstream notebook generation. - Use Case: Ask "what's the revenue trend" against your orders pipeline and receive a confirmed monthly line-chart spec with SQL and altair code, ready for the build-notebook step. ## Quick Start Ask the assistant to explore your dlt pipeline and answer a question like "explore my data -- what's the revenue trend by month?"

Frequently Asked Questions about explore-data

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

FAQPage Schema
How do I explore data in a dlt pipeline?▼

Connect using dlthub MCP tools like list_pipelines, list_tables, and get_table_schema, or fall back to Python with dlt.attach and pipeline.dataset(). Then profile tables, pick a business question, and plan one chart with SQL and altair code.

How do I create charts from dlt pipeline data?▼

Write an aggregated SQL query through dataset("SELECT ...").df() and render it with altair using typed encodings like :T, :Q, and :N. Match the chart type to the question: line for trends, bar for comparisons, scatter for relationships.

Can I analyze a standalone DuckDB file without a dlt pipeline?▼

Yes. Connect with dlt.pipeline(pipeline_name="adhoc", destination=dlt.destinations.duckdb("<path>")) and then use pipeline.dataset() normally. Row counts, schema inspection, and SQL queries work the same way.

What if the dlthub MCP tools are unavailable?▼

Run uv run dlthub ai status to diagnose the MCP server and try dlthub ai init to fix it. If MCP cannot be restored, fall back to the Python path using dlt.attach or dlt.pipeline for all discovery and queries.

When should I use ibis instead of SQL with dlt datasets?▼

Use SQL by default for chart queries since it is concise for aggregations. Switch to table.to_ibis() when you need complex joins, computed columns, or group-by logic that raw SQL makes awkward, such as joining dlt parent and child tables on _dlt_id.