A skill is a saved way of doing one job. You explain it once, and after that it's one step. This is the prompt that gets Claude to build yours properly.
There's a task you've done 20 times this year. Every time, you walk Claude through it from zero: the steps, your voice, the format, what not to do. A skill ends that. The words below make Claude interview you about the task first, one question at a time, then build the skill with you and test it on a real example before you save it.
The interview is the part most people skip, and it's the reason most skills come out generic. Don't rush it. Claude is learning how you do the job, so the skill does it your way every time after.
I want to build a skill: a saved, repeatable way for you to do one job for me the same way every time. The job is [describe the task you repeat every week, in your own words].
Before you build anything, interview me one question at a time until you are 95% confident you can do this job without me re-explaining it. Ask me about: the steps I take now, what a finished result looks like, one past example I was happy with, my voice and formatting rules, what you should never do, and what you will need from me each time this runs.
Then build the skill as one instruction document I can save and reuse. It needs: a short name, one line on when to use it, the exact steps you will follow, the few questions you will ask me at the start of each run (only the things that change each time), and the exact format of the finished output.
Show me the draft. Let me test it on a real example and tell you what to fix. When I say it is right, give me the final version and tell me exactly how to save it in Claude so next time the whole job is one step.
You don't need 50 skills. You need the handful that erase your repeated week. Every one of these gets built with the same prompt above, just a different task in the bracket.