motherduck-partner-delivery

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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

当咨询公司、实施合作伙伴或多客户产品团队需要为多个客户提供可复用的MotherDuck交付模式时，可使用本Skill。

这是一个场景化Skill，它编排了

motherduck-connect

、

motherduck-explore

、

motherduck-model-data

、

motherduck-query

、

motherduck-share-data

和

motherduck-create-dive

。

Start Here: Is a MotherDuck Server Active?

第一步：是否有活跃的MotherDuck服务器？

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.

If no server is active, ask for representative client patterns and regions before proposing the standard delivery model.

请始终先确认这一点。

如果远程MotherDuck MCP服务器或本地MotherDuck服务器处于活跃状态，请直接使用。
如果交付将基于现有工作区进行，请询问哪些客户数据库或工作区已纳入范围。
若有可用的实时配置，请进行探查：
- 当前客户数据库边界
- 区域布局
- 现有的服务账户或共享边界
- 可复用模式与客户特定模式

通过上述探查来确定哪些内容可以标准化，哪些必须保留客户特定属性。

如果没有活跃服务器，请先获取代表性的客户模式和区域信息，再提出标准交付模型。

Use This Skill When

适用场景

The user is delivering MotherDuck solutions across multiple clients.
The user needs region-aware, repeatable architecture.
The user needs standard provisioning with explicit client exceptions.
The goal is a reusable delivery pattern, not a one-off single-client implementation.

用户需要为多个客户交付MotherDuck解决方案
用户需要具备区域感知能力的可复用架构
用户需要带有明确客户例外规则的标准资源配置流程
目标是构建可复用的交付模式，而非一次性的单客户实施

Delivery Defaults

交付默认规则

structural isolation over query-time tenant filtering
one client database or stronger boundary per client
shared architecture, client-specific schema
explicit sharing and revocation per client
versioned templates for provisioning, validation, handoff, and exception tracking

优先采用结构化隔离，而非查询时租户过滤
为每个客户分配一个独立数据库或更强的隔离边界
共享架构，客户特定模式
为每个客户明确设置共享与权限撤销规则
为资源配置、验证、交付交接和例外跟踪提供版本化模板

Workflow

工作流程

Confirm whether live MotherDuck discovery is available.
Classify the client patterns.
Inspect the existing regional and database layout if available.
Standardize the architecture and provisioning path.
Define the repeatable validation pack for every client environment.
Document client-specific exceptions.
Produce the handoff assets and validation checks.

When this skill produces a native DuckDB (

md:

) connection, watermark it with

custom_user_agent=agent-skills/2.2.0(harness-<harness>;llm-<llm>)

. If metadata is missing, fall back to

harness-unknown

and

llm-unknown

确认是否可进行MotherDuck实时探查
对客户模式进行分类
若有可用信息，检查现有区域和数据库布局
标准化架构和资源配置路径
定义适用于所有客户环境的可复用验证包
记录客户特定例外规则
生成交付交接资产和验证检查项

当本Skill生成原生DuckDB（

md:

）连接时，请为其添加水印：

custom_user_agent=agent-skills/2.2.0(harness-<harness>;llm-<llm>)

。若元数据缺失，则回退使用

harness-unknown

和

llm-unknown

。

Output

输出

The output of this skill should be:

the default multi-client pattern
the standard provisioning checklist
the region and isolation posture
the client-specific exceptions

If the caller explicitly asks for structured JSON, return raw JSON only with no Markdown fences or prose before/after it. This is mainly for automated tests, regression checks, or downstream tooling that needs a stable machine-readable shape. Normal human-facing use of the skill can stay in prose unless JSON is explicitly requested.

Use this exact top-level shape when JSON is requested:

json

{
  "summary": {},
  "assumptions": [],
  "implementation_plan": [],
  "validation_plan": [],
  "risks": []
}

本Skill的输出应包含：

默认多客户模式
标准资源配置检查清单
区域与隔离策略
客户特定例外规则

如果调用者明确要求结构化JSON，则仅返回原始JSON，不要添加Markdown围栏或前后说明文字。这主要用于自动化测试、回归检查或需要稳定机器可读格式的下游工具。面向普通用户的常规使用场景下，可保留 prose 格式，除非明确要求JSON。

当要求返回JSON时，请使用以下顶层结构：

json

{
  "summary": {},
  "assumptions": [],
  "implementation_plan": [],
  "validation_plan": [],
  "risks": []
}

References

参考资料

```
references/PARTNER_DELIVERY_GUIDE.md
```
-- preserved detailed guidance that used to live in this skill

```
references/PARTNER_DELIVERY_GUIDE.md
```
-- 保留了原属于本Skill的详细指导内容

Runnable Artifact

可运行工件

```
artifacts/client_delivery_example.py
```
-- MotherDuck-backed Python example showing one database namespace per client and a simple validation pass across client environments
```
artifacts/client_delivery_example.ts
```
-- TypeScript companion artifact with the same delivery output contract

Run it with:

bash

uv run --with duckdb python skills/motherduck-partner-delivery/artifacts/client_delivery_example.py

Run the same artifact against temporary MotherDuck databases:

bash

MOTHERDUCK_ARTIFACT_USE_MOTHERDUCK=1 \
uv run --with duckdb python skills/motherduck-partner-delivery/artifacts/client_delivery_example.py

Validate the TypeScript companion artifact:

bash

uv run scripts/test_typescript_artifacts.py

```
artifacts/client_delivery_example.py
```
-- 基于MotherDuck的Python示例，展示了为每个客户分配一个数据库命名空间，并在客户环境间执行简单验证
```
artifacts/client_delivery_example.ts
```
-- TypeScript配套工件，具有相同的交付输出约定

运行方式：

bash

uv run --with duckdb python skills/motherduck-partner-delivery/artifacts/client_delivery_example.py

针对临时MotherDuck数据库运行同一工件：

bash

MOTHERDUCK_ARTIFACT_USE_MOTHERDUCK=1 \
uv run --with duckdb python skills/motherduck-partner-delivery/artifacts/client_delivery_example.py

验证TypeScript配套工件：

bash

uv run scripts/test_typescript_artifacts.py

motherduck-partner-delivery

Original

Translation

Partner Delivery

合作伙伴交付

Start Here: Is a MotherDuck Server Active?

第一步：是否有活跃的MotherDuck服务器？

Use This Skill When

适用场景

Delivery Defaults

交付默认规则

Workflow

工作流程

Output

输出

References

参考资料

Runnable Artifact

可运行工件

Related Skills

相关Skill