OpenParable
Skip to content
← Back to skills

Motherduck Query

Apps & Automation
motherduck-query

Motherduck Query is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/motherduck-query-motherduckdb-agent-skills-2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/motherduck-query, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Query MotherDuck

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

Prerequisites

  • MotherDuck connection established via motherduck-connect
  • Target database and tables identified via motherduck-explore

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 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.

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

  • 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