write-script-duckdb

Parameterized DuckDB queries use the $variable syntax for placeholders. Define variables in script comments, then reference them in your SQL using $name. This prevents SQL injection and makes queries reusable across different input values.

Yes. DuckDB supports external database attachments for cross-system queries and integrates with Ducklake for data lake reads. This lets you join and analyze data across local files, external databases, and cloud data sources in a single script.

Parameterized SQL templates work for ad-hoc analytics, data munging, and report generation. They're especially useful when you need to run the same query logic repeatedly with different filter values or time ranges without rewriting the script.

You should be comfortable writing SQL. DuckDB uses standard SQL syntax, so experience with relational databases helps. The Skill handles parameterization and external data attachment; you provide the query logic.

Parameterized queries separate query logic from data values, preventing SQL injection attacks. Variables defined using $name syntax are safely escaped, making parameterized templates safer than string concatenation for dynamic queries.

Yes. DuckDB natively reads CSV, Parquet, and other formats from local storage. Parameterized queries let you reference these files dynamically, making it easy to process multiple files or apply consistent logic across different datasets.