motherduck-query

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill when executing SQL queries for analytics, aggregations, transformations, or data exploration against MotherDuck databases.

当你需要针对MotherDuck数据库执行SQL查询以进行数据分析、聚合、转换或数据探索时，请使用本技能。

Write DuckDB SQL, not PostgreSQL SQL, even when using the PG endpoint.
Always use fully qualified
```
"database"."schema"."table"
```
names.
Preserve the intended grain of every result set; state the grain before optimizing or materializing a query.
Filter early, aggregate early, and prefer serving tables or summaries for repeated reads.
Keep SQL obvious, multi-line, and explicit about grain, filters, and output shape.
Treat DDL, DML,
```
ATTACH
```
,
```
DETACH
```
, recovery commands such as
```
CREATE SNAPSHOT
```
,
```
ALTER DATABASE ... SET SNAPSHOT
```
,
```
UNDROP DATABASE
```
, and lifecycle commands such as
```
SHUTDOWN
```
as writes. Use MCP
```
query_rw
```
only when the user explicitly asks for the change and confirms it.
Tag long-lived integrations with
```
custom_user_agent
```
when the connection path supports it.

Confirm the actual tables, columns, and grain before writing SQL.
Write the query in SQL first, then wrap it in Python or TypeScript only if needed.
Use CTEs and DuckDB-native patterns such as
```
GROUP BY ALL
```
,
```
QUALIFY
```
, and
```
arg_max
```
.
Check the plan, row count, and shape for pushdown, unnecessary sorts, or repeated raw rescans.
Materialize expensive repeated queries into serving tables or light views when warranted.

```
references/QUERY_PLAYBOOK.md
```
for DuckDB query patterns, exploration SQL, performance rules, common analytical shapes, and common mistakes

参考
```
references/QUERY_PLAYBOOK.md
```
获取DuckDB查询模式、探索性SQL、性能规则、常见分析结构以及常见错误相关内容