Connector Marketplace Skill: What It Does and How to Install It

Helps a SaaS team decide whether to build an app marketplace, join others' or buy embedded iPaaS, and design its operating model.

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

connector-marketplace-strategy makes Claude act as a platform-strategy advisor. It starts from the gate (build, join or buy), noting that most companies should not build one, or not yet, and if the answer is build it designs curation level, partner mix, governance, take-rate and a seeding sequence in a written decision document.

It loads when you mention building an app store or integration marketplace, ecosystem readiness, revenue share, curated versus open admission or seeding a two-sided ecosystem. It asks nine interview questions and wants your explicit approval on the full document. It is strategy only and bundles three reference files and no scripts.

Good for

SaaS leaders losing deals over missing integrations
Platform teams with a partner directory deciding on a real marketplace
Product leads choosing between build, join or buy

Install connector-marketplace-strategy

Claude Code

Copy this prompt.

Install the connector-marketplace-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.

The README installs every skill in the repo (61 skills/*/SKILL.md in the git tree), because skills here reference each other. connector-marketplace-strategy is one of them. Pick one route, not both.

From the project README. Source.

What's in the skill

When it loads

Decide whether and when a SaaS should build its own app/connector marketplace, versus joining others' marketplaces or buying embedded iPaaS, and design its operating model - curation level, partner mix, governance rules, take-rate, and seeding sequence. Use whenever the user mentions building an app store or integration marketplace, ecosystem readiness, marketplace revenue share or take-rate, curated vs open admission, third-party app governance, or seeding a two-sided developer ecosystem - even if they never say "marketplace strategy". Strategy layer only. Do NOT use for billing and payout mechanics (samber/developer-platform-skills@app-marketplace-monetization-model) or for being a connector on others' data platforms (samber/developer-platform-skills@etl-connector-strategy).

Sections in SKILL.md

Interview
Workflow
1. Gate: build, join, or buy
2. Brainstorm the operating model
3. Governance
4. Quality bar: the curation spectrum
5. Economics: take-rate architecture
6. Seeding sequence
7. Flywheel measurement
Failure modes
Invocation examples
References

Key facts

Author: Samuel Berthe
Repo: samber/developer-platform-skills, which holds 61 skills
License: MIT (LICENSE, README, plugin.json and SKILL.md all say MIT)
Version in SKILL.md: 1.0.2
Installs on skills.sh: 9,664 (Nov 2, 2026)
GitHub stars (repo): 9 (Nov 2, 2026)
Last commit (repo): Nov 1, 2026
What installs: 5 files including SKILL.md: 3 reference files and evals/evals.json; no scripts
Needs: The other skills in the repo; the README says to install all of them
Works in: Claude.ai, Claude Code, Codex, Cursor, Gemini CLI, and tools that read skills.sh installs

What it includes

Asks nine questions on ecosystem state, demand evidence, staffing and purpose.
Includes whether you can staff the full partner lifecycle as a standing commitment.
Try: “We keep losing enterprise deals over missing integrations - should we build an app marketplace or just list on the big platforms?”
Interview
Decides whether to build at all.
1. Gate: build, join or buy
Proposes two or three candidates with trade-offs and a recommendation.
2. Brainstorm the operating model
Writes the governance rules.
3. Governance
Sets the curation position on a spectrum.
4. Quality bar
Designs the take-rate architecture.
5. Economics
Sequences how the ecosystem gets its first partners.
6. Seeding sequence
Defines how the marketplace flywheel is measured.
7. Flywheel measurement

From the official docs

Permissions

Low risk

This skill writes design advice and bundles no scripts, so the main thing to watch is where your agent saves notes.

What it can do

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

Watch out for

It may save notes to developer-platform-context.md
SKILL.md says that when your agent keeps memory in a file, it should consider using this file name. Our advice: keep it out of commits if it holds company plans. github.com

Technical details

Scopes	Asks you interview questions and writes a design document from your answers

Questions

How do I install connector-marketplace-strategy?

Use the install box at the top of this page. The README says to install every skill in samber/developer-platform-skills, not one, because the skills hand work to each other. Pick one route per agent.

Does connector-marketplace-strategy work in Claude, Codex and Cursor?

The README documents install routes for Claude.ai (plugin marketplace), Claude Code, Codex, Cursor, Gemini CLI and the skills.sh CLI. The install box lists each one.

What does it ask me before it designs anything?

SKILL.md lists nine questions to ask first, and the answers change the later steps. Have your current setup and constraints ready.

Does it run scripts or need an API key?

It bundles no scripts. The folder holds SKILL.md, reference Markdown files and an evals file, and the skill works by asking you questions and writing advice.

Is connector-marketplace-strategy safe to install?

It bundles no scripts, so installing it adds instructions and reference files rather than programs. SKILL.md also suggests that, if your agent keeps notes in a file, it uses developer-platform-context.md. Our advice: keep that file out of public commits if it holds company plans, and check any figures the skill cites against their sources before quoting them to customers.

Where do billing and payouts go?

Not here. SKILL.md says this is strategy only: billing and payout mechanics belong to app-marketplace-monetization-model, and being a connector on others' data platforms belongs to etl-connector-strategy.

Information

updated Nov 2, 2026

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

samber/developer-platform-skills skills.sh

Sources

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

Show all 2

samber/developer-platform-skills README · github.com
connector-marketplace-strategy SKILL.md · github.com