etl-connector-strategy Skill (samber): Source Connectors on ETL Platforms

Makes Claude plan whether and how your SaaS builds a source connector on third-party ETL and ELT platforms.

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

etl-connector-strategy makes Claude plan a SaaS vendor's presence as a source connector on ETL and ELT platforms. It checks demand first, then platform choice, build path, API readiness, honest CDC wording, certification and the maintenance budget.

It starts when you mention an ETL or ELT catalog listing, a source connector, data-pipeline integration or adding CDC. Claude asks 7 interview questions, one per message, then works through 7 steps and writes a connector strategy document section by section, checking each with you. The final document waits for your explicit approval. The skill bundles no scripts.

Good for

SaaS vendors asked by customers to appear in their ETL catalog
Product managers whose data-sync page promises CDC
Teams writing the business case for a connector investment

Install etl-connector-strategy

Claude Code

Copy this prompt.

Install the etl-connector-strategy 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 etl-connector-strategy, 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

Plan a SaaS vendor's presence as a source connector on third-party ETL/ELT platforms - demand validation before any build, platform selection from where customers' data stacks run, a build-path menu (platform-managed listing, vendor-maintained SDK connector, custom open-source tap) ranked by who absorbs the maintenance tax, an extraction-readiness audit of the product API, honest CDC scoping (API sources ship pseudo-CDC, never log-based), certification targets, and a funded maintenance plan. Use whenever the user mentions an ETL or ELT catalog listing, a source connector, data-pipeline integration, or adding CDC - even if they never say "connector strategy". Do NOT use for the vendor's own inbound marketplace - use samber/developer-platform-skills@connector-marketplace-strategy instead.

Sections in SKILL.md

Interview
Customer data-stack maturity
Workflow
1. Demand-validation gate
2. Platform selection
3. Build-path choice
4. Extraction-API readiness audit
5. CDC honesty scoping
6. Certification path
7. Maintenance plan
Deliverable and validation
Failure modes
Measurement
Invocation examples
References

Key facts

Author: Samuel Berthe
License: MIT
Version: 1.0.1
Installs on skills.sh: 9,545 (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 installs: 5 files including SKILL.md: evals/evals.json and 3 reference files. It bundles no scripts.
Needs: The other skills in the repo; the README says to install the whole set
Works in: Claude Code, Claude.ai, Codex, Cursor, Gemini CLI, and other agents through the skills CLI

What it includes

Asks 7 interview questions, one per message, before proposing anything.
Try: “Customers keep asking when we'll be in their ETL platform's catalog - do we build the connector ourselves on the SDK or go through the platform's request program?”
Opening questions
Approves no connector build without named evidence of customer demand.
Demand-validation gate
Targets one ETL platform archetype first and a second only after measuring upkeep.
Platform selection
Compares custom, vendor-SDK and platform-managed paths by who carries the maintenance.
Build-path choice
Audits your API for incremental sync before any build, with fixes sequenced first.
Extraction-API readiness audit
Words what an API-only source can honestly offer instead of promising log-based CDC.
CDC honesty scoping
Separates getting listed from getting certified, with each program's clocks.
Certification path
Budgets yearly upkeep at 15 to 30% of build cost per connector, from vendor estimates.
Maintenance plan
Writes the strategy document section by section and gates the final one on your approval.
Deliverable and validation
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-only	No 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 etl-connector-strategy?

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 etl-connector-strategy 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 etl-connector-strategy 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.

etl-connector-strategy vs connector-marketplace-strategy?

This skill is for a vendor appearing as a source on other companies' ETL platforms. SKILL.md sends the vendor's own inbound connector marketplace to connector-marketplace-strategy.

Can we promise CDC support?

SKILL.md says never promise it as if it were log-based CDC. That kind of CDC reads the internal transaction log of the database being extracted, and no external platform or public API gets that. The skill instead scopes what a SaaS source can honestly ship.

Information

updated Nov 2, 2026

Repository: samber/developer-platform-skills
Folder: skills/etl-connector-strategy

samber/developer-platform-skills skills.sh

Sources

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

Show all 6

README · github.com
etl-connector-strategy SKILL.md · github.com
etl-connector-strategy folder · github.com
connector-marketplace-strategy SKILL.md · github.com
marketplace.json · github.com
plugin.json · github.com