How do I install the Share Data skill?

Run npx skillmds add majiayu000/share-data in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Share Data safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Share Data?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Share Data free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Share Data?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Share Data by majiayu000 — Agent Skill

Name: Share Data
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Share Data with MotherDuck

Use this skill when you need to distribute a MotherDuck database without copying data. Shares are read-only, zero-copy database clones and should be treated as explicit provisioning operations.

Source Of Truth

Prefer the current MotherDuck sharing docs and SQL reference first.
If the MotherDuck MCP ask_docs_question feature is available, use it before falling back to public docs.
Keep the sharing model aligned with the documented behavior:
- zero-copy and metadata-only
- database-granularity sharing
- read-only recipients
- owner-controlled update mode

Prerequisites

MotherDuck connection established via connect
Source database identified via explore
Share SQL validated via query

Default Posture

Default internal sharing to ACCESS ORGANIZATION, VISIBILITY DISCOVERABLE, and UPDATE AUTOMATIC.
Use UPDATE MANUAL when the recipient needs a stable snapshot or versioned delivery.
Use ACCESS RESTRICTED or VISIBILITY HIDDEN when distribution should stay tightly controlled.
Never treat a share as row-level security. Shares operate at database granularity.

Workflow

Identify the exact database to publish and who should consume it.
Decide sensitivity, discoverability, and freshness requirements before writing SQL.
Create the share with explicit access, visibility, and update settings.
If access is restricted, grant readers explicitly. If the share is hidden or link-based, distribute the share URL directly.
Have recipients ATTACH the shared database and query it read-only.
If the share uses UPDATE MANUAL, the owner runs UPDATE SHARE and consumers run REFRESH DATABASE when a new snapshot is ready.

Open Next

references/SHARE_PLAYBOOK.md for the full SQL playbook, access/update decision matrix, consumer workflow, and common failure modes

Related Skills

connect for MotherDuck authentication and connection setup
explore for discovering databases, tables, columns, and existing shares
query for validating share SQL and downstream queries
duckdb-sql for DuckDB SQL syntax and lookup support

---name: share-datadescription: Create and manage MotherDuck data shares for zero-copy data distribution. Use when sharing databases with team members, other organizations, or making data publicly available.license: MIT--- # Share Data with MotherDuck Use this skill when you need to distribute a MotherDuck database without copying data. Shares are read-only, zero-copy database clones and should be treated as explicit provisioning operations. ## Source Of Truth - Prefer the current MotherDuck sharing docs and SQL reference first. - If the MotherDuck MCP `ask_docs_question` feature is available, use it before falling back to public docs. - Keep the sharing model aligned with the documented behavior: - zero-copy and metadata-only - database-granularity sharing - read-only recipients - owner-controlled update mode ## Prerequisites - MotherDuck connection established via `connect` - Source database identified via `explore` - Share SQL validated via `query` ## Default Posture - Default internal sharing to `ACCESS ORGANIZATION`, `VISIBILITY DISCOVERABLE`, and `UPDATE AUTOMATIC`. - Use `UPDATE MANUAL` when the recipient needs a stable snapshot or versioned delivery. - Use `ACCESS RESTRICTED` or `VISIBILITY HIDDEN` when distribution should stay tightly controlled. - Never treat a share as row-level security. Shares operate at database granularity. ## Workflow 1. Identify the exact database to publish and who should consume it. 2. Decide sensitivity, discoverability, and freshness requirements before writing SQL. 3. Create the share with explicit access, visibility, and update settings. 4. If access is restricted, grant readers explicitly. If the share is hidden or link-based, distribute the share URL directly. 5. Have recipients `ATTACH` the shared database and query it read-only. 6. If the share uses `UPDATE MANUAL`, the owner runs `UPDATE SHARE` and consumers run `REFRESH DATABASE` when a new snapshot is ready. ## Open Next - `references/SHARE_PLAYBOOK.md` for the full SQL playbook, access/update decision matrix, consumer workflow, and common failure modes ## Related Skills - `connect` for MotherDuck authentication and connection setup - `explore` for discovering databases, tables, columns, and existing shares - `query` for validating share SQL and downstream queries - `duckdb-sql` for DuckDB SQL syntax and lookup support

Frequently asked questions