motherduck-enable-self-serve-analytics

Plans governed self-serve analytics rollouts on MotherDuck with curated datasets, Dives, and shares.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Internal teams often depend on a central data team for every analytics question. This Skill produces a governed rollout plan for self-serve analytics on MotherDuck, defining the first audience, first trusted dataset, first Dive or share, and the ownership boundaries needed to expand safely. ## Core Features & Use Cases - Rollout Planning: Selects the first audience, first asset, governing dataset, ownership model, and guardrails for a staged self-serve launch. - Orchestration of MotherDuck Skills: Coordinates explore, query, model-data, create-dive, and share-data skills against the live workspace data model. - Runnable Artifacts: Ships Python and TypeScript examples that publish a curated view and produce team KPI output for a first rollout asset. - Use Case: A data lead wants customer success managers to answer their own account-health questions. The Skill inspects the workspace, publishes a curated customer_health view, and defines a team KPI Dive with explicit ownership and sharing boundaries. ## Quick Start Ask the assistant to plan a self-serve analytics rollout on MotherDuck for one internal team, starting with a curated dataset and a single Dive.

Frequently Asked Questions about motherduck-enable-self-serve-analytics

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

FAQPage Schema
How do I roll out self-serve analytics on MotherDuck?

Start with one audience and one curated dataset rather than broad access. Publish a single Dive or share on top of that dataset, document the metric owner and access boundary, and expand only after the first workflow is stable.

When should I use a MotherDuck Dive versus a share?

Use a Dive when the audience needs a ready-made interactive answer surface with filters and live refresh. Use a share when the consuming team wants direct SQL access or needs to reuse the data in another tool or workflow.

Does this skill work without an active MotherDuck server?

It first checks for a remote MotherDuck MCP server or local server and explores the live data model if available. If no server is active, it asks for a table list and target audience before drafting the rollout plan.

Can I use this for customer-facing or embedded analytics?

No, this skill targets internal audiences only. For external users or embedded product analytics, the documentation directs you to the motherduck-build-cfa-app skill instead of stretching a self-serve setup.

What output does the self-serve rollout plan include?

The output names the first audience, the first asset, the governing dataset, the ownership model, and the rollout guardrails. If explicitly requested, it can return structured JSON with summary, assumptions, implementation plan, validation plan, and risks.