What problem does it solve? Setting up connectivity to MotherDuck involves choosing between the Postgres endpoint, native DuckDB API, pg_duckdb, and JDBC, each with different authentication, SSL, and scaling requirements. This Skill guides that selection and provides working connection code so applications connect correctly on the first attempt. ## Core Features & Use Cases - Connection Method Selection: Decision guidance for PG endpoint, native DuckDB API, pg_duckdb, and DuckDB-WASM based on workload type. - Ready-to-Use Code Examples: Python (psycopg2, SQLAlchemy, duckdb) and Node.js (pg, @duckdb/node-api) snippets with SSL and token handling. - Read Scaling & Session Affinity: Configuration of read-scaling tokens, session_hint, and attach modes for high-concurrency read workloads. - Use Case: A backend engineer building a serverless analytics API uses the PG endpoint connection string with environment-managed tokens, verifies connectivity with SELECT 1, and adds session_hint-based read scaling when concurrent read traffic grows. ## Quick Start Ask the assistant to connect your application to MotherDuck and it will recommend the right connection method with working code.