a prompt is not a skill.

elisabeth hitz · june 18, 2026 · 5 min read

most people use the words "prompt" and "skill" as if they are the same thing. they are not, and the gap between them is the whole reason AI goes from answering your questions to actually running a piece of your work. if you only take one distinction from anything i write, take this one.

what a prompt is

a prompt is a single instruction you type in the moment. "write me a recap of this meeting in three bullets." it is powerful, and it is disposable. you type it, you get one result, and tomorrow you type it again. the quality depends on how well you phrased it that day. it lives in your head and your clipboard, and every time you start a fresh chat, you start from zero. a prompt is a thing you do.

what a skill is

a skill is a folder the AI loads on its own whenever a task matches it. you do not paste it in. you do not invoke it by name. claude notices the task fits a skill you have and pulls it automatically.

inside that folder is more than a long instruction. a skill can hold up to four things, and you include only what the work needs:

• instructions (the SKILL.md file): what the skill does, when to use it, and how, written like a runbook for a new colleague. this is the only required part.
• references: examples of good output, a style guide, past work that sets the bar. this is how it learns what "good" looks like for you.
• assets: the real materials, your template, your brand kit, the logo, so the output looks like yours.
• scripts: small pieces of code for the parts that should run the exact same way every time, a calculation, a formatter, a structured comparison.

some skills are just a SKILL.md and nothing else, and that is perfectly fine. the point is that a skill is a thing you own, not a thing you retype.

the difference, in one picture

think about onboarding someone. a prompt is telling a new hire what to do out loud, every single morning. a skill is writing the standard operating procedure once and handing it to them. the prompt is the reminder you give forever. the skill is the document that makes the reminder unnecessary. one depends on you being there to say it; the other does not.

why the difference compounds

here is the part that matters for your business. a prompt is flat: it is only ever as good as the one you typed. a skill compounds. every time you learn something about what works, you put it back into the skill, and every future run inherits it. the system gets better while you do less.

a skill is also steady where a prompt drifts. retyping an instruction every conversation means it slips a little each time, and the AI slides back toward its defaults. a skill pins the rules in a fixed, prominent place, so the quality holds across every run. i wrote about that drift in how much you can actually steer ai, a skill is steering that does not slide.

when to use each

this is not prompts versus skills forever. you want both. reach for a prompt when you are thinking out loud, exploring, or doing something once. reach for a skill when it is a task you redo, when you want the same quality every time, or when you want to hand the work to a teammate and have it come out right without you in the room.

how you actually make one

you do not write code. you talk to claude. tell it you want a skill for the thing you are tired of re-explaining, and it interviews you: what should this do, when should it trigger, what does good output look like, what examples should it learn from. you answer, you hand it real templates and real past work, and it writes the folder. then it shows up in your skills list and fires automatically whenever the task comes up. for the deeper version, what a skill file looks like and why owning your files beats renting another subscription, see claude skills, explained.

the one-line version: a prompt is something you type. a skill is something you own. that is the difference between using AI and building with it.