motherduck-build-dashboard

Compose multi-section MotherDuck Dive dashboards with KPIs, trend charts, and breakdowns.

Updated Oct 15, 2019
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill motherduck-build-dashboard-kkkaoru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: motherduck-build-dashboard
Source: https://github.com/kkkaoru/dotfiles/tree/main/.agents/skills-stroage/motherduck-build-dashboard
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill motherduck-build-dashboard-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires duckdb, and includes references (resource) components.

What problem does it solve? Turning existing MotherDuck data into a coherent, shareable analytics dashboard requires schema discovery, per-section SQL, and Dive composition; this Skill orchestrates that end-to-end workflow so the result is a saved workspace artifact rather than scattered queries. ## Core Features & Use Cases - Schema-first dashboard design: Explores live MotherDuck tables, metrics, dimensions, and date ranges before choosing the dashboard story and sections. - Structured composition defaults: Enforces one story per dashboard with one KPI row, one primary trend chart, optional breakdown chart, and optional detail table, with heavy shaping done in SQL. - Reusable patterns and runnable artifacts: Ships copy-pasteable Sales, Product Analytics, and Operational Metrics Dive templates plus Python and TypeScript example artifacts that produce KPI, trend, breakdown, and detail outputs. - Use Case: Ask for a revenue dashboard over your MotherDuck orders table and receive the dashboard story, validated per-section SQL, a Dive implementation plan, and the save/update path. ## Quick Start Ask the assistant to build a MotherDuck Dive dashboard with KPIs, a monthly trend, and a category breakdown over your existing analytics database.

Frequently Asked Questions about motherduck-build-dashboard

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

FAQPage Schema
How do I build a dashboard on MotherDuck data?

Explore the live schema first to identify key metrics, dimensions, and date columns, then write one SQL query per dashboard section and compose them into a Dive. This Skill orchestrates that workflow and saves the result as a shareable workspace artifact.

What is a MotherDuck Dive dashboard?

A Dive is a saved, shareable MotherDuck workspace artifact built as a React component using useSQLQuery and Recharts. It renders KPIs, trend charts, breakdowns, and detail tables against live MotherDuck data.

When should I use a Dive dashboard instead of a full analytics app?

Use a Dive when the result is a workspace analytics surface with one KPI row, a trend, and a breakdown. For customer-facing products needing per-customer isolation, use the motherduck-build-cfa-app approach instead.

How many charts and KPIs should a dashboard have?

The Skill enforces one story per dashboard with a maximum of 5 KPIs, 2 charts, and 1 detail table. If more sections are needed, split them into separate dashboards to keep the narrative focused.

Why does my Dive chart show NaN or blank values?

Query results return unknown types, so every numeric value must pass through the N() helper before rendering. Also guard data with Array.isArray and format dates in SQL with strftime rather than parsing them in JavaScript.