"here we connect and innovate"
Learning objectives
Projects, covered in the previous lesson, handle general recurring context — who you are, what you do, how you like things communicated. Skills solve a more specific problem: a particular task you do the same specialized way, over and over, that deserves its own dedicated instruction set rather than being folded into general Project context.
A Skill is a reusable instruction package built for a specific type of task, that automatically loads when that kind of task comes up, rather than being manually re-explained or re-pasted every time. Where a Project sets broad, ongoing context, a Skill is narrower and more procedural: it’s built around exactly how you want one particular kind of task handled.
The two features solve related but distinct problems, and it’s worth knowing which one fits a given need.
| Feature | Solves | Best For |
| Project | Repeating general background across many different tasks | Ongoing context for a job, client, or area of life |
| Skill | Repeating one specific, detailed procedure | A narrow, well-defined recurring task done the same specialized way each time |
Imagine you write social media captions in a very specific brand voice — casual, a particular sentence rhythm, certain words you always avoid. Rather than pasting a long style guide into every conversation where you need a caption, a Skill built around exactly that style guide can apply automatically whenever a caption-writing task comes up, without you needing to re-explain it.
You don’t need to build a Skill from scratch by hand. A practical starting point is simply asking Claude directly to help construct one: describe the recurring task in detail, the style or standard you want followed, and ask Claude to draft a Skill file based on that description. From there, you refine it the same way you’d refine any other output — through targeted follow-up instructions.
Real-world example
Before a Skill Exists
Before
Pasting a full brand style guide into the conversation every single time a new caption is needed.
After
A Skill already encodes the brand style guide, so a simple request like “write a caption for this new product photo” automatically applies the correct voice.
Analogy
A Skill is a bit like a specialized checklist a professional keeps for one specific recurring job — a pilot’s pre-flight checklist, for instance, isn’t their general knowledge of flying; it’s a precise, repeatable procedure for one particular task, followed the same way every time.
Best practices
Common mistakes
Important note
Skills and Projects can complement each other. A Project might hold your general working context, while a Skill nested within or alongside it handles one specific, detailed recurring procedure within that broader context.
Lesson summary
A Skill is a reusable, narrow instruction package for a specific recurring task, distinct from a Project’s broader ongoing context. It’s most valuable for tasks you do the same specialized way repeatedly — a particular writing style, a specific analysis format, a consistent report structure — and it can be drafted with Claude’s own help, then refined like any other output.
Hands-on exercise
Objective
Identify a real recurring task in your own work that would benefit from a dedicated Skill, and draft a plan for it.
Instructions
Expected outcome
A draft Skill description for one real recurring task, plus a clear understanding of how it differs from general Project-level context.
Task: writing weekly internal status updates in a specific three-section format (Completed, In Progress, Blockers), always under 200 words, professional but not stiff.
Draft Skill description covers this exact structure and tone. Distinct from Project instructions, which cover general role and team context rather than this one specific recurring format.
Reflection Question: How is the task you identified for a Skill different in kind from the general context you’d put in a Project — what makes it narrow and procedural rather than broad and ongoing?
Key takeaways