← Back to all free guides

Skill vs Workflow
vs Agent

Everyone throws these three words around and it makes AI feel impossible. Here’s the plain-English difference, plus the one question that tells you which to reach for.

You don’t need to memorize AI jargon. You need to know which of three tools fits the job in front of you. Screenshot this part.

01

Skill

A task you do on repeat. Teach Claude once and it does it your way every time.

02

Workflow

A fixed set of steps, run in the same order every time. You decide the steps and Claude runs them.

03

Agent

An expert you hand a goal to. It figures out the steps and keeps working until the job is done.

Skill: A Task On Repeat

A skill is a saved set of instructions for one specific job. In Claude it’s a folder with a SKILL.md file inside. The file starts with a name and a short description of what it does and when to use it, followed by the steps. Claude keeps only those short descriptions in view and opens the full skill when your request matches one, so you can save a whole stack and nothing slows down. (Anthropic’s skills docs)

Use one when you catch yourself explaining the same task over and over, like your report format, your brand voice or the way you want an email audit run.

Plain Example

My email flows audit is a skill. Install it once and every audit comes out in the same format, scored the same way. Grab the email flows audit skill here.

Workflow: Fixed Steps

A workflow is a sequence you lay out in advance and run in the same order every time. Claude isn’t deciding what to do next. You already decided. Anthropic describes workflows as paths that are "predefined," while agents "dynamically direct their own processes." (Building effective agents)

Use one when you know the exact steps and want the same result every time. For anything predictable, it’s faster, cheaper and more reliable than an agent.

Plain Example

A video transcript goes in. Every time, it drafts the blog post, pulls 5 captions from it, then writes the email. Same steps, same order.

Agent: Hand Off A Goal

An agent is Claude given a goal and the tools to reach it. It decides its own steps and keeps going until the job is done. You hand it a job the way you’d brief a specialist you trust. Its expertise comes from the role and tools you give it, so you can set up an email strategist, a Meta ads media buyer or a research agent.

Use one when the task is open-ended and you can’t script the steps ahead of time.

Plain Example

Give a Meta ads media buyer agent your ad account and say "find what’s wasting spend this week and tell me where to move it." It picks which campaigns to dig into instead of following a list. Agents can use skills too, so you can hand your expert the skills it needs.

Which One Do You Need?

Picture a kitchen. A skill is a recipe card. An agent is the chef you tell "make dinner," who decides the menu. A workflow is the line every plate runs down the same way. Most real systems end up using all three.

Ask one question about the task in front of you, then match it below.

  1. Is it the same task done the same way over and over? Build a skill.
  2. Known steps that must run in order? Build a workflow.
  3. Needs figuring out, the way an expert would? Use an agent.

When in doubt, start smaller. Anthropic’s own advice is to find "the simplest solution possible" and add complexity only when you need it. A sharp prompt beats a skill you didn’t need, and a skill beats an agent until the job calls for more.

Steal This Prompt

Paste this into Claude, describe a task you keep doing, and it tells you whether it should be a skill, workflow or agent, then builds it with you.

Skill, Workflow, Or Agent For My Task
You are a practical AI systems coach. I want to turn a repetitive or chaotic part of my work into a real AI system, but I'm not sure whether it should be a skill, a workflow, or an agent. Help me decide, then build the right one. Use plain language. The task I keep doing: [describe it, e.g. "answer customer support emails" or "turn my video into a blog post, captions, and an email"] About me: - What I do: [role / business] - What "done well" looks like for this task: [your standard] - Tools I already use: [list] - An example of this task done well, if I have one: [paste or attach] Do this: 1. Diagnose it. Tell me which of the three this task needs, and why, in three lines or fewer: - Skill if it's the same task done the same way on repeat. - Workflow if it's a fixed set of steps that always run in the same order. - Agent if it's open-ended and needs judgment, where the steps change each time. If it needs more than one, tell me how they combine and start me with the simplest piece. 2. Build it. - If a SKILL: write the full SKILL.md. Start with frontmatter: a name in lowercase-with-hyphens, and a description that says what it does and when to use it. Then clear step-by-step instructions, the exact inputs you need from me, the output format, and one short example. - If a WORKFLOW: lay out the exact ordered steps from trigger to finished result, what goes in and comes out of each step, and mark where I approve before anything is sent or published. - If an AGENT: write its role brief, covering who it is, its goal, 3 to 5 principles it always follows, the tools or info it needs, what it must ask me before doing, and what "finished" looks like. 3. Start me today. Give me the single smallest first step, then run it with me right now on a real example of the task. Rules: - Pick the simplest option that will actually work. Don't suggest an agent when a skill will do. - Don't invent tools, integrations, or features I didn't mention. If something would need a tool I don't have, say so. - Never let it send, publish, delete, or spend without my approval. When you're done, ask me the 2 questions that would make this fit my work better, then revise.

You’ll stop feeling behind on AI the moment this clicks. Look at a task, ask which of the three it is, and you can build almost anything.