The Agent Spectrum

Module 2 · Section 2 of 5

The Agent Spectrum

Not all agents are the same, and treating them as interchangeable leads to either underusing them (asking Claude to “help” with things you could fully hand off) or overusing them (delegating things that genuinely need human judgement).

Here’s a rough spectrum, from least to most autonomous:

Skills are the simplest form. A skill is a markdown file in your ~/.claude/skills/ directory that gives Claude instructions for a specific task. When you say “run the draft-reviewer skill on this document,” Claude reads the skill file and follows it. You’re still in control — you invoke it explicitly, you see the output, you decide what to do next. The skill is just a reusable set of instructions so you don’t have to re-explain your review process every time.

Agents with tools are more capable. You can give Claude access to MCP servers — calendar, email, file systems, web search — and it can use those tools to gather information and act. An agent checking your email and flagging action items isn’t just reading what you paste in; it’s actually fetching the messages, processing them, and returning structured results. You still review and approve anything consequential, but the agent is doing real work.

Subagents go further. Claude Code can spawn subagents — separate instances with their own context and instructions — to work on parallel tasks. A content pipeline might have one subagent researching, another drafting, another reviewing, all running in sequence. You set it in motion and review the final output. The intermediate steps happen without you watching each one.

Autonomous agents are the far end. A cron job that runs your morning-brief skill every day at 7am, compiles your briefing, and writes it to a daily note — that’s fully autonomous. You set it up once and it runs indefinitely. No prompting required.

Where you deploy on this spectrum depends on the stakes and the reversibility of the task.