Motherduck Enable Self Serve Analytics

Roll out self-serve analytics on MotherDuck for internal teams.

When your AI uses it

Roll out self-serve analytics on MotherDuck for internal teams. Use when deciding the first governed dataset, the first Dive or share, ownership boundaries, and the rollout path from one audience to broader adoption.This is the skill's description: the text your AI reads to decide when the skill applies.

analyticsenablemotherduckself

Read exactly what your AI will be told

motherduck-motherduck-enable-self-serve-analytics/SKILL.md

MotherDuck · MIT · source

---
name: motherduck-enable-self-serve-analytics
description: Roll out self-serve analytics on MotherDuck for internal teams. Use when deciding the first governed dataset, the first Dive or share, ownership boundaries, and the rollout path from one audience to broader adoption.
license: MIT
---

# Enable Self-Serve Analytics

Use this skill when the user wants broad internal access to analytics with clear guardrails, trusted datasets, and a practical rollout path.

This is a use-case skill. It orchestrates `motherduck-explore`, `motherduck-query`, `motherduck-model-data`, `motherduck-create-dive`, and `motherduck-share-data`.

## Start Here: Is a MotherDuck Server Active?

Always determine this first.

- If a **remote MotherDuck MCP server** or **local MotherDuck server** is active, use it.
- If the user has not named the target database, ask which database or workspace will power the rollout.
- Explore the live data model before defining the rollout:
  - trusted source tables
  - candidate curated views
  - department-level dimensions
  - core KPIs
  - share boundaries