How to Sell AI Skills: Prompts, Claude Skills and Workflows
October 7, 2026
To sell AI skills, package one capability that solves a specific job, ship it with a README, worked examples, a version number and a clear licence, and list it where its buyers already shop: a prompt marketplace for prompts, Gumroad or Lemon Squeezy for downloadable files, n8n's or Make's template libraries for visibility, a Claude Code plugin marketplace for Claude skills, your own site, or Taku Marketplace. Then charge for what can't be copied in a minute: updates, support, private data, or a version that already runs.
That last part matters most. A Claude skill is a folder of text files. A prompt is a paragraph. An n8n workflow is a JSON export. Once one person has it, anyone can have it.
So the real question isn't "can I sell this?" It's "what am I selling on top of the files?"
- Sell the outcome, not the file. Updates, support and a working setup are hard to pass around.
- Package it like software. README, examples, changelog, licence, disclosures.
- Match the store to the format. Prompts, files, workflow templates and Claude plugins each have different homes.
- Pick a pricing model. One-off, subscription for updates, or a bundle with your time. Nobody can promise you sales.
What "AI skills" means, and which ones people pay for
"AI skills" here means three kinds of packaged AI capability:
| Type | What it actually is | What the buyer receives | How easy it is to pass on |
|---|---|---|---|
| Claude Agent Skill | A folder with a SKILL.md file plus optional scripts and reference files | The folder, installed in Claude Code, claude.ai or the API | Very easy: zip and send |
| Prompt or prompt pack | Text instructions, sometimes with variables and examples | Text | Trivial: copy and paste |
| Automation workflow | An n8n or Make scenario that chains apps and AI steps | An importable template, plus the accounts it needs | Easy to share, harder to set up |
Anthropic's Agent Skills documentation describes a skill as a directory: a SKILL.md with a name and description in its frontmatter, instructions in the body, and optional scripts and resources Claude loads only when needed. Claude skills explained walks through building one, and AI app vs prompt vs skill covers where each format fits.
Why the files alone are a weak product
First, there's a lot of free supply. Anthropic publishes open-source skills in its own skills repository, and community libraries of prompts and workflows are huge. Your paid skill competes with free ones.
Second, buyers should read every file before running it. Anthropic's docs tell people to use skills only from trusted sources and to audit everything bundled with one, because a skill can run code and call tools. A buyer who reads your whole skill has, in effect, got the whole product.
What people actually pay for
- Maintenance. Models, APIs and app integrations change. A skill that gets fixed every month is worth more than one that worked once.
- Data and domain knowledge. A tax-research skill backed by a curated reference set carries knowledge a copycat doesn't have.
- Support. "It didn't work on my machine" is the message every creator gets. Answering it is a service.
- A running app. Something buyers can use without installing anything is a different product from a folder they have to set up.
- Your time. Setup calls, customisation and training sit naturally next to a skill and can't be copied.
If your plan relies on the file staying secret, rethink it. If it relies on the file staying current, you have a product.
How to package an AI skill so people can buy it
Treat it the way you'd treat a small piece of software.
| File or element | What to put in it |
|---|---|
| README | The job it does, who it's for, what it needs (model, plan, apps, API keys), install steps and known limits |
| Examples | Two or three real inputs with real outputs: screenshots for workflows, sample conversations for prompts and skills |
| Changelog | Dated entries for each release, so buyers can see the product is alive |
| Licence | What a buyer may do: personal use, client work, modification, resale |
| Disclosure | Which data leaves the machine, which third-party services it calls, and any running costs |
A good test: could someone who has never seen your posts install it and get a useful result on the first try? If not, the README isn't done.
Version every release with Semantic Versioning: patch for fixes, minor for new features, major when something breaks. For Claude Code plugins this is mechanical, not just polite. Claude Code's publishing docs note that if you set a version and push new commits without changing it, users keep their old copy.
And write the description for the buyer's job. "Advanced marketing AI skill" sells nothing. "Turns a product changelog into a week of LinkedIn posts in your brand voice" does. The same habit helps Claude, since the description in SKILL.md is what it matches requests against.
Where to sell AI skills
There's no single store for every format. Here's how the main options compare, checked against each platform's own pages.
| Where | Best for | How you get paid | Things to know |
|---|---|---|---|
| PromptBase | Single prompts and prompt packs | Marketplace sale, minus a commission | Listings are reviewed before going live |
| Gumroad | Any downloadable file | Per-sale fee, no monthly fee | Acts as merchant of record for sales tax |
| Lemon Squeezy | Files, software, subscriptions | Per-transaction fee, no monthly fee | License keys and recurring billing built in |
| n8n template library | n8n workflows | Affiliate programme, not template sales | Reviewed submissions; good for visibility |
| Make templates | Make scenarios | No paid option in Make's docs | Public library listing needs Make's approval |
| Claude Code plugin marketplace | Claude skills bundled as plugins | No built-in checkout | Access follows who can clone the repo |
| Your own site | Anything, plus services | Whatever checkout you set up | You handle traffic, delivery and support |
| Taku Marketplace | AI apps people run in a desktop workspace | Set out in Taku's publisher terms | Free and paid listings; early marketplace |
Sell AI prompts on PromptBase
PromptBase is a marketplace built to buy and sell prompts for models like ChatGPT and Midjourney. Its site says prompts are reviewed before they're listed, that it takes a commission on marketplace sales, and that there's no platform fee when you bring the buyer through your own link. It suits prompts with a clear, specific output.
Sell skill files on Gumroad or Lemon Squeezy
For a zip of a Claude skill, a prompt pack or a workflow bundle, a digital-file storefront is the simplest route.
Gumroad charges no monthly fee and takes a cut of each sale, with a higher cut when the buyer finds you through its Discover marketplace. It now acts as merchant of record and handles sales tax.
Lemon Squeezy also charges per transaction with no monthly fee for its store, acts as merchant of record, and can issue license keys automatically and bill weekly, monthly or yearly. That makes it the better fit for selling updates as a subscription.
Sell AI workflows through n8n and Make
Both automation platforms have public template libraries, but neither is a checkout.
The n8n workflow library accepts templates through n8n's creator programme, and n8n's pitch to creators is to "get featured, and earn via our affiliates program". A free n8n template works best as a shop window for your paid version or setup service.
On Make, templates are available on all plans, and any team template can be submitted to Make for review to join the public library. The docs present templates as a sharing tool, with no paid option. Use it for reach and sell the done-for-you setup elsewhere.
Sell Claude skills through a Claude Code plugin marketplace
If your buyers live in Claude Code, bundle your skills into a plugin. A plugin marketplace is a git repository with a .claude-plugin/marketplace.json file listing your plugins.
There's no payment layer inside it. Claude Code's hosting guide explains that access relies on the user's own git credentials, so a private repository means a private marketplace. A common pattern: take payment on your site or a storefront, then grant the buyer read access to the repo. Auto-update is off by default, so tell buyers how to update.
Anthropic also runs a directory on claude.ai. Submitting needs a paid claude.ai plan and listings are reviewed. It's distribution, not a paid store.
Sell from your own site
Your own site gives you the most control and the most work. It's the natural home for bundles, like a skill plus a setup call. Pair it with a storefront for checkout and the free libraries for discovery.
Publish to Taku Marketplace
Taku is an AI-native desktop workspace where people mirror an AI app or workflow someone already got working, run it, edit it and save it as their own. The marketplace carries free and paid apps, and creators have public profiles. If you build in Codex, Claude Code or Cursor, you can publish your work to Taku with the Taku Publisher plugin. Buyers get something to run, not a folder to set up, which is the "running app" value described above.
The marketplace is early. How creator rewards work is set out in Taku's publisher terms, and those terms don't promise sales or cash payouts. They also require you to choose the licence buyers receive for each release and to disclose any data your listing sends out, the external services it uses and any recurring costs.
How to price AI skills
Prices vary wildly across these stores, and anyone quoting a typical income is guessing. Choose a pricing model first, then test numbers with real buyers.
| Model | How it works | Fits best when | Watch out for |
|---|---|---|---|
| One-off purchase | Buyer pays once for the current version | Simple prompts, small skills, stable workflows | Every future fix is unpaid work |
| Subscription for updates | Buyer pays on a schedule for fixes, new versions and support | Skills tied to fast-changing models or APIs | You must ship updates, or people cancel |
| Bundle with a service | The skill comes with setup, customisation or training | Business buyers, complex workflows | Your time doesn't scale |
| Free version plus paid | The free one builds trust; the paid one adds data, support or features | Building an audience on n8n, Make or GitHub | The free version has to be genuinely useful |
Price against the job, not the word count: a workflow that saves a recruiter an hour a day is worth more than a long prompt that saves nothing. And don't promise outcomes you can't control. "Drafts your weekly report" is fine; "doubles your revenue" invites refund requests.
For business models beyond selling files, see how to monetize AI agents.
Licensing and protecting your work honestly
You can't make a text file uncopyable. You can be clear about the rules, make the paid version worth paying for, and make buying easy.
Your licence should answer four questions: can buyers use it for client work, modify it, share it inside their team, or resell it? Choose a License is a good primer on common open-source licences. For a paid product, a short custom licence in plain English often works better. Also check what you're allowed to sell: bundled open-source code brings its licence terms with it.
What protection realistically looks like:
- License keys on Lemon Squeezy or Gumroad identify paying customers and gate updates. They don't stop file sharing.
- Private repositories for Claude Code plugins limit who gets updates. Anyone with access can still copy the current version.
- Keeping logic server-side is the only strong protection. The buyer gets the result, not the recipe, but you take on hosting and privacy duties.
- Platform terms set the baseline. On Taku, the publisher terms say you keep your rights in your content. If you choose Taku's Default Community License for a release (it only applies when you explicitly select it), the Marketplace Terms let users remix your work and commercially use what they build from it, but not resell your substantially unmodified content as a standalone competing asset.
Expect some copying. Creators who do well compete on freshness, support and trust.
Start selling your AI skills
- Define the outcome in the buyer's words.
- Find what can't be copied: updates, data, support or a running app.
- Package it: README, examples, changelog, licence, disclosures.
- List it where its buyers shop, and pick a pricing model you can sustain.
If you've built a skill or workflow that works on your machine but stalls when other people try to set it up, Taku lets them mirror it into a desktop workspace and run it, and you can publish there from Codex, Claude Code or Cursor with the Taku Publisher plugin. Taku is in Beta, and the Mac app is available now.
FAQ
Can you sell Claude skills?
Yes. Sell the skill folder as a download on Gumroad or Lemon Squeezy, or bundle it into a Claude Code plugin and sell access to a private plugin marketplace repository. Buyers can share files once they have them, so most sellers charge for updates and support.
Where can I sell AI prompts?
PromptBase is the best-known marketplace for prompts. You can also sell prompt packs as downloads on Gumroad or Lemon Squeezy, or from your own site. Packs with examples, variations and updates hold value better than single prompts.
Can I sell n8n or Make workflows?
Not as paid listings in their template libraries. n8n offers featuring and an affiliate programme, and Make presents templates as a sharing tool. Most creators publish a free version there and sell the full workflow, setup or support elsewhere.
How much should I charge for an AI skill?
There's no reliable benchmark, and no store can promise sales. Start from the value of the job, choose a model (one-off, subscription for updates, or a bundle with a service), and test with real buyers.
How do I stop people sharing my paid skill?
You can't fully stop it. License keys and private repositories limit who gets updates, and keeping core logic on a server you control is the strongest protection. Regular updates and good support give honest buyers a reason to pay.
Can I publish AI apps to Taku?
Yes. Creators can publish from Codex, Claude Code or Cursor with the Taku Publisher plugin, and the marketplace carries free and paid apps. How creator rewards work is set out in Taku's publisher terms, which don't promise sales or cash payouts.