What problem does it solve?
This skill helps you decide whether DuckLake is the right MotherDuck storage pattern when object-store semantics, open table format, and file-aware maintenance are genuinely part of the requirement.
Core Features & Use Cases
- Storage decision guidance: Decide between native MotherDuck storage and DuckLake based on concrete needs like open table format, durable object storage as the source of truth, BYOB bucket ownership, or file-aware maintenance.
- Mode selection & constraints: Pick the right DuckLake operating mode (fully managed, BYOB with MotherDuck compute, or BYOB with own compute) and verify regional/bucket constraints for BYOB proposals.
- Operational posture & gotchas: Define ingestion/maintenance expectations explicitly, including inlining posture and the need for explicit maintenance/compaction—without assuming background magic or one-size-fits-all performance.
Quick Start
Ask an AI to review your workload goals and recommend whether to use DuckLake versus native MotherDuck storage, including the best DuckLake mode and what maintenance you must plan for.