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

Helps the operator of an app marketplace design billing, fees, waivers, payouts and the tax split.

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

app-marketplace-monetization-model makes Claude act as a marketplace-monetization designer for the operator side. It covers merchant-of-record posture, billing rails, the fee stack, pricing models for developers, fee waivers, payout cadence and holds, and the marketplace-facilitator and VAT tax layer.

It loads when you mention charging for apps, revenue-share collection, paid-app billing, developer payouts, fee waivers or merchant of record. It is mechanics only: the take-rate level belongs to connector-marketplace-strategy. It asks ten interview questions, drafts in ten steps, and bundles three reference files and no scripts.

Good for

Marketplace teams adding paid apps
Finance and billing leads who must decide who is merchant of record
Product leads publishing a sale-to-bank timeline for developers

Install app-marketplace-monetization-model

Claude Code

Copy this prompt.

Install the app-marketplace-monetization-model 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. app-marketplace-monetization-model is one of them. Pick one route, not both.

From the project README. Source.

What's in the skill

When it loads

Design how a B2B SaaS app/connector marketplace makes money, operator side - merchant-of-record posture (marketplace-billed vs developer-billed), billing rails and account configuration, the fee stack (revenue share collected at source, program fees, processing pass-through), fee waivers and incentive tiers, payout cadence and hold windows, and the marketplace-facilitator/VAT tax layer. Use whenever the user mentions charging for apps, rev-share collection, paid-app billing or billing APIs, developer payouts, fee waivers, or merchant of record - even if they never say "marketplace monetization". Mechanics layer only. Do NOT use for take-rate level and tiers - use samber/developer-platform-skills@connector-marketplace-strategy instead.

Sections in SKILL.md

Interview
Where B2B vs B2C actually matters here
Workflow
2. Merchant-of-record posture
3. Billing rails
4. Fee-stack composition
5. Pricing-model menu for developers
6. Fee waivers and incentives
7. Payout design
8. The tax layer
9. Enforcement and notice
10. 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,737 (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 ten questions, starting with the take-rate architecture from the strategy layer.
Try: “Design our marketplace fee stack and payout schedule: rev-share collection, a small-developer waiver, and a sale-to-bank timeline we can publish to partners.”
Interview
Takes the take rate from the strategy layer as an input.
1. Confirm take-rate architecture
Chooses marketplace-billed or developer-billed.
Changing this later rewrites the tax map and payouts, per SKILL.md.
2. Merchant-of-record posture
Configures billing rails and account dimensions behind that posture.
3. Billing rails
Composes revenue share, program fees and processing pass-through.
4. Fee stack
Sets which pricing models developers get, after checking the rails support them.
5. Pricing-model menu
Designs fee waivers and incentive tiers.
6. Waivers and incentives
Sets payout cadence, holds and thresholds and publishes the sale-to-bank timeline.
7. Payout design
Maps marketplace-facilitator and VAT rules jurisdiction by jurisdiction.
8. Tax layer
Writes enforcement rules and notice commitments.
9. Enforcement and notice

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 app-marketplace-monetization-model?

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 app-marketplace-monetization-model 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 ten 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 app-marketplace-monetization-model 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.

How is it different from connector-marketplace-strategy?

This skill designs the mechanics: billing, collection, waivers, payouts and tax. SKILL.md says not to use it for take-rate level and tiers, which belong to connector-marketplace-strategy.

Does it handle real payments?

No payment tool is named in SKILL.md. It produces a design document for how your marketplace bills, collects and pays out; it does not move money.

Information

updated Nov 2, 2026

Repository: samber/developer-platform-skills
Folder: skills/app-marketplace-monetization-model

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
app-marketplace-monetization-model SKILL.md · github.com