PlugWiki

bulk-data-sharing-design Skill (samber): Bulk Data and Lake Export

Makes Claude design how customers get your data in bulk, as Parquet files on object storage or as a native warehouse share.

Installs
9.3K
on skills.sh
Stars
9
on GitHub
Files
4
besides SKILL.md
Updated
Nov 2026
last repo commit

bulk-data-sharing-design makes Claude design bulk file and lake export as a product surface. It chooses between Parquet file drops and native warehouse or lake sharing, then covers partitioning, delivery cadence, credentials, cost allocation, schema evolution, compliance and rollout.

It starts when you mention bulk export, data dumps to S3, Parquet, Snowflake shares, Delta Sharing or export freshness SLAs. Claude asks 7 opening questions, then works through 8 steps. The skill bundles no scripts.

Good for

  • SaaS teams asked to deliver customer data into Snowflake or Databricks
  • Data engineers defining Parquet layout and schema-evolution rules
  • Teams pricing a data-export add-on and settling who pays egress

Install bulk-data-sharing-design

Claude Code

  1. 1

    Copy this prompt.

    Install the bulk-data-sharing-design skill in Claude Code. Run this command:
    
    /plugin marketplace add samber/developer-platform-skills
    /plugin install developer-platform-skills@developer-platform-skills
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Pick one route, not both, or you get every skill twice. The README asks you to install the whole set, not just bulk-data-sharing-design, because the skills reference each other and a lone skill leaves those hand-offs with nowhere to go. The plugin adds all 61 skills in the repo (counted from the repo tree). Its manifests list no hooks, agents or MCP servers.

From the project README. Source.

What's in the skill

When it loads

Design bulk file and lake export as a B2B product surface - the two-camp choice between Parquet file-drops on object storage and native warehouse/lake sharing (Snowflake shares, Delta Sharing, linked datasets), the partitioning and schema-evolution contract across batches, delivery cadence and freshness commitments (full dump vs incremental vs CDC vs streaming), shared-bucket security with per-recipient credentials, egress cost allocation, and cross-border data residency. Use whenever the user mentions bulk export, data dumps to S3, Parquet, Snowflake shares, Delta Sharing, or export freshness SLAs - even if they never say "bulk data sharing". Do NOT use for live SQL endpoints - use samber/developer-platform-skills@sql-jdbc-access-design instead.

Sections in SKILL.md

  1. Clarifying questions
  2. Data-stack maturity
  3. Workflow
  4. 1. Choose the camp
  5. 2. Specify the file-layout and partitioning contract
  6. 3. Set the delivery cadence and the freshness posture
  7. 4. Design the security and credential model
  8. 5. Allocate egress, storage, and compute cost
  9. 6. Write the schema-evolution contract
  10. 7. Settle compliance and residency
  11. 8. Stage the rollout
  12. Failure modes
  13. Measurement
  14. Invocation examples
  15. References

Key facts

License
MIT
Version
1.0.1
Installs on skills.sh
9,342 (Nov 2, 2026)
GitHub stars
9 (Nov 2, 2026)
Last repo commit
Nov 1, 2026

What it includes

  • Asks 7 questions in one batch before designing anything.

    Try: “Our enterprise customers keep asking to get their data into Snowflake - design a bulk export surface, and tell me whether to build file drops or a native share.”

    Opening questions

  • Chooses between Parquet file drops and native warehouse or lake sharing.

    Choose the camp

  • Specifies Hive-style partition paths and the layout customers will depend on.

    Specify file layout and partitioning

  • Sets how often data lands and what freshness you promise.

    Set delivery cadence and freshness

  • Vends short-lived signed URLs or scoped credentials per recipient, never shared keys.

    Design the security and credential model

  • Names who pays each cost layer in writing before launch.

    Allocate egress, storage and compute cost

  • Adds columns only; a rename becomes add-new-plus-deprecate-old.

    Write the schema-evolution contract

  • Handles cross-border transfer, preferring an architecture fix over paperwork.

    Settle compliance and residency

  • Starts with a native share for the dominant warehouse platform when one exists.

    Stage the rollout

  • Advises saving decisions to developer-platform-context.md when memory is a file.

    Write · Remember decisions (optional)

From the official docs

Permissions

Low risk

This skill is written advice that bundles no scripts. The one thing it may write is a decisions file, so check what Claude saves.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It may save decisions to a file

    SKILL.md advises using developer-platform-context.md when memory lives in a file, and calls it an advisory reference. Check or delete that file if you do not want decisions kept. github.com

  • The plugin route adds all 61 skills

    The README asks you to install every skill in the repo, and the repo has 61. The plugin manifests list no hooks, agents or MCP servers, and the repo tree holds none. github.com

  • Folder holds Markdown and one JSON file

    This skill's folder has 5 files: SKILL.md, evals/evals.json and 3 reference files. It has no .py, .sh or .js file. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlyNo read-only setting is documented. Decline the memory-file suggestion if you want no files written.
Scopes
  • Asks you opening questions and works from your answers and anything you share, such as specs or docs

  • May save settled decisions to a file named developer-platform-context.md if your memory lives in a file

Questions

How do I install bulk-data-sharing-design?

Use the install box above. The README asks you to install all 61 skills in the repo, not just this one, because the skills point to each other. In Claude Code that is the plugin route, and elsewhere the skills CLI or the client's own route installs the set.

Does bulk-data-sharing-design work in Claude.ai, Codex or Cursor?

The README documents installs for Claude.ai, Claude Code, Codex, Cursor and Gemini CLI. It also lists the skills CLI, which it calls universal for Agent Skills-compatible tools. The Claude.ai route adds the whole repo as a plugin marketplace.

Does it need an API key or any setup?

SKILL.md sets no environment variable and the folder bundles no scripts. It does ask for details of your own API or product in its opening questions.

Is bulk-data-sharing-design safe to use?

The folder holds Markdown and one JSON file, and no scripts. SKILL.md does suggest saving settled decisions to developer-platform-context.md when your memory lives in a file, so check what Claude writes. Our advice: treat the design it produces as a draft for your team to review before you publish it.

bulk-data-sharing-design vs sql-jdbc-access-design?

Use this skill for bulk files and lake export. SKILL.md sends live SQL endpoints to sql-jdbc-access-design.

Should we ship Parquet files or a warehouse share?

SKILL.md calls these two architectural camps and decides by your customers' warehouse landscape: how many already run Snowflake, Databricks or BigQuery, and whether one dominates. If one does, its rollout plan starts with a native share for that platform.

Information

updated Nov 2, 2026

Folder
skills/bulk-data-sharing-design

samber/developer-platform-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6
  1. README · github.com
  2. bulk-data-sharing-design SKILL.md · github.com
  3. bulk-data-sharing-design folder · github.com
  4. sql-jdbc-access-design SKILL.md · github.com
  5. marketplace.json · github.com
  6. plugin.json · github.com

Updated Nov 2, 2026.