How to Sell Claude Skills to Clients: Package One Repeatable Job, Charge Setup Plus a Monthly Fee
One builder on this site reports selling a podcast-repurposing skill for $2,500 upfront plus $400 a month. Here is how to find a job worth packaging, build and test the skill, hand it over safely and price it.
A 47-minute build that reportedly sold for $2,500 plus $400 a month
A builder named Nav Toor, documented on this site, says he built a Claude Skill in 47 minutes that turns one podcast episode into 15 pieces of content, then sold it to a client for $2,500 upfront plus $400 a month. He reports seven skills in total, priced between $2,000 and $5,000 a month across the portfolio. Those are self-reported social media figures and nobody has verified them. Treat them as a sign of what one person tried, not a price list.
What makes the model interesting is how little there is to deliver. A Claude Skill is a folder with a text file of instructions in it. No server, no hosting, no code if you do not want any. That also makes it easy to underprice, easy to copy and easy to oversell, so this guide covers what to package, how to build and test it, how to hand it over, and what to charge.
What you are actually selling
A skill is a SKILL.md file with a name and a short description at the top, followed by instructions that Claude loads when a task matches. You can add reference files next to it: a style guide, a template, example outputs, even a small script. When the client asks Claude for something that fits the description, Claude reads the instructions and follows them.
According to Anthropic's help center, skills are available on Free, Pro, Max, Ultra, Team and Enterprise plans as of November 2026, and they need code execution switched on. Custom skills you upload are private to that one account, so each client installs their own copy. Team and Enterprise owners can provision a skill for everyone in the organization. Skills also do not sync across Claude.ai, the API and Claude Code, so you upload them separately wherever they will be used.
So you are not selling software. You are selling a tested way of getting one specific job done the way this client wants it, plus someone to fix it when it drifts. If that sounds thin, it is. The jobs that justify a price are the ones where the client currently pays a person every month for the same output.
Pick a job that deserves a price
The best candidates share four traits. The job happens on a schedule (weekly show notes, monthly reports, every inbound contract). The output has a fixed shape. The client already knows what good looks like because a person produces it today. And a mistake is cheap to catch, because someone reads the result before it goes out.
Podcast repurposing fits all four, which is probably why it worked. So do monthly client reporting for an agency, first-pass review of vendor contracts, turning call transcripts into follow-up emails, and drafting a weekly newsletter from a client's raw notes. Jobs that fail the test: anything where the client cannot tell good from bad output, anything one-off, and anything where a wrong answer causes real harm and nobody checks it.
A worked example: a podcast host with four episodes a month
Picture a business podcast that publishes four 40-minute episodes a month. The host pays a freelancer or an in-house assistant to turn each one into a LinkedIn post, a short newsletter blurb, five quote cards, a short-video script and a handful of social posts. Say that is two hours of work per episode, eight hours a month. That is an illustration, not a figure from the case study.
You build a skill that takes a transcript and returns the full set in the host's voice, formatted the way they post. The host pastes a transcript into Claude, gets everything in a couple of minutes, and spends 15 minutes editing instead of two hours producing. You charge a setup fee for the audit, the build and the training call, and a monthly fee for keeping it sharp. The host also pays for their own Claude plan, which is $20 a month on Pro billed monthly or $17 with annual billing, as of November 2026.
Whether the numbers work depends on what the host pays today for that eight hours. If it is a $25-an-hour assistant, the skill saves roughly $200 a month in labor, and a $400 retainer does not pay for itself on labor alone. It has to buy the host something else: more output, faster turnaround, or a content library they would otherwise never get to. Check this arithmetic with every prospect before you quote.
Step by step: build and sell your first skill
Step 1: Audit the job before you write anything
Ask the client to show you the last three outputs and the inputs that produced them. Sit through one real run if you can. Write down every decision the person makes: what gets cut, which tone, which clients are never mentioned, what gets flagged for review. Those decisions are the instructions. Without them you will build a generic skill that the client could have got from a free prompt.
Step 2: Collect good and bad examples
Get five finished outputs the client loved and two they rejected, with a sentence on why. Put the good ones in a folder named examples and the rejected ones in a short file of things to avoid. Claude follows examples more reliably than adjectives.
Step 3: Write the SKILL.md
Create a folder named after the skill in lowercase with hyphens, for example podcast-repurposer. Inside, make SKILL.md. Start with a name and a description that says what the skill does and when to use it, written in one or two plain sentences. Anthropic's documentation and help center quote different description limits, so keep it well under 200 characters. Below that, write the steps in order: what to read, what to produce, in what format, and what to do when the input is missing something. End with a checklist Claude runs on its own output before replying.
Step 4: Add reference files and keep the main file short
Put the voice guide, templates and examples in separate files and tell the main file when to read each one. Claude loads them only when needed, which keeps the skill focused and cheaper to run. If you add a script for something deterministic, such as counting characters or converting a table, test it on its own first.
Step 5: Test on inputs you have not seen
Run the skill on at least five new real inputs, including a messy one and one that is too short. Compare against what the client's person would have produced. Fix the instructions where it fails, not the output by hand. Keep a log of what you changed, because it becomes your retainer report.
Step 6: Package it and install it on their account
Zip the folder so the skill folder is the root of the archive, not loose files. Have the client open Customize, then Skills in Claude, upload the zip and switch it on. Menu names have changed more than once, so follow what their screen shows. Do the install on a call, and run one real job together before you hang up.
Step 7: Write a one-page handover
Say what to paste in, what comes back, what to check before using it, and who to message when it looks wrong. Include the three failure modes you saw in testing. Clients forget everything else, but they keep this page.
Step 8: Price setup and retainer separately
Charge setup for the audit, build and training. Charge the retainer for fixes, new formats, and a short monthly check of recent outputs. If the client will not pay a retainer, sell the setup alone and offer a paid fix hour, which is honest about how little maintenance some skills need.
What this costs you and the client
Your costs are close to zero: a Claude Pro plan at $20 a month billed monthly, or $17 with annual billing, as of November 2026, which is enough to build and test. The Max plan is $100 a month if you are running long jobs all day. The client needs their own paid plan and code execution enabled. Check anthropic.com pricing before quoting, because plan names and prices have moved this year.
Your real cost is time. Budget a day for the audit and build and another for testing and handover on a first skill, less once you have a template. The 47-minute build in the case study almost certainly excludes the audit and the testing.
When not to sell skills
Do not sell a skill when a good saved prompt would do the job. A skill earns its keep when there are reference files, multiple formats or steps the client keeps forgetting. Do not sell one into a job where mistakes are expensive and nobody reviews the output, such as legal filings or medical advice. And do not promise results you cannot control: the model changes, the client's inputs change, and outputs drift. Anthropic does not review skills you upload yourself, so tell clients to read the instructions of any skill they install, including yours. Finally, anything you can build in 47 minutes a client could eventually build too. Your edge is the audit, the testing and being the person who answers.
Frequently Asked Questions
What is a Claude Skill?▾
A Claude Skill is a folder containing a SKILL.md file of instructions, plus optional reference files and scripts, that Claude loads when a task matches its description. It lets you teach Claude one job done one way, without writing code or running a server.
Can I sell Claude Skills to clients?▾
Yes, and at least one builder on this site reports doing so, charging $2,500 upfront plus $400 a month for a podcast-repurposing skill. Those figures are self-reported. You are selling the audit, build, testing and support more than the file itself.
Does the client need a paid Claude plan?▾
Anthropic's help center lists skills on all plans including Free as of November 2026, but they require code execution to be enabled. Most clients doing real work will want Pro at $17 to $20 a month, or a Team plan.
How do I give a Claude Skill to a client?▾
Zip the skill folder so the folder is the archive root, then have the client upload it under Customize, then Skills, and switch it on. Custom skills are private to each account, so every user installs their own copy unless a Team or Enterprise owner provisions it for the organization.
How much should I charge for a Claude Skill?▾
There is no market rate yet. Work backwards from what the client pays a person to do the same job today, and charge setup for the build and a smaller monthly fee for maintenance. The documented example used $2,500 plus $400 a month, but check your client's numbers before copying it.
Are Claude Skills safe to install?▾
Anthropic does not review skills you upload yourself, and a skill's instructions and scripts run inside the conversation. Read every file before enabling any skill, and keep scripts simple enough for the client to understand.