Terminal
Terminal/Skill
Design or implement MotherDuck analytical schemas and transformation models, including grain, types, and materialization.
By MotherDuck
Works with
npx skills add motherduckdb/agent-skills --skill motherduck-model-dataFor multi-model work, keep transformations in reviewable SQL files using the project's existing dbt, SQLMesh, or local conventions. If none exist, use stage directories and a model_manifest.yml recording dependencies, materialization, and target database. A single-table request needs only the requested SQL or change.
Use the known source schema and connection. Discover missing types, grain, and join keys before implementing; planning can use supplied schema without a live connection.
NOT NULL aggressively; do not assume primary keys or foreign keys are enforced.raw, staging, and analytics lifecycle stages when the project is non-trivial.query_rw. For an answer, review, or plan, return the requested explanation or SQL without creating a project or mutating the warehouse unless requested.Read only the reference sections needed for the current task.
references/MODELING_PLAYBOOK.md for schema patterns, data-type guidance, CTAS/view decisions, complex types, constraints, project scaffold conventions, and common modeling mistakes.Load related skills only for missing capabilities; reuse established context.
motherduck-duckdb-sql for type syntax and function detailsmotherduck-query for executing DDL, rebuilds, and validation queriesmotherduck-explore for understanding the source schema before remodelingmotherduck-load-data for ingestion paths that feed the modeled tablesmotherduck-manage-guides for durable business definitions and join rules that do not belong in transformation code