using-duckdb
Query Fabric lakehouse and warehouse data using DuckDB, either locally or inside a Fabric notebook. Automatically invoke when the user mentions "DuckDB", "query Delta tables locally", or asks to "attach DuckDB to a lakehouse", "query OneLake data", "explore lakehouse data", "data freshness check", "validate data quality", "use DuckDB in Fabric".
npx skills add data-goblin/power-bi-agentic-development --skill using-duckdb --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Using DuckDB with Fabric Query Delta Lake tables and raw files in OneLake using DuckDB. Works both locally (CLI/Python) and inside Fabric notebooks. Read-only; for writes, use the `executing-spark` skill. ## Two Modes | Mode | Where it runs | Auth | Best for | |------|--------------|------|----------| | **Local** | Developer machine | Azure CLI (`az login`) | Exploration, validation, ad-hoc analysis | | **In-notebook** | Fabric Spark container | `notebookutils.credentials.getToken('storage')` | Combining DuckDB speed with Spark write-back | ## Local: Prerequisites - DuckDB installed (`brew install duckdb` on macOS) - Azure CLI authenticated (`az login`) - Extensions installed: `INSTALL delta; INSTALL azure;` (one-time) ## Local: Querying Delta Tables ```bash WS_ID=$(fab get "Workspace.Workspace" -q "id" | tr -d '"') LH_ID=$(fab get "Workspace.Workspace/LH.Lakehouse" -q "id" | tr -d '"') duckdb -c " LOAD delta; LOAD azure; CREATE SECRET (TYPE azure, PROVIDER credential_chain, CHAIN 'cli'); SELECT * FROM delta_scan( 'abfss://${WS_ID}@onelake.dfs.fabric.microsoft.com/${LH_ID}/Tables/schema/table' ) LIMIT 10; " ``` The `CHAIN 'cli'` parameter uses Azure CLI credentials. Without it, D
- Two Modes
- Local: Prerequisites
- Local: Querying Delta Tables
- Local: Querying Raw Files
- In-Notebook: Attaching DuckDB to a Lakehouse
- Auto-Discovering Tables
- OneLake Path Format
- Common Patterns
- References
duckdb -c "
LOAD delta; LOAD azure;
CREATE SECRET (TYPE azure, PROVIDER credential_chain, CHAIN 'cli');
SELECT * FROM delta_scan(
LOAD azure;
SELECT * FROM read_csv('${BASE}/data.csv') LIMIT 10;
SELECT * FROM read_parquet('${BASE}/facts.parquet') LIMIT 10;
SELECT * FROM read_json('${BASE}/events/*.json');What does the using-duckdb skill do?
Query Fabric lakehouse and warehouse data using DuckDB, either locally or inside a Fabric notebook. Automatically invoke when the user mentions "DuckDB", "query Delta tables locally", or asks to "attach DuckDB to a lakehouse", "query OneLake data", "explore lakehouse data", "data freshness check", "validate data quality", "use DuckDB in Fabric".
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill using-duckdb --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From data-goblin/power-bi-agentic-development, a repository with 833 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
