How do I install the Create Dive skill?

Run npx skillmds add majiayu000/create-dive in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Dive safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Dive?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Dive free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Create Dive?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Dive by majiayu000 — Agent Skill

Name: Create Dive
Rating: 4.2 (5 reviews)
Author: majiayu000

Create Dive

Create interactive MotherDuck Dives with live SQL queries. Use when building, previewing, saving, styling, updating, or embedding a Dive, especially when the workflow depends on get_dive_guide, useSQLQuery, theme prompts, and live MotherDuck data.

majiayu000 1f935df 2 files · 3.3 KB Updated Sep 9, 2026 567 repo stars

File contents

Create MotherDuck Dives

Use this skill when the user needs a persistent, shareable Dive rather than a one-off chart or a full customer-facing analytics application.

Source Of Truth

Prefer current MotherDuck Dive docs first.
If MotherDuck MCP is available, call get_dive_guide before generating, saving, or updating a Dive.
Keep theming, local-preview, code-management, and embedding guidance aligned with the current Dive docs.

Default Posture

Validate the underlying SQL and schema first with explore and query.
Keep Dive queries fully qualified and SQL-heavy; let React handle presentation, not data reshaping.
When a Dive uses shared databases in REQUIRED_DATABASES, always suffix the alias (e.g. _share) so it cannot collide with an existing database name. Never set alias to conflict with an existing database name.
Start from a named theme direction such as Corporate Dashboard, Tufte Minimal, or FT Salmon instead of vague visual prompts.
Prefer one query per visual section rather than one giant cross-purpose query.
Preview locally before saving when the environment supports it.
Treat embedded Dives as a lightweight read-only surface; for per-customer serving and policy control, move to build-cfa-app.

Workflow

Explore the live schema and validate the core SQL first.
Decide the Dive story, sections, and interaction model.
Call get_dive_guide if MCP is available.
Build and preview the Dive locally when possible.
Save or update the Dive only after the live queries, theme, and loading states are correct.
If teammates need access, make sure the underlying data is shared appropriately.

Open Next

references/DIVE_DESIGN_GUIDE.md for useSQLQuery mechanics, theming prompts, chart-selection rules, loading/error states, layout patterns, and common Dive implementation gotchas

Related Skills

explore for discovering the real tables, views, and dimensions before visualizing them
query for validating the SQL each Dive section will run
build-dashboard when the work is really a multi-section dashboard composition problem
build-cfa-app when the requirement is a fuller product surface with per-customer isolation or backend policy control

---name: create-divedescription: Create interactive MotherDuck Dives with live SQL queries. Use when building, previewing, saving, styling, updating, or embedding a Dive, especially when the workflow depends on get_dive_guide, useSQLQuery, theme prompts, and live MotherDuck data.license: MIT--- # Create MotherDuck Dives Use this skill when the user needs a persistent, shareable Dive rather than a one-off chart or a full customer-facing analytics application. ## Source Of Truth - Prefer current MotherDuck Dive docs first. - If MotherDuck MCP is available, call `get_dive_guide` before generating, saving, or updating a Dive. - Keep theming, local-preview, code-management, and embedding guidance aligned with the current Dive docs. ## Default Posture - Validate the underlying SQL and schema first with `explore` and `query`. - Keep Dive queries fully qualified and SQL-heavy; let React handle presentation, not data reshaping. - When a Dive uses shared databases in `REQUIRED_DATABASES`, always suffix the `alias` (e.g. `_share`) so it cannot collide with an existing database name. Never set `alias` to conflict with an existing database name. - Start from a named theme direction such as `Corporate Dashboard`, `Tufte Minimal`, or `FT Salmon` instead of vague visual prompts. - Prefer one query per visual section rather than one giant cross-purpose query. - Preview locally before saving when the environment supports it. - Treat embedded Dives as a lightweight read-only surface; for per-customer serving and policy control, move to `build-cfa-app`. ## Workflow 1. Explore the live schema and validate the core SQL first. 2. Decide the Dive story, sections, and interaction model. 3. Call `get_dive_guide` if MCP is available. 4. Build and preview the Dive locally when possible. 5. Save or update the Dive only after the live queries, theme, and loading states are correct. 6. If teammates need access, make sure the underlying data is shared appropriately. ## Open Next - `references/DIVE_DESIGN_GUIDE.md` for `useSQLQuery` mechanics, theming prompts, chart-selection rules, loading/error states, layout patterns, and common Dive implementation gotchas ## Related Skills - `explore` for discovering the real tables, views, and dimensions before visualizing them - `query` for validating the SQL each Dive section will run - `build-dashboard` when the work is really a multi-section dashboard composition problem - `build-cfa-app` when the requirement is a fuller product surface with per-customer isolation or backend policy control

Frequently asked questions