using-duckdb
data-goblin/power-bi-agentic-development / plugins/etl/skills/using-duckdb
queries OneLake tables with DuckDB , which improves: freshness and quality checks without Spark
Details
- judge’s score
- 9/10
- place
- outside the packs
- publisher
- data-goblin
- status
- new
- pinned commit
- 4cc6195 on GitHub (new tab)
- skill’s last commit
- Jul 16, 2026
- repo stars
- 1,060
- main type
- Data
Judgement
Precise description and clear triggers. Real pitfalls (CHAIN 'cli', 60-minute token, object cache) and exact commands. Score held back by path inconsistencies and a missing reference.
reservations
- Reference to executing-spark not provided: cannot verify the rest of the write-back.
- Inconsistent paths: GUID identifier locally, name suffixed .Lakehouse in the notebook.
- The access token is interpolated into f-string SQL strings, which is fragile and can leak into logs.
- No pinned DuckDB version or extensions, although delta and azure evolve quickly.
- Triggering
- 2/2
- Added value
- 2/2
- Precision
- 2/2
- Scope
- 2/2
- Quality
- 1/2
Alerts
1 alert, by category
Data
- medium risk
Storage token written in clear text in an SQL query and a temp_*.duckdb database on disk: avoid in shared notebooks.
Original description
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", "…
added on Oct 19, 2026 · license GPL-3.0