motherduck-share-data

Create and manage zero-copy read-only MotherDuck database shares with SQL.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Distributing MotherDuck databases to teammates, partner organizations, or the public usually means copying data or building export pipelines. This Skill guides you through MotherDuck's native share mechanism so recipients query a read-only, zero-copy clone of your database with explicit access, visibility, and update controls. ## Core Features & Use Cases - Share Creation with Explicit Controls: Create shares with deliberate ACCESS (ORGANIZATION, RESTRICTED, UNRESTRICTED), VISIBILITY (DISCOVERABLE, HIDDEN), and UPDATE (MANUAL, AUTOMATIC) settings instead of implicit defaults. - Recipient and Snapshot Management: Grant or revoke read access for named users, publish manual snapshots with UPDATE SHARE, and guide consumers through ATTACH and REFRESH DATABASE. - Use Case: A data team needs to deliver a versioned analytics dataset to an external partner. They create a RESTRICTED, HIDDEN, MANUAL share, grant read access to specific users, and publish new snapshots on a defined cadence. ## Quick Start Ask the assistant to create a MotherDuck share from your analytics database with organization access, discoverable visibility, and automatic updates, then list your owned shares to verify.

Frequently Asked Questions about motherduck-share-data

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

FAQPage Schema
How do I create a MotherDuck share from a database?

Use CREATE SHARE with explicit options, for example CREATE SHARE my_share FROM my_database with ACCESS ORGANIZATION, VISIBILITY DISCOVERABLE, and UPDATE MANUAL. Then verify the result with LIST SHARES or the MD_INFORMATION_SCHEMA.OWNED_SHARES view.

How do recipients access a MotherDuck shared database?

Recipients attach the share using ATTACH with the share URL and an alias, then query it read-only with fully qualified table names. For manual-update shares, they run REFRESH DATABASE to pull newly published snapshots.

What is the difference between UPDATE MANUAL and UPDATE AUTOMATIC shares?

UPDATE MANUAL freezes the share at a snapshot until the owner runs UPDATE SHARE, suiting versioned data products and reproducible analysis. UPDATE AUTOMATIC propagates source database changes periodically, suiting always-current internal datasets.

Can MotherDuck shares enforce row-level security?

No, shares operate at database granularity and cannot filter rows per recipient. For per-customer isolation, publish separate databases or use customer-facing analytics patterns with stronger structural isolation.

Why do share recipients still see stale data after an update?

With UPDATE MANUAL, recipients see the old snapshot until the owner runs UPDATE SHARE and each consumer runs REFRESH DATABASE on their attached copy. Both steps are required for the new data to appear.