agentsclimarketplace

Motherduck query

Skill motherduckdb/agent-skills/skills/motherduck-query

Opinionated AI agent skills for building applications with MotherDuck

Install
npx -y skills add motherduckdb/agent-skills --skill motherduck-query

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Execute DuckDB SQL queries against MotherDuck databases. Use when running analytics, aggregations, transformations, or any SQL operation. Covers query best practices, CTEs, window functions, QUALIFY, and performance optimization.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.3 KB, 447 tokens by cl100k_base, as published. Nobody here has run it

Query MotherDuck

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

Prerequisites

  • An established MotherDuck connection (or an active MotherDuck MCP server)
  • Target database and tables identified

Default Posture

  • 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 the MotherDuck MCP query_rw tool when the user's change request authorizes the write. Ask for confirmation only when the action is destructive, externally visible, or outside the stated scope.
  • Tag long-lived integrations with custom_user_agent when the connection path supports it.

Workflow

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

Open Next

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

Related Skills

  • motherduck-connect for session setup
  • motherduck-duckdb-sql for syntax and function reference
  • motherduck-explore for understanding the source schema before writing queries

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.