write-script-duckdb

Generate parameterized DuckDB scripts with frontmatter and $name syntax.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/adamkingsbury/unified-data-model --skill write-script-duckdb-adamkingsbury
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-script-duckdb
Source: https://github.com/adamkingsbury/unified-data-model/tree/main/.claude/skills/write-script-duckdb
Command: npx skills add https://github.com/adamkingsbury/unified-data-model --skill write-script-duckdb-adamkingsbury

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing DuckDB queries can be error-prone and hard to standardize across projects. This Skill provides a structured template and guidance for creating parameterized DuckDB scripts, improving consistency, readability, and reusability.

Core Features & Use Cases

  • Standardized parameter syntax: Define arguments with comments and use $name style for dynamic values.
  • Ducklake integration: Attach and query data from a data lake using named attachments.
  • External database connections: Connect to external databases via resource attachments and TYPE hints.
  • S3 file operations: Read data from S3 storage in DuckDB-friendly formats.

Quick Start

Place scripts in a folder, then run wmill script generate-metadata and wmill sync push to deploy.

Frequently Asked Questions about write-script-duckdb

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

FAQPage Schema
How do I write parameterized DuckDB scripts for external databases?▼

DuckDB scripts for external databases use a standardized, parameterized template with $name syntax for dynamic values and frontmatter-driven entry points. This enforces deterministic execution and improves consistency across local scripts, Ducklake data lakes, and S3-based file operations.

Can I use DuckDB to query data lakes with named attachments?▼

Ducklake integration allows you to attach and query data from a data lake using named attachments within parameterized scripts. This standardizes data lake querying by combining frontmatter-driven entry points with documented commands for reliable execution.

What is the best way to standardize DuckDB queries across projects?▼

Standardizing DuckDB queries requires a structured template with parameter definitions using $name syntax and frontmatter-driven entry points. This approach improves consistency, readability, and reusability across local scripts, S3 file operations, and external database connections.

How do I read data from S3 storage in DuckDB-friendly formats?▼

S3 file operations in DuckDB-friendly formats are supported through parameterized scripts that enforce documented commands for deterministic execution. Scripts use frontmatter-driven entry points and $name syntax to dynamically define arguments for reading S3 data.

Does this DuckDB scripting approach work with resource attachments and TYPE hints?▼

External database connections are supported via resource attachments and TYPE hints within the parameterized script template. This enforces a frontmatter-driven entry point and documented commands to ensure deterministic execution across connected external databases.