You had a task you wanted handled. You went looking for how to do it, and came back with three words: skill, workflow, agent. Nobody told you which one you needed. So you picked the one that sounded most impressive and spent a weekend building it.
That is the expensive mistake in this whole section of the course. The fancy option is the slowest and the priciest. Building the chef when you needed a recipe card burns a weekend, costs more every time it runs, and gives you a worse result than the simple version would have.
By the end of this you will name any task out loud, ask one question, and know which of the three it is. Then you will build the smallest version that fits, which is usually a lot smaller than you expected.
Here is what you will be able to do:
Say out loud whether a task needs a skill, a workflow, or an agent.
Use one question to pick, in under a minute.
Build the smallest version of the three, instead of the fanciest.
Spot when you are about to over-build, and stop yourself.
Combine all three later, once the task really needs it.
This is for beginners. There is no jargon to memorize here. There is a kitchen, and three things in it.
The proof behind this
Liz Elliott is not an engineer and never studied computer science. She runs 33 active social brands and built four software products with AI help: PRISM, AutoViral, UPRISE Social Studio, and Profounder.
The thing worth copying is not the size of that. It is the shape. Almost none of it is clever agents. It is small saved skills and fixed step lists doing the same boring job the same way every day, which is exactly what this lesson teaches you to spot.
What this lesson is
Lesson 8.1 of the free AI for Entrepreneurs course, in Module 8: Building Skills.
Three words get thrown around a lot: skill, workflow, agent. You do not need to memorize AI jargon. You need to know which one fits the job in front of you.
Think about a kitchen.
A skill is a recipe card. It is the how-to for one dish. You write it once. Anyone can follow it and get the same plate.
A workflow is the line the food moves down. Chop, cook, plate. Same order, every single service. Nobody on the line decides what comes next. That was decided before the doors opened.
An agent is the chef. You say "make dinner." The chef decides the menu, checks what is in the fridge, and figures it out.
They stack. A workflow can run skills. An agent can use skills. A big system may use all three. So they are not rivals. They are three sizes of the same idea.
Here is the part most people get wrong. They reach for the chef when they needed a recipe card. An agent is the biggest, slowest option. It thinks at every step, which costs more time and more money. A workflow is faster and steadier for work you already know how to do.
The rule of thumb is a ladder. A sharp prompt beats a skill you did not need. A skill beats a workflow. A workflow beats an agent, right up until the job really calls for more. Start at the bottom of that ladder and climb only when you have to.
New here? Use the free AI for Entrepreneurs course outline to read this series in the best order.
Behind the paywall
The diagnosis prompt. Paste your task in and it tells you which of the three it is, then builds it for you.
The one question that decides it, and the exact lists of when each shape wins, with real examples for all three.
The five check questions to run before you build anything.
Where a workflow file and an agent file actually live in Claude Code, and the one starter phrase that gets you an agent with no file at all.
The approval point rule, which is the difference between an agent that helps and an agent that spends your money.
Seven ways people over-build, and the eight point checklist.
What paid subscribers get overall
Paid subscribers get the full build on every lesson in this series. Every copy and paste prompt, every command, every checklist, and every mistake list. Not the summary. The thing you actually run.
You also get the whole back catalog, and the ones coming every other day after this.
Read the rest of this one right now
This is a short lesson that saves long weekends. The diagnosis prompt is the whole point of it.
Module 8 is the build module. Everything in it goes faster once you can name the shape before you start.
<!-- native: divider -->
Paid gets you the diagnosis prompt, the five check questions, the file paths, and the approval rule.
<!-- native: button url="https://www.lizontheweb.com/subscribe?" text="Subscribe to unlock this article now" -->
<!-- native: divider -->
The full walkthrough is below the paywall.
Click the button, subscribe, and the locked section below opens right away. You get this article now.
