The idea

So, what is an agent, anyway?

The word gets stretched over everything — a prompt, a tool call, a workflow step, a throwaway context window. awesome-agents uses it for one thing, and means it: a reusable specialist for a kind of work.

Skill Reusable know-how for a task.
Agent A reusable specialist for a kind of work.

A task and a body of work are not the same thing. That gap is the whole distinction.

Skills are for repeatable tasks

Useful when the job is bounded and the result can be checked. A good skill makes a task easy to do consistently.

  • Deploy a Docker image
  • Extract tables from a PDF
  • Generate release notes from commits
  • Run accessibility checks

You verify it: did it run, did it parse, did the checks pass?

Closest to procedures

Agents are for judgment-heavy work

Useful when the work depends on context, standards, and tradeoffs — on a particular way of approaching the problem.

  • A launch editor that critiques positioning
  • A staff engineer reviewing a PR for the long term
  • A protocol reviewer hunting unsafe assumptions
  • An analyst separating signal from noise

You evaluate it: was it useful, did it notice the right risks, would you use it again?

Closest to practitioners

Some things can be verified. Others have to be evaluated.

For a skill, success is mechanical — the file converted, the tests passed, the format matched. Two strong agents can look at the same pull request and disagree, because they optimize for different things. That is not a bug; it is the point. An agent carries a working style: what it pays attention to, what it worries about, what it treats as quality, and what it ignores.

Not a throwaway worker

The definition is the thing that lasts.

Many systems spin up a short-lived worker for a single task. Useful — but that is a run, not the agent.

01

Definition

The reusable specialist: role, behavior, boundaries, tools, examples. What you inspect, version, fork, and come to trust.

02

Instance

One installed copy of that specialist in your environment, wired into the harness you already use.

03

Run

One execution on one task. It does its work and disappears — nothing durable to inspect on its own.

Without a durable definition, every “agent” is just another temporary context window with a nicer name.

Not a rivalry

Agents use skills.

They are not competing ideas. A good agent uses many skills. A release manager uses a changelog-generating skill, then decides what users actually need to know. The skill performs the task; the agent decides how that task fits the work.

A skill is reusable know-how. An agent is a reusable specialist.

That is what this directory indexes — durable agent definitions you can inspect before you run, and compare before you rely on.

Browse the directory Read the docs