Claude Skills vs Projects: Separate Procedures from Project Knowledge¶

For / Key Points

For: Practitioners who want Claude to retain workflows or project material

Key Points: - Put repeatable procedures in Skills - Put case-specific source material in Projects - Combine both when a project needs a shared operating procedure

If you repeat the same reporting format every week, use a Skill. If Claude needs Product A specifications and meeting notes, use a Project. The features are complementary layers for separating procedure from project knowledge.

The decision is: should this information travel across projects, or change with one project?

The short answer: procedures in Skills, context in Projects¶

A Skill packages instructions for a specific task. Claude evaluates its name and description, then loads instructions, references, or scripts when relevant. Anthropic describes this as progressive disclosure.¹

A Project is a workspace that groups chats, Project knowledge, and Project instructions for one body of work. Uploaded material becomes background knowledge for conversations inside that Project.²

Decision axis	Skills	Projects
Primary role	Reusable procedures and criteria	Case-specific material and guidance
Scope	Multiple conversations and supported Claude surfaces when enabled	The selected Project
Loading model	Loads relevant material dynamically	Retrieves Project knowledge and can use RAG at scale
Update trigger	The workflow changes	The case material or policy changes
Typical content	Review workflow, report format, validation script	Product specs, client files, research data

What belongs in a Skill¶

Put the “how” that survives a change of project into a Skill. A custom Skill can contain only instructions or add reference files and executable scripts when the workflow requires them.³

---
name: weekly-report
description: Organize weekly progress into outcomes, blockers, and next actions
---

## Weekly report
- Select no more than three outcomes
- Attach an owner and next action to each blocker
- Never infer an unverified number

Good candidates include report formats, code-review criteria, document workflows, and internal checklists. Do not embed a client name or this week's metrics in the Skill; that makes a reusable procedure stale.

What belongs in a Project¶

Put the evidence needed for one case into a Project. Add requirements, meeting records, and research to Project knowledge, then place durable response guidance in Project instructions.

One important boundary is that content from one chat is not automatically shared with every other chat in the Project. Move decisions that must persist into Project knowledge or instructions instead of leaving them only in conversation history.⁴

When Project knowledge grows, Claude can enable retrieval-augmented generation automatically. The older claim that every file is always loaded or that a Project permanently consumes a fixed 200K-token block is therefore misleading.²

Four questions for choosing¶

Use these questions in order:

Will another project reuse the procedure? If yes, use a Skill
Does the content change with the client, product, or period? If yes, use a Project
Does the workflow need scripts or templates? If yes, use a Skill
Must multiple chats consult the same evidence? If yes, use Project knowledge

For example, “how to produce a monthly report” is a Skill. Client A's sales CSV and quarterly target belong in a Project. Running the Skill inside that Project keeps the procedure and evidence independently maintainable.

Current availability notes¶

Skills are available on Claude Free, Pro, Max, Team, and Enterprise, and require code execution to be enabled. Claude Code and API availability follows separate rollout states; Anthropic currently describes those surfaces as beta.⁵

Project counts, sharing, and organization controls vary by plan and administrator settings. Check the current Projects UI and official help instead of copying a pricing matrix into a durable workflow article.

The current primary management surface for Skills is Customize > Skills. Do not rely only on the older Settings > Capabilities > Skills path.

Operating rules¶

Keep case data out of Skills and pass it as input
Keep response policy in Project instructions and long source material in knowledge
Promote durable decisions from chat history into Project knowledge
Document the responsibility of each Skill and Project in one sentence

Summary¶

This is not a choice of one feature over the other. Put slowly changing procedures in Skills and case-specific knowledge in Projects to reduce stale duplication.