Motherduck Partner Delivery

---
name: motherduck-partner-delivery
description: Deliver repeatable MotherDuck architectures across multiple clients. Use when a consultancy, agency, or multi-client product team needs to standardize isolation, provisioning, regional deployment, sharing boundaries, and client-specific exceptions across client engagements.
license: MIT
---

# Partner Delivery

Use this skill when a consultancy, implementation partner, or multi-client product team needs a repeatable MotherDuck delivery pattern across several clients.

This is a use-case skill. It orchestrates `motherduck-connect`, `motherduck-explore`, `motherduck-model-data`, `motherduck-query`, `motherduck-share-data`, and `motherduck-create-dive`.

## Start Here: Is a MotherDuck Server Active?

Always determine this first.

- If a **remote MotherDuck MCP server** or **local MotherDuck server** is active, use it.
- If the delivery will run against an existing workspace, ask which client databases or workspaces are already in scope.
- Explore the live setup when available:
  - current client database boundaries
  - regional layout
  - existing service-account or share boundaries
  - reusable schemas vs client-specific schemas

Use that discovery to decide what can be standardized and what must stay client-specific.