Installs
12,000 installs. $0 in your account. Your repo's growth chart is somebody else's distribution.
Monetize your Claude Code skills. Shopify for AI skills.
Publish your skill, set a price, get paid. Free to list — we take 15% on sales.
The hockey sticks are real. The payouts aren't.
Three public repos full of free Claude Code skills. Stars went vertical this spring. The creators got the same thing you got — thanks!
@forrestchang/andrej-karpathy-skills
0 → ~110K stars in 3 months. Public repo. No payment surface.
@mattpocock/skills
0 → ~60K stars in 3 months. Free to install. Free to fork.
@agentskills/agentskills
Steady climb to ~17K stars. The demand isn't a spike — it's a trend.
Today, your skill makes other people money.
You wrote it on a Sunday. It got curated, starred, and installed by people you'll never meet. Six months in, the only thing in your inbox is "thanks!" — and you're starting to wonder if the third skill is worth shipping.
Stars
A wall of GitHub stars and "this saved my afternoon" DMs. None of them pay for groceries.
The third one
You open the editor for skill #3 and pause. "Should I bother?" There is currently no clean answer.
From
SKILL.md
to first sale in 2 minutes.
No marketplace approval queue. No SDK to learn. Stripe handles the rest.
-
1
Drop your
SKILL.md.Upload the file you already have. We accept skills and Claude Code plugins. No review committee, no waiting list.
-
2
Set a price.
One-time, monthly, or both. Pick a number; change it whenever you want.
-
3
Get paid.
We handle Stripe Connect, the install token, and payouts. You keep the source file and the customer relationship.
What you get when you list a skill.
A small set of things that the GitHub-and-a-Stripe-Checkout combo doesn't give you.
Two prices on one product
Charge a one-time fee, a monthly subscription, or both on the same skill — visitors pick which way to pay. Change the numbers whenever a Sunday afternoon convinces you the price is wrong. No "pricing tier" config files, no Stripe dashboard archaeology.
Updates ship to subscribers
Push a new version of your
SKILL.md
and existing subscribers get it the next time
Claude Code asks for the install token. No
re-purchase, no manual re-share, no "hey can you
DM me the new file" thread. Your changelog does
the marketing for you.
A page for every skill
Every skill gets a public page at
skillmarket.dev/@you/skill-name, plus a creator profile that lists everything
you ship. The link your X bio is already doing,
except this one converts. Followers get pinged
when you publish the next one.
Per-skill numbers that don't lie
Installs, conversion rate, MRR, and churn — broken out per skill, not bundled into one vanity total. The "should I bother with skill #3?" question stops being a feeling and starts being a row in a table. Toggle 7d, 30d, or 90d to see whether last week was the trend or the noise.
What that adds up to.
You don't have to bet your launch on whether the audience prefers $15 once or $9 a month — ship both, watch which one sticks, raise the price the day you have proof. Pricing becomes a lever, not a one-shot decision you regret in week three.
The work you keep doing for free anyway — the v1.2, the v1.3, the bug fixes after someone files an issue — finally pays you every time you ship it, because subscribers stay subscribers as long as the skill keeps getting better.
You stop being a GitHub repo and start being a creator with a back catalog. The same DM that used to end in "thanks!" now ends in a follow, and the next skill you publish has an audience waiting before line one.
"Should I bother with skill #3?" gets an answer instead of a vibe. You see exactly which skill earns its weekend, which one churns, and which one is quietly compounding — so the next thing you build is the thing the numbers asked for.
From the people already shipping.
Five creators who've been getting "thanks!" emails instead of payouts. They told us why they signed up.
I shipped
/changelog-writeron a Sunday and woke up to 8,000 installs and a folder of "thank you" DMs. By skill #2 I was already drafting the "I'm done with this" tweet. Set a price the day I got my Stripe link, and the first $43 payout did more for skill #3 than every star ever did.
Marta Wójcik
Solo indie dev —
/changelog-writer
(1.2k stars on awesome-claude-skills)
I have a folder literally called
should-i-botherwith four half-finished skills in it. Slapped a price on the one closest to done, told three people on X, and now there's a number next to it on a dashboard. Turns out "should I bother" was just "is anyone paying".
Devon Rhee
Side projects out of FAANG hours
Installs don't pay for dinner. $9/month does.
Aisha Bello
Indie hacker, second SaaS, ships skills as side artifacts
Genuinely — why isn't this just built into the install flow already?
Tomás Aguirre
Maintains skills on claudemarketplaces.com
Last skill I shipped, I burned out at v1.4 because every release was free labor with a star count attached. This time I set the price before I wrote line one of
SKILL.md. Same code, same Sundays — different feeling when the email says "$127 paid out".
Hana Tanaka
Builds skills as part of dev advocacy
And what the dashboard looks like.
Pre-launch, so no real numbers yet — here's the shape you'll see when payouts go live.
Creator dashboard — sample
Illustrative/changelog-writer
$9 / month- Active subs
- 47
- MRR
- $423
- Last payout
- $359.55
→ April 14
Numbers are illustrative. They reflect a small, curated skill — not a unicorn outlier.
How payouts work.
- Stripe Connect for payouts. You onboard once, get paid on Stripe's normal cadence, no balance limits.
-
An install token gates the
SKILL.mddownload, so buyers can't redistribute it freely. You ship the file; we keep it honest. - 15% take rate is the only fee. No listing fee. No monthly cost. Free to list, free to leave.
Make the skill that finally pays the rent.
Two sliders. We do the math at our default conversion rate of 2.4% — that's a starting assumption, not a promise. Move the sliders to vibe-check the number.
Start selling.
Early access when payouts go live, no spam — I'll personally email you when there's news worth your inbox.
Your skills shouldn't be free forever.
The most-installed free skill on GitHub right now should be paying its author's rent. Let's make that normal.
Sign up as a creator