motherduck-create-dive

Create persistent MotherDuck Dives combining React components with live DuckDB SQL.

53|3|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/motherduckdb/agent-skills --skill motherduck-create-dive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: motherduck-create-dive
Source: https://github.com/motherduckdb/agent-skills/tree/main/plugins/motherduck-skills-claude/skills/motherduck-create-dive
Command: npx skills add https://github.com/motherduckdb/agent-skills --skill motherduck-create-dive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you create and safely manage persistent, shareable MotherDuck Dives so your team can build interactive React + SQL analytics that stay live over the workspace data.

Core Features & Use Cases

  • Dive authoring & editing: Build new Dives or update existing ones with correct version handling and minimal overwrites.
  • Live workflow with validation: Explore schema and validate SQL first to ensure each Dive section runs correctly with the right loading, empty, and error states.
  • Team sharing and embedding: Configure required resources for teammate access, and support embedding read-only Dive experiences when you need an app-ready surface.

Quick Start

Create a persistent, shareable Dive that visualizes the current revenue trend by month, using MotherDuck MCP to fetch the Dive guide and validate the underlying SQL before saving.

Frequently Asked Questions about motherduck-create-dive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a live MotherDuck Dive combining React components with SQL?

To create a MotherDuck Dive, you build React components using the required useSQLQuery hook, validate your live DuckDB SQL against the workspace schema first, and configure required resources for team sharing to ensure the interactive analytics stay live.

How does SQL validation work when authoring MotherDuck Dives?

SQL validation in MotherDuck Dives works by checking your queries against the workspace schema before saving, ensuring each Dive section correctly handles loading, empty, and error states to prevent broken interactive analytics.

Can I embed a read-only MotherDuck Dive session into an external application?

Yes, you can embed read-only MotherDuck Dive sessions in applications by configuring the required resource metadata, providing an app-ready surface that securely displays live SQL analytics without allowing viewer modifications.

What is the best way to manage version history when editing existing Dives?

The best way to manage Dive version history is to apply updates through a Dives-as-code workflow that ensures correct version handling and performs minimal overwrites, preserving previous iterations of your React and SQL components.

Do I need to use the MotherDuck MCP to build Dives?

You should use the MotherDuck MCP to fetch the get_dive_guide when available, ensuring your Dive follows the required React + useSQLQuery component contract and keeping required resource metadata aligned with actual dependencies.