# Claude Skills: The Paid Work Playbook Build a Client-Ready Claude Skills System in 30 Days - Price: $12.99 (Kindle ebook) - Level: Intermediate - Pages: 220 - Best for: Anyone with a folder of skills they cannot say earns its place - You finish with: Twelve tests that settle which skills stay, one that fires unnamed in three fresh sessions, and a handover pack you can attach to an invoice - Series: Claude Code Skills That Pay, book 2 of 2 - Buy on Amazon: https://amzn.to/4xkonel - Web page: https://youcanbuildthings.com/books/claude-skills-paid-work ## What you get You installed the skills and you still type the same prompt every morning. Twelve tests settle which ones earn their place: one that fires in three fresh sessions without being named, one whose output goes straight to a client, and a handover pack you can attach to an invoice. There are 217 Claude Skills books on Amazon and most of them start you at zero. You are not at zero. You installed the folder. You copied someone else's skills. You still cannot say which of them earns its place. This one is about the part nobody writes down: reading a downloaded skill before you run it, pricing what your folder charges on every session, teaching a skill to stay quiet, and packaging the set so it can go out with an invoice. The free companion repo ships the finished skills in a folder you can copy, plus two scripts that measure your own folder with no account and no sign-up. ## Chapters 1. The Folder You Have Been Avoiding Eye Contact With: Build the intake sheet: what each skill claims, when it last fired, whether you have seen it work. 2. A Skill Is Not Just a Prompt, and Here Is the Test That Settles It: Run the same prompt in two fresh sessions, skill off then on, and get a number for whether it helped. 3. The Bill Your Folder Charges Before You Type a Word: Price what your folder loads into every conversation, then rank each skill by cost against how often it fires. 4. Make It Fire in a Fresh Session, Every Time: Write one skill with an explicit trigger and prove it fires three times without you naming it. 5. Output You Would Put Your Name On: Add the sources a skill must use, the shapes it must never produce, and one worked example of a right answer. 6. The Hardest Part Is Teaching It to Stay Quiet: Give a skill an abstain rule, then run the near-miss prompts that must not trigger it. 7. Finding the Ones That Are Real: A five-question screen that rejects a bad skill in ninety seconds. 8. Read It Before You Run It: Read a public skill line by line before installing it, then write your own version that borrows none of the text. 9. Proof the Work Got Done Is the Part People Pay For: Make a skill report what it did NOT do, then sort its output into send-as-is, read-first, or never-leaves-your-desk. 10. Arrange the Shelf So Someone Else Can Use It: Package the folder for a paying client: naming, a manifest, and a one-page description of what fires when. 11. Six Months In, Delete Most of It: A pruning routine that drops anything unfired in thirty days, merges duplicates, and re-measures the bill. 12. Make Them Outlive the Tool You Built Them In: The release-day re-test you run when a new model ships and half your folder stops working. ## Free guides from this book - [Best AI Coding Tools for Claude Skills in 2026: The Buyer's Shortlist](https://youcanbuildthings.com/articles/best-ai-coding-tools-for-claude-skills.md): We checked 9 AI coding tools for where they load SKILL.md files and which fields they keep. See which one fits your Claude Skills. - [Best Claude Skill Security Scanners in 2026: The Buyer's Shortlist](https://youcanbuildthings.com/articles/best-claude-skill-security-scanners.md): We compared 6 ways to scan a Claude Skill and ran Cisco's free scanner on a test-file payload ourselves. Here is what each one catches and misses. - [Best Claude Skills Books in 2026: The Buyer's Shortlist](https://youcanbuildthings.com/articles/best-claude-skills-books.md): We compared 12 Claude Skills books on coverage, depth, price and ratings. See which one fits a beginner, a developer, or someone billing clients. - [Best Claude Skills Marketplaces in 2026: The Buyer's Shortlist](https://youcanbuildthings.com/articles/best-claude-skills-marketplaces.md): We ran the open-standard validator on 973 skills from 6 sources and checked licences, listing cost and upkeep. Here is where to get Claude Skills. - [Best Tools to Test Claude Skills in 2026: The Buyer's Shortlist](https://youcanbuildthings.com/articles/best-tools-to-test-claude-skills.md): We ran or verified 6 tools for testing Claude Skills: format, triggering, with-vs-without and cost. See which one answers your question first. - [How to Make Claude Code Use Your Skills Automatically](https://youcanbuildthings.com/articles/claude-skill-not-triggering.md): Get Claude Code to pick up your skill the moment you ask in plain words, in every new session, without typing its name. One rewritten description line, the 3-session test that proves it, and the 18 runs I did to check it. - [How to Make Claude Skills Write Client-Ready Work](https://youcanbuildthings.com/articles/claude-skill-best-practices.md): Turn a Claude skill that writes generic drafts into one that writes client-ready updates in your format on the first run. Three sections added to SKILL.md, five checks that grade it, and what happened when I ran the before and after today. - [How to Turn Claude Code Output Into Billable Client Work](https://youcanbuildthings.com/articles/claude-code-skips-tasks.md): Put your name on Claude Code work and bill for it, because the skill ends every run by naming what it guessed, what you should check, and where it went off script. One block added to a skill, one deliberate break that tests it, and the three review tiers that decide what goes to the client. - [How to Use Your Claude Skills in Codex and GitHub Copilot](https://youcanbuildthings.com/articles/use-claude-skills-in-codex.md): Run one folder of Claude skills in Claude Code, OpenAI Codex and GitHub Copilot, so every skill you build works in every tool your clients use. Where each tool looks, the one-line link that serves Codex, and the frontmatter that quietly stops working when you move.