What problem does it solve? Getting data into MotherDuck correctly requires choosing the right loading path for each source type, and picking the wrong one leads to failed loads, slow transfers, or unsupported operations on the Postgres endpoint. ## Core Features & Use Cases - Source-aware loading paths: Classifies sources as object storage/HTTPS, local files, local DuckDB databases, in-memory dataframes, or external databases, then selects CTAS, INSERT...SELECT, COPY, or bulk upload accordingly. - Client path guidance: Distinguishes native DuckDB client workflows from Postgres-endpoint thin-client workflows so local-file COPY, CREATE SECRET, and database uploads are never attempted over the wrong interface. - Format and cloud coverage: Reference material covers CSV, Parquet, JSON, Delta Lake, and Iceberg options plus S3, GCS, and Azure authentication secrets. - Use Case: You have a folder of Parquet files in S3 and a local .duckdb file to consolidate. The skill directs the S3 data through a remote-read CTAS and uploads the local database with CREATE OR REPLACE DATABASE FROM, then validates row counts. ## Quick Start Load the CSV files from my S3 bucket into a new MotherDuck staging table and validate the row counts.