On this page
Read
The useful mental model
A skill is reusable know-how that loads on demand. The agent always sees a short name and description, reads the full instructions only when the task matches, and opens extra files or runs bundled scripts only when needed. That keeps the context window light while the skill itself can hold a lot.
In plain English
It is a playbook the agent keeps on a shelf. It reads the title on the spine every time, and takes the whole playbook down only when the job needs it.
Where builders use it
- 01Repeatable document and report tasks
- 02A team's house style and checklists
- 03Publishing workflows with fixed steps and exact checks
Why it matters
A prompt lives in one conversation. A skill packages the same guidance once, so the agent applies it every time, loads it only when needed, and can run bundled scripts for steps that must be exact. Whether a skill actually works is a separate question that testing answers.
Why now
Agent products now let people add their own skills, and Anthropic has published the Agent Skills format as an open standard. Availability and details vary by product, so check the current documentation before relying on a specific behavior.
A common misconception
“A skill is just a longer prompt.”
A prompt lives in one conversation. A skill is a folder the agent discovers and loads on demand, and it can include reference files and scripts. Only its name and description are always in context.
“A skill makes the agent good at the task.”
A skill gives the agent instructions. Whether they work is a separate question, answered by testing the agent on real tasks, which is what evals do.
See
See the mental model
The visual is generated from the same structured knowledge as the written explanation.
Two columns compare a skill and an eval. A skill teaches the agent how to approach a task and contains instructions, references, and scripts. An eval checks whether the agent can do the task and contains tasks, graders, and scores. Each improves the other.
Builder example
Stop re-explaining the same task to an agent
A team asks an agent to publish a glossary entry every week, and each time pastes the same twelve instructions.
Failure
The agent follows the instructions differently each time. Some steps are skipped, and nobody can tell which version of the instructions was used.
Intervention
Package the steps as a skill: a short description that says when to use it, the full procedure in SKILL.md, reference files for the standards, and a script for the checks that must be exact.
Observable result
The agent loads the procedure only for glossary work and runs the same checks each time, and the team improves one file instead of twelve pasted prompts.
Sources
Go deeper
- Anthropic Engineering - Equipping agents for the real world with Agent Skills
- Claude Docs - Agent Skills overview
- Anthropic - Agent Skills repository
Last researched 12 October 2026