motherduck-share-data

Create MotherDuck read-only zero-copy data shares with SQL workflows.

53|3|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/motherduckdb/agent-skills --skill motherduck-share-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: motherduck-share-data
Source: https://github.com/motherduckdb/agent-skills/tree/main/plugins/motherduck-skills-claude/skills/motherduck-share-data
Command: npx skills add https://github.com/motherduckdb/agent-skills --skill motherduck-share-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MotherDuck share data safely without copying bytes, so team members or partners can access the same database contents from a read-only, zero-copy clone.

Core Features & Use Cases

  • Create zero-copy data shares with explicit database-granular ownership and controlled access.
  • Choose access, visibility, and update mode (including manual snapshots for reproducible delivery).
  • Operate and consume shares using the owner workflow (CREATE/UPDATE/GRANT) and the consumer workflow (ATTACH/REFRESH/QUERY).
  • Use case: share an analytics database to a partner with hidden visibility and manual updates so they receive a stable snapshot each time you publish.

Quick Start

Use the motherduck-share-data skill to create a read-only zero-copy share from your chosen MotherDuck database with restricted access, hidden visibility, and manual updates for a specific audience.

Frequently Asked Questions about motherduck-share-data

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

FAQPage Schema
How do I share a DuckDB database without copying data?

You can share DuckDB data without copying bytes by creating a MotherDuck zero-copy share. This generates a read-only clone of the source database, allowing recipients to query the contents without duplicating storage.

How does zero-copy data sharing work in MotherDuck?

MotherDuck zero-copy sharing creates a read-only data share from a source database without moving actual bytes. Owners manage distribution using CREATE SHARE and GRANT SQL, while consumers ATTACH and REFRESH the database to query it.

How do I set up manual snapshot updates for a shared MotherDuck database?

To set up manual snapshot updates, configure the share's update mode to manual. You then use UPDATE SHARE SQL to publish stable snapshots at your chosen intervals, ensuring partners receive reproducible data versions upon REFRESH.

Can I restrict visibility and access when sharing MotherDuck data externally?

Yes, you can restrict external distribution by configuring access and visibility modes during share creation. Hidden visibility ensures controlled delivery, while explicit GRANT statements manage database-granular ownership for named recipients.

What is the consumer workflow for querying an attached MotherDuck data share?

Consumers query an attached MotherDuck data share by first using ATTACH to connect to the shared database, then executing REFRESH DATABASE to sync the latest snapshot, and finally running standard read-only SQL queries against it.

When should I use manual updates instead of automatic refreshes for DuckDB data sharing?

Use manual updates for DuckDB data sharing when you need reproducible delivery and stable snapshots. This mode lets you explicitly publish versions, ensuring partners analyze a consistent data state rather than continuously changing live data.