Claude Skills: The Paid Work Playbook
Build a Client-Ready Claude Skills System in 30 Days
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.
What You'll Build
Build the intake sheet: what each skill claims, when it last fired, whether you have seen it work.
Run the same prompt in two fresh sessions, skill off then on, and get a number for whether it helped.
Price what your folder loads into every conversation, then rank each skill by cost against how often it fires.
Write one skill with an explicit trigger and prove it fires three times without you naming it.
Add the sources a skill must use, the shapes it must never produce, and one worked example of a right answer.
Give a skill an abstain rule, then run the near-miss prompts that must not trigger it.
A five-question screen that rejects a bad skill in ninety seconds.
Read a public skill line by line before installing it, then write your own version that borrows none of the text.
Make a skill report what it did NOT do, then sort its output into send-as-is, read-first, or never-leaves-your-desk.
Package the folder for a paying client: naming, a manifest, and a one-page description of what fires when.
A pruning routine that drops anything unfired in thirty days, merges duplicates, and re-measures the bill.
The release-day re-test you run when a new model ships and half your folder stops working.