a prompt is not a skill.
every "skills vs prompts" post online ends in the same fence-sitting answer: it depends. that's true and useless. here's the version i actually use to decide, built from running both every day.
what each one is for
a prompt is a one-off instruction. you type it, you get a result, it scrolls away. great when you don't know yet what you want.
a skill is a saved process. a file claude reaches for on its own, the same way every time. great when you already know exactly how you want something done.
the one test that decides it
forget the comparison tables. use this:
if you'd be annoyed re-explaining it, it's a skill.
that's the whole rule. the first time you ask claude to do something, it's a prompt, because you're still figuring out what good looks like. the third time you type roughly the same instructions, you're paying a tax. that's the signal to turn it into a skill.
what i moved, and why
the things i turned into skills were the things i was redoing constantly. my brand voice. how i screen a post before it goes out. how i write a dm that converts. each one was a prompt i retyped with small variations, and the output drifted every time.
as skills, they don't drift. same standard, every session. the things i still do with prompts are the genuinely new problems, the ones where i don't know the answer yet. known and repeated becomes a skill. new and uncertain stays a prompt.
the trap
don't try to skill everything on day one. you can't write a good skill for a process you haven't figured out yet. you'll lock in a mediocre version. explore with prompts until you know what good looks like, then harden the winner into a skill. prompts find the process. skills keep it.
why this is the whole game right now
here's the part most people miss. about 85% of people have access to AI. about 25% use it on real work. that 60-point gap is not a tools problem. it's that a generic prompt you retype never fits your actual job, so you drift back to doing it by hand.
a skill is how you close that gap on yourself. it's the difference between "i have claude" and "claude runs this part of my business the same way every week." i wrote about the gap itself in the ai adoption gap, and about why a skill holds where a prompt slips in how much you can actually steer ai.
the takeaway
prompts are how you figure it out. skills are how you keep it. start everything as a prompt. the moment you'd be annoyed explaining it again, write the file. for what a skill actually looks like inside, see claude skills, explained.
want your prompts turned into a system?
free 2-minute builder: name your business, pick the job, get a framing shift pack + on-page system in your voice. not a course. a file you keep.
build your system free