Use DuckLake on MotherDuck

Use this skill when the storage decision is genuinely about open table format and object-store behavior, not just about where to put another analytical table.

Source Of Truth

• Prefer current MotherDuck DuckLake docs first.
• Use the upstream DuckLake and DuckDB extension docs only to clarify extension-level behavior that MotherDuck docs reference.
• Keep the guidance aligned with the documented product posture:
  • native MotherDuck first
  • upstream DuckLake v1.0 is production-ready, but MotherDuck's DuckLake docs define the MotherDuck product surface and preview/compatibility limits; verify the current DuckDB/DuckLake version matrix instead of assuming a pinned version
  • fully managed, BYOB, and own-compute paths are distinct
  • maintenance and compaction are explicit operations, not background magic

Default Posture