Quick context on me: I'm an AI-native digital marketer with zero coding background, and my entire business runs on these three words. Not because they're trendy. Because they're three of the only things about AI that don't change every time a new model drops.
Everyone throws "skill," "agent," and "workflow" around like they're interchangeable. They're not. Mix them up and you end up re-explaining the same task to Claude from scratch every single time, instead of building something that runs itself once and keeps working.
So here's the plain-English version of each one, when to reach for which, and three copy-paste prompts that build your first skill, your first agent, and your first workflow today.
The short version
Three Words, Three Jobs
Before the analogy, here's the version you can hold in your head:
A skill is a recipe
One task. The exact same steps. Every single time.
An agent is an employee
One lane of responsibility. A handful of related tasks. Judgment about which one applies.
A workflow is the assembly line
Strings a bunch of skills (and agents) together, in a fixed order, to deliver one finished outcome.
A skill is a recipe. An agent is an employee. A workflow is the assembly line that puts both to work.
The full picture
Picture Building a Real Employee
A skill is one page out of the training manual. "Here's exactly how you write a TikTok caption." Nothing more. It doesn't decide anything, it just executes the same steps correctly, every time you point it at that task.
An agent is the person you hired and handed the whole manual to. "You own captions, hooks, and video descriptions. Use whichever page of the manual applies to what I'm asking for." It has judgment inside its lane, and the good ones reach for a skill instead of winging it from memory.
A workflow is the whole department running at once. The agent uses skill A, hands the result to skill B, checks it against a rule, and delivers a finished thing back to you. You don't touch a single one of the individual steps. You say "go," and you check the output.
Here's what that looks like in my own business. I have a content agent whose whole lane is my content: it owns hooks, captions, scripts, all built as separate skills it can reach for. When I want to launch a new free guide, I don't run four separate tasks myself. I tell Claude to run my lead magnet launcher workflow. That one command fires my content agent through six chained skills, in a fixed order, that build a guide page, write the landing copy, add a card to my resources page, publish a live landing page, write the Instagram DM automation, and push all of it live on my site.
That's literally how the guide you're reading right now got made. More on that in a minute.
The decision
When to Use Which One
You don't need a framework for this. Ask yourself one question at a time, in this order:
Is it the same steps, every single time?
Build a skill. If you can write it as a numbered list that never changes, it's a recipe, not a role.
Does it need someone to juggle a few related tasks and decide which one applies?
Build an agent. That's a lane of responsibility, not a single recipe.
Do you need several of these to run back to back, automatically, to deliver one bundled result?
Build a workflow. That's several numbered lists, chained, with an order that never changes.
The honest version
Almost everyone starts in the wrong place: they try to build a workflow before they have any skills to chain together. Build a skill first. Once you have two or three, the agent and the workflow basically build themselves, because you're just organizing work you've already automated.
Build #1
Your First Skill
Works in Claude Code. No coding background needed.
Pick one task you do the same way every time. A recap email. A client invoice. A caption format you always follow. If you had to train a new hire to do it perfectly on day one, that's your skill.
Paste this into Claude Code, fill in the bracket, and answer the questions it asks you back.
Copy-paste prompt — build a skill
I want to build my first Claude skill.
The task I do the same way every time:
[Describe the repeatable task in plain English. Example: "writing
a weekly recap email to my team every Friday" or "formatting a new
client's invoice."]
Set it up as a single skill file:
- Create a folder at .claude/skills/[skill-name]/
- Inside it, write a SKILL.md file with:
- A short description of what the skill does AND when I should
use it, so you know to trigger it automatically next time I
ask for something related
- The exact steps to do the task, in order, written like you're
training a new hire who has never done this before
- Any real examples, templates, or formatting rules I already
use (ask me for these if you don't know them)
Ask me questions about how I actually do this task today before
you write the steps. Don't guess. The more specific the steps,
the better the skill works.
When you're done, tell me the exact phrase I can type to trigger
this skill. That's it. One file, one job. Once you've got a few of these and want to level them up (splitting a big skill into steps, adding reference files, adding scripts it runs instead of re-reading), this guide covers exactly how.
Build #2
Your First Agent
A dedicated AI teammate with its own lane, not a one-off task.
Pick one area of your work that has more than one related task in it. Content. Customer emails. Bookkeeping. If you already built a skill or two from the section above, this is where they go to live.
One rule before you paste this: keep the job description to ONE lane. If you catch yourself writing "and" to connect two unrelated jobs, that's two agents, not one.
Copy-paste prompt — build an agent
I want to build my first Claude Code subagent, a dedicated AI teammate with its own job, not just a one-off task. The role: [Describe the area of responsibility. Example: "everything related to my short-form content" or "answering and tagging customer emails."] Set it up: - Create a file at .claude/agents/[agent-name].md - Give it a "description" field that says exactly what it's responsible for and when I should hand it work. Be specific enough that it's obvious when to use this agent versus just doing the task myself. - Write it a system prompt like an onboarding doc for a new hire in this role: what it owns, how it should make decisions, what "good" looks like, and which tools or skills it's allowed to use. - If I already have skills built for pieces of this job, list them here: [skill names], and tell this agent to use them instead of improvising the task from scratch. - Keep its scope to ONE area of responsibility. If the role is actually two unrelated jobs, tell me and suggest splitting it into two agents instead of one. Ask me clarifying questions about how I want this role to make decisions before you write the file.
Once it's built, you talk to it by name. "Hey, have the content agent write this week's captions." It reaches for the right skill on its own instead of you re-explaining the task from zero.
Build #3
Your First Workflow
One command, several skills, a bundle of finished outputs.
This one only works once you've got at least two skills (or an agent) already built. A workflow doesn't do new work, it just refuses to let you forget the order you already do things in.
Pick something you do in the same multi-step sequence every time it comes up. Launching content. Onboarding a client. Closing out your week. Then paste this in.
Copy-paste prompt — build a workflow
I want to build my first workflow: one command that strings together several skills (and/or agents) in a fixed order to deliver a multi-part outcome. The finished outcome I want, end to end: [Describe the finish line. Example: "every time I publish a new lead magnet, I want the guide page, the landing page, the resources card, and the promo DM script all built and pushed live."] The skills or agents I already have that this should chain together: [List them. Example: "guide-writer skill, landing-page skill, resources-card skill."] Build this as its own skill file, the conductor: - Create .claude/skills/[workflow-name]/SKILL.md - List every output this workflow produces, numbered, in the exact order they should happen - For each output, name which skill or agent handles it - Include a final check step before anything counts as done. Define what "this actually worked" looks like, not just "the file exists" - Write the trigger phrase and the exact inputs you need from me before you can start If any step depends on something only I can decide (a review, a yes-or-no call), mark it as a stop-and-ask step instead of letting the workflow guess.
From here on, you don't run the six steps. You say the trigger phrase once, and the workflow runs every step, in order, and tells you when it's actually done, not just when a file got saved.
The receipts
This Guide Is the Proof
I don't love guides that only talk in theory, so here's the real example instead of a hypothetical one: this exact page. The landing page you found it through. Its new card on my resources page. The Instagram DM that just sent it to you if you commented to get it.
All of that came from one sentence I typed into Claude: "go build this lead magnet, run the lead magnet launcher workflow."
I didn't write the layout code for this page. I didn't manually add myself to the data file that tracks every guide on my site. I typed one line, described what the guide needed to cover, and walked away. I came back to six finished things: this guide page, the landing page copy, the resources card, a live email-gated landing page, the Instagram DM automation spec, and it was already pushed live to my website.
That's the entire point of a workflow. It's not that an agent couldn't already do each of those six things. It's that I never have to remember the six steps, or their order, again.
The Whole Thing at a Glance
1. A skill is a recipe. One task, the same steps, every time.
2. An agent is an employee. One lane, a few related tasks, judgment about which skill applies.
3. A workflow is the assembly line. It chains skills (and agents) together, in a fixed order, into one finished outcome.
4. Build in that order. Skill first, then an agent to hold your skills, then a workflow to chain them. Trying to build a workflow with nothing to chain is where most people get stuck.
5. The three prompts above build all three, today, with zero coding background. That's the entire system this website runs on.
Stop treating every AI task like it's the first time you've ever asked for it. Build the skill once. Give it to an agent. Let a workflow run the whole thing without you.
— Zach
Work with Me
Want me on your problem for an hour?
Book a 1:1 call and we build the fix live — the workflow you want automated, the tool you can’t crack, whatever’s stuck. Direct, hands-on, no pitch waiting at the end.