sql-jdbc-access-design Skill (samber): Customer-Facing SQL Access
Makes Claude design how customers query your product's data with SQL, from the architecture choice to tenant isolation and pricing.
- Installs
- 9.4K
- on skills.sh
- Stars
- 9
- on GitHub
- Files
- 4
- besides SKILL.md
- Updated
- Nov 2026
- last repo commit
sql-jdbc-access-design makes Claude design customer-facing SQL access to a product's data: a JDBC or ODBC endpoint, a warehouse share or a hosted query surface. It picks the architecture by scan frequency and then covers tenant isolation, schema stability, BI connectivity, query governance, credentials and pricing.
It starts when you mention JDBC, ODBC, SQL access for customers, connecting Tableau or Power BI to product data, or pricing a SQL add-on. Claude asks 7 opening questions, then works through 8 steps. SKILL.md says to settle first which problem this is, because data sharing, multi-tenant isolation and customer SQL access are different architectures. The skill bundles no scripts.
Good for
- Product teams whose customers want BI tools on their data
- Data platform engineers planning isolation for an external SQL endpoint
- Leads pricing SQL access as an add-on
Install sql-jdbc-access-design
Claude Code
- 1
Copy this prompt.
Install the sql-jdbc-access-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
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 sql-jdbc-access-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 customer-facing SQL access to a product's data - a JDBC/ODBC endpoint, warehouse share, or hosted query surface. Covers the architecture gate by scan frequency (zero-copy share, replicated copy, per-tenant compute isolation), engine-level tenant isolation with secure views and row-level security, an additive-only schema-stability contract enforced in CI, BI-tool connectivity and driver certification, query governance and cost caps, short-lived credential issuance, and the pricing shape. Use whenever the user mentions JDBC, ODBC, SQL access for customers, connecting Tableau or Power BI to product data, or pricing a SQL add-on - even if they never say "SQL access". Do NOT use for bulk file delivery - use samber/developer-platform-skills@bulk-data-sharing-design instead.
Sections in SKILL.md
- Clarifying questions
- Consumer type and scan frequency
- Workflow
- 1. Confirm the problem and inventory the consumers
- 2. Gate the architecture on scan economics
- 3. Enforce tenant isolation in the engine
- 4. Publish a schema-stability contract
- 5. Design BI connectivity and driver distribution
- 6. Configure query governance and cost caps
- 7. Issue credentials
- 8. Choose the pricing shape
- Failure modes
- Measurement
- Invocation examples
- References
Key facts
- Author
- Samuel Berthe
- License
- MIT
- Version
- 1.0.1
- Installs on skills.sh
- 9,371 (Nov 2, 2026)
- GitHub stars
- 9 (Nov 2, 2026)
- skills.sh audits
- Gen Agent Trust Hub pass; Socket pass; Snyk pass (Nov 2, 2026)
- Last repo commit
- Nov 1, 2026
What it includes
Asks 7 questions in one batch before designing anything.
Try: “Our customers keep asking to plug Tableau into their data in our product - design the SQL access surface, we're on Snowflake.”
Opening questionsSettles which problem this is and lists consumers with their query shapes.
Confirm the problem and inventory the consumersPicks zero-copy share, replicated copy or per-tenant compute by scan frequency.
Gate the architecture on scan economicsUses secure views and row-level security, not filters in application code.
Enforce tenant isolation in the engineTreats tables and columns as an API and serves a curated mart layer.
Publish a schema-stability contractPlans BI-tool support; a Postgres wire-protocol endpoint is cheapest when allowed.
Design BI connectivity and driver distributionSets statement timeouts and concurrency caps before launch.
Configure query governance and cost capsPrefers short-lived tokens, then managed secrets, over static passwords.
Issue credentialsPackages SQL access as a paid tier or add-on, never as a free feature.
Choose the pricing shapeAdvises 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-only | No read-only setting is documented. Decline the memory-file suggestion if you want no files written. |
|---|---|
| Scopes |
|
Questions
How do I install sql-jdbc-access-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 sql-jdbc-access-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 sql-jdbc-access-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.
sql-jdbc-access-design vs bulk-data-sharing-design?
Use this skill for live SQL access. SKILL.md sends bulk file delivery to bulk-data-sharing-design, and that skill sends live SQL endpoints back here.
Where should tenant isolation live?
In the query engine, never in application code. SKILL.md says an app-layer WHERE tenant_id filter fails here, because an external SQL handle leaves no application layer to intercept the query. It uses secure views tied to the caller's identity.
Information
updated Nov 2, 2026
- Repository
- samber/developer-platform-skills
- Folder
skills/sql-jdbc-access-design
Sources
Docs, issue trackers and discussions this page is built from.
Show all 6Hide
- README · github.com
- sql-jdbc-access-design SKILL.md · github.com
- sql-jdbc-access-design folder · github.com
- bulk-data-sharing-design SKILL.md · github.com
- marketplace.json · github.com
- plugin.json · github.com