Projects vs Agent Skills
A Project is a place with persistent context; a Skill is a procedure that travels. One holds your material, the other holds your method.
Last verified August 21, 2026
The short answer
Use a Project when the same body of material comes up repeatedly — a client, a codebase, a research topic. Use a Skill when the same procedure comes up across different material. Material versus method is the whole distinction.
Can you use both? Yes. A Project holds the context; skills apply inside it.
Side by side
Option A
Projects
A persistent workspace in the Claude apps holding files, custom instructions and conversation history for one body of work.
Pick it when
You keep re-uploading the same documents or re-explaining the same background at the start of every conversation.
Option B
Agent Skills
Folders of instructions, scripts and resources loaded on demand. Portable across the Claude apps, Claude Code, the API and the Agent SDK.
Pick it when
You keep explaining the same process — how to structure a report, how to review a document, what your house style is.
Material versus method
| Projects | Skills | |
|---|---|---|
| Holds | Files, instructions, history | Instructions, scripts, resources |
| Scope | One body of work | One procedure, anywhere |
| Activated by | You opening it | Claude judging it relevant |
| Where | Claude apps only | Claude apps, Code, API, SDK |
| Plan | Free (limited), unlimited on Pro | Pro and above |
The clean test: is the thing you keep repeating the material, or the method?
Re-uploading the same brand guidelines every conversation → Project. Re-explaining how to write a good release note → Skill.
What each one cannot do
A Project cannot follow you. It exists in the Claude apps. Move to
Claude Code or the API and it is not there. CLAUDE.md is the nearest
equivalent for a repository, and it is a genuinely better artefact — reviewed, versioned, shared with
everyone who clones the repo.
A Skill does not carry your documents. It is procedure. If the task needs your files, they come from the Project, from an upload, or from MCP.
The three-mechanism picture
| Question | Answer |
|---|---|
| Where does the material live? | Project (apps) or repository (Claude Code) |
| How should the work be done? | Skill |
| What can Claude reach? | MCP or connectors |
Nearly every “how do I make Claude remember X” question resolves to one of those three, and picking the wrong one produces a setup that half works.
Common misconceptions
- "Projects are the Claude apps version of Skills." They are different concepts that happen to both reduce repetition. Projects persist material; skills package procedure.
- "A Project is like CLAUDE.md." Closer, but CLAUDE.md lives in a repository, is version-controlled and is reviewed in pull requests. A Project lives in the Claude apps.
- "Skills need a Project." They are independent, and skills work in Claude Code and the API where Projects do not exist.
Sources
- 01Claude pricingOfficialclaude.comUnlimited projects listed as a Pro inclusion.
- 02Agent Skills announcementOfficialclaude.com