DuckDB

DE//AGENT currently lists 5 resources under DuckDB: 3 skills, 2 projects. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Prove a join cannot fan out before writing it — via SQL Review
• Spot NULL-unsafe `NOT IN` and `=` predicates — via SQL Review
• State the grain of a result set in one sentence — via SQL Review
• Express a quality contract as executable checks — via Pipeline → DQ → quarantine → publish
• Design a quarantine table with a reason — via Pipeline → DQ → quarantine → publish
• Alert on the quarantine rate, not just on failure — via Pipeline → DQ → quarantine → publish
• Read a plan bottom-up and name the expensive node — via SQL Query Plan Explainer
• Detect cardinality misestimation from stale statistics — via SQL Query Plan Explainer

7 more objectives live on the individual resource pages.

These resources map to stages: Python + SQL (2), Reliability (1), Warehousing (1), Data Quality (1). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. SQL Review score 39.9 — beginner
2. Pipeline → DQ → quarantine → publish score 38.65 — intermediate
3. SQL Query Plan Explainer score 38.5 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: SQL Review, dbt → warehouse → tests → docs.

Security-flagged entries: SQL Review (1 flag), Pipeline → DQ → quarantine → publish (2 flags), SQL Query Plan Explainer (1 flag), Pipeline Test Author (2 flags), dbt → warehouse → tests → docs (4 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• SQL Review — Reviews a SQL statement for fan-out joins, NULL-unsafe predicates, implicit casts, non-deterministic ordering, and functions that silently change grain. details
• Pipeline → DQ → quarantine → publish — Put a contract in front of a table: validate each batch, publish the clean rows, quarantine the rest with reasons, and alert on the quarantine rate. details
• SQL Query Plan Explainer — Reads EXPLAIN / EXPLAIN ANALYZE output and explains scans, joins, spills and estimated-vs-actual row skew, then proposes the single highest-impact change. details
• Pipeline Test Author — Builds a local DuckDB/pyarrow harness with tiny fixtures so pipeline logic is testable in CI without a cluster, and asserts on invariants, not snapshots. details

Real install commands from the registry — read the source before running any of them:

npx de-agent-platform add sql-review

SQL Review — review first

npx de-agent-platform add sql-query-plan-explainer

SQL Query Plan Explainer — review first

npx de-agent-platform add pipeline-test-author

Pipeline Test Author — review first

Official source: DuckDB (license: MIT) — start there for the canonical documentation, then come back for the vetted registry entries.

Adjacent topics: Python (2 shared), SQL (2 shared), PostgreSQL (2 shared), Apache Parquet (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.