Claude Skills are folders of instructions that teach Claude to do one task your way, every time. You build a skill once, store it where Claude can read it, and trigger it with a phrase. This guide covers the setup in Claude Chat, Claude Cowork and Claude Code, what goes inside a skill file, and the five mistakes that break them.
This post is part of my guide to AI tools for newsletter creators.
Last updated October 1, 2026.
It is Monday morning. I am sitting at my desk with coffee (of course) and I have to produce a paid newsletter, a free newsletter, a LinkedIn carousel, and three sales emails by Friday. A year ago, that would have meant 25 hours of writing, editing, second-guessing, and rebuilding the same template from scratch every single time.
Instead, I open Claude Cowork, type one sentence, and watch a skill take over. Headline, subtitle, full body, SEO package, image prompts, CTA block. Done in 12 minutes. Two more skills handle the carousel and the emails.
By 11 a.m., I am done. The rest of the day is for client calls, my course, and grilling out with my family on the back deck.
This is what Claude Skills do for solo creators. They turn the messy, repeatable parts of running a business into one-click workflows that match your exact voice, your exact offers, your exact systems.
If you have ever copied and pasted the same prompt into ChatGPT for the 40th time, watched your "draft" come out generic and corporate, or wasted an afternoon getting Claude to remember how you write. Skills are the fix.
**Here is what this guide covers:**
- What Claude Skills are and why they matter for solo creators
- The difference between Claude Chat, Claude Cowork, and Claude Code
- How Claude Skills work in each product
- 10 real creator use cases (so you know what is possible)
- Which skills a content creator should build first
- How to build your first skill with Claude Skill Builder in 30 minutes
- What goes inside a SKILL.md file
- Where to store your skills and how to organize them
- How to install and run a skill (with the trigger trick most people miss)
- Where to find pre-built skills on GitHub and how to vet them safely
- Claude Skills vs. Claude Projects: when to use each
- The five mistakes that kill skills and how to fix them
- The honest math on whether skills are worth the time
- A 5-step plan to get your first skill live this week
Let's go.
What are Claude Skills, and why do they matter for solo creators?
Claude Skills are folders of instructions, examples, and rules that teach Claude how to do a specific task the way you want it done, every single time. Each skill is a reusable workflow you build once and run forever. For solo creators, that means your newsletter, your sales emails, your LinkedIn carousels, and your offer pages all spin off the same brain you trained, instead of starting from a blank prompt.
A skill is a small file inside a Skill folder, called SKILL.md. That file holds the rules: what task this skill performs, when Claude should use it, and how Claude should handle the work step by step.
Anthropic launched Skills in October 2025. Since then, the use case for solo creators has gone from "interesting" to non-negotiable.
**Here is why.**
A lot of creators are paying $20 to $200 a month for AI tools they barely use. They open ChatGPT, paste a half-baked prompt, and get a draft that sounds like every other Substack post on the internet.
A longer prompt will not fix that. A skill will.
When I write a paid newsletter issue, I do not type instructions into Claude. I open Cowork, point at the topic, and a skill called 9tothrive-paid-newsletter runs the entire workflow. SEO block, headline variants, full body in my voice, image prompts, sign-off, P.S. line.
I have 36 of these in my Skills folder right now. Each one runs a different part of my business.
Skills matter for creators because:
- They make your AI output sound like you, not the average internet writer
- They cut a four-hour task to 12 minutes without losing quality
- They keep your brand voice consistent across every asset, every week
- They let you grow without hiring
- They store your best thinking outside your head
- They know your frameworks, methods, terminology, and everything about you, your business, and your offers
This is the core of running a portfolio business with AI as your unfair advantage.
What's the difference between Claude Chat, Claude Cowork, and Claude Code?
Claude Chat (claude.ai) is the conversational version you use in your browser for thinking, writing, and quick research. Claude Cowork is a desktop app for non-developers that runs multi-step tasks across your files, folders, and connected tools. Claude Code is a command-line tool for developers building software. All three run skills. Cowork is the one most solo creators want.
Three products. One brain. Different jobs.
Claude Chat (claude.ai)
This is the version most people meet first. You open a tab, type a question, get an answer. Free for basic use, $20 a month for Claude Pro, and higher tiers if you need long context windows or extra usage.
Use it for: brainstorming, drafting, quick research, asking questions, working through messy ideas. Best for "thinking with Claude."
Limitation: it cannot reach into your files, run scripts, or execute multi-step workflows on its own.
Claude Cowork
This is the desktop app. You install it on your Mac or PC, point it at a folder, and Claude can read your files, write files, run skills, and orchestrate full workflows without you touching code.
This is where my entire business runs. Every newsletter, every carousel, every sales email starts here.
Use it for producing real deliverables: Word docs, PDFs, spreadsheets, decks. Running multi-step skills. Working across your local files and connected apps like Notion, Gmail, Google Drive, and Substack.
Claude Code
This is for developers. It lives in your terminal. It writes code, edits codebases, runs tests, and ships pull requests. If you do not write software for a living, you do not need it.
That said: many of the best skill templates live inside the Claude Code ecosystem on GitHub. So even if you are not a developer, you will draw on that world as you start to build skills.
The short version: solo creators want Cowork. Some get away with Chat plus a few skills. Almost no creator needs Code.
How do Claude Skills work in each Claude product?
Skills work the same way across all three Claude products. A folder with a SKILL.md file gets stored where Claude can find it, and Claude pulls in the skill when your request matches its trigger description. The difference is in setup. Chat uses uploaded skills via the web interface, Cowork reads from a local Skills folder you point it at, and Code reads from .claude/skills inside your project.
Same skill file. Different storage location. Same end result.
Skills in Claude Chat
Inside claude.ai, you upload skills through the Customize menu under Skills. You zip your skill folder, click the plus button, and Claude installs it inside your account. Once installed, Claude reads the description and triggers the skill when your prompt matches.
This is fine for one or two personal skills. It is not great if you want to maintain 36 of them or share them with a team.
Skills in Claude Cowork
Cowork reads skills from a local folder on your computer. You connect a folder once. After that, every skill inside that folder is available the moment you start a session.
This is what I use. My folder lives at Desktop/Claude Cowork/Skills/. I have 36 markdown files in there. When I tell Cowork to write a paid newsletter, it picks up 9tothrive-paid-newsletter.md and runs.
The benefit: you can edit a skill in any text editor, save it, and Cowork reads the new version next time you trigger it. No upload step. No version drift.
Skills in Claude Code
Skills live inside .claude/skills/ in your project folder. Each skill is its own subfolder with a SKILL.md file. Code uses these to handle repetitive engineering tasks like running tests, refactoring, or generating components in your stack's exact pattern.
For creators, the takeaway is simple. Pick one product, store your skills there, and write the skill once. The same SKILL.md file will run in any Claude product you connect it to. You build it once, you own it forever.
What can you do with Claude Skills? (10 real creator use cases)
You can build a Claude Skill for any repeatable task in your business. The most useful ones for creators are content production (newsletters, social posts, sales emails), brand management (voice rules, banned words, image specs), audience research (ICP profiles, competitor scans), and offer building (sales pages, lead magnets, course outlines). One creator can run a full content business off ten well-built skills.
These are the ten skills I use most often. Each one runs a workflow I used to do manually for years.
1. **Weekly free and paid newsletters.** Produces the full weekly issue with SEO block, body, image prompts, sign-off.
2. **About page or section.** For Substack and LinkedIn.
3. **Hero post writer.** Long-form pillar for your publication hero section.
4. **LinkedIn single post.** Turns any newsletter into a 250-word LinkedIn post.
5. **LinkedIn carousel.** Turns any topic into a 7 to 10 slide branded swipe deck.
6. **Email.** Builds email sequences using a fixed architecture.
7. **Sales page.** Produces a full long-form sales page from an offer brief.
8. **Lead magnet.** Creates the freebie, the landing page, and the welcome sequence.
9. **Brand voice enforcement.** Checks every draft for tone, banned words, AI tells, and language style.
10. **Customer research.** Pulls real reader pain points from sources you specify.
Below that list, I have skills for cold email, copy editing, Notes, images, paid ads, SEO audits, schema markup, customer onboarding, and more. The full Skills folder is the operating system of my business.
The pattern is the same every time: identify a task you do at least once a month, write down how you do it, turn that into a SKILL.md file, save it, point Claude at it.
Skills are the unfair advantage. The average creator is still copy-pasting prompts.
Which Claude Skills should a content creator build first?
Build the skill for the thing you publish every week first, then the skill for the thing you sell. For most content creators that order is: the weekly piece, the social post that promotes it, the email sequence behind the offer, the sales page, and a voice check that reads every draft before it ships. Five skills cover most of a content business.
Here is the order I give creators who write for a living.
**1. The weekly publish skill.** Your newsletter, your blog post, your video script. The thing with a deadline attached. This is the skill you will run 52 times a year, so it earns its build time faster than anything else.
**2. The repurpose skill.** Takes the finished piece and turns it into the social post, the Note, or the carousel. Feed it the published piece, not the outline, or the output drifts.
**3. The voice check skill.** No writing, only reading. It holds your banned words, your sentence rules, your formatting rules, and it marks every line that breaks one. I run this last on everything, including this guide.
**4. The offer skill.** Sales page, email sequence, launch assets. Lower frequency, higher stakes, so the examples inside it matter more than the instructions.
**5. The research skill.** Pulls reader questions, competitor angles, and real quotes from sources you name. This one keeps the other four from running on your opinions alone.
Build them in that order and stop. A creator with five tested skills ships more than a creator with 30 untested ones.
How to use Claude Skill Builder to create your first skill
Open Claude (Chat, Cowork, or Code), type "create a new skill," and follow the conversational prompts. Claude Skill Builder asks what task you want to automate, walks you through the trigger description, the step-by-step instructions, and the example outputs, then generates a working SKILL.md file you can save into your Skills folder. Total time for your first skill: 15 to 30 minutes.
Anthropic ships a built-in skill called skill-creator (often called Claude Skill Builder). It writes skills for you through conversation. You do not need to know markdown, YAML, or any technical syntax.
Here is the exact process I use to build a new skill in under 20 minutes.
**Step 1: Open Claude and trigger the skill.** In Cowork, type "I want to create a new skill" or "use the skill-creator skill." Claude pulls up the skill-creator and starts the conversation.
**Step 2: Describe the task.** Tell Claude what you want the skill to do. Be specific. "Write a weekly paid newsletter" is too vague. "Write a 1,500-word paid newsletter for my Tuesday issue, with an SEO package, three subject lines, an image prompt, and a P.S. line, in my voice" is the level of detail you want.
**Step 3: Describe the trigger.** This is the description Claude reads to decide when to fire the skill. Include the exact phrases you will use. "Write my Tuesday newsletter," "draft this week's paid issue," "create a paid newsletter on this topic." List them all.
**Step 4: Walk through the steps.** Tell Claude how you want the work done. What goes first? What goes last? What rules matter? What banned words exist? Claude turns your answers into structured instructions.
**Step 5: Add an example.** Paste in one or two real examples of what good output looks like. This is the single biggest quality lever. The skill will pattern-match against your examples.
**Step 6: Test it.** Save the skill, restart Claude, and trigger it on a real task. The first version will need tweaks. The third version will be 90% there.
This is also the safest way to build a skill if you are a non-developer. You are not writing code. You are having a conversation. Claude writes the file. If you are still in the early days of building your newsletter, [How to Start a Newsletter Business on Substack](https://thrivewithcarrie.substack.com/p/start-newsletter-business-on-substack) is the place to begin. Then build your first skill once you have a real workflow to automate.
For the official documentation, Anthropic's [Agent Skills overview](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview) goes deep on the technical side.
What goes inside a Claude Skill file?
A Claude Skill file is a single markdown file called SKILL.md. It opens with YAML frontmatter (a small block at the top with name and description). The body holds the written instructions, rules, examples, and any reference materials Claude should follow. The description is the most important part. It is what Claude reads to decide whether to use the skill.
The structure is simpler than it sounds. Here is the anatomy of every skill on my drive.
**1. The frontmatter (top 5 lines).** A small block between three dashes. Inside it, two lines: name, which is the file name, and description, which tells Claude when to fire, written with the exact phrases you will type. Keep it specific and trigger-rich.
**2. The role.** A short paragraph telling Claude who it is for this task. "You are a long-form sales page writer for a creator selling a $597 course." This sets context.
**3. The rules.** Bulleted list of things Claude must always do. And things Claude must never do. Banned words. Required sections. Voice constraints. Format requirements.
**4. The steps.** The exact sequence Claude follows when the skill runs. Step one, step two, step three. Numbered. Specific. I ask Claude to ask me questions at the beginning of every skill to ensure we are in alignment.
**5. Examples.** Real before-and-after snippets showing what good output looks like. The more specific, the better. You can also load your proprietary frameworks, processes or systems for the skill to follow.
**6. The output format.** Tell Claude exactly how the deliverable should be structured. What sections, in what order, in what file format.
That is it. Six parts. Most of my skills are between 300 and 800 words. The longest are 2,000.
The mistake new builders make is overthinking the file. A 200-word skill with one good example will perform better than a 2,000-word skill with no examples every time. Specifics over volume. Always.
Where to store your Claude Skills (and why folder structure matters)
Store your Claude Skills in one dedicated folder on your computer (a Skills subfolder inside your primary working directory works well). Keep each skill as its own .md file or its own subfolder if it has reference materials. Name the folder Skills, point Claude Cowork at it, and back it up to cloud storage. Your folder structure is your operating system. Treat it like one.
Skills live in three possible places. Pick one and stay consistent.
**1. A local Skills folder (recommended for Cowork users).** Mine is at Desktop/Claude Cowork/Skills/. Every skill is a single .md file in that folder. When I open a Cowork session and point at the parent folder, every skill is instantly available.
This is the cleanest setup for solo creators. You can see every skill at a glance, edit any one of them in any text editor, and back the entire folder up to iCloud or Google Drive.
**2. The Anthropic skills GitHub repository (for shared or open-source skills).** Anthropic maintains a public skills repo on GitHub. Some creators store their skills inside a GitHub folder so they can version-control them and share with collaborators. Useful if you have a team. Overkill if you are solo.
**3. Inside your Claude account (for Chat).** If you only use claude.ai, your skills live inside your account, uploaded through the Customize menu. Easy, but harder to back up and edit at scale.
Folder structure rules I follow
- One folder. Not five scattered across your drive.
- Lowercase, hyphenated file names: paid-newsletter.md, not Paid Newsletter Skill v3 FINAL.md.
- One skill per file. Do not bundle three skills into one giant file.
- A README at the top of the Skills folder listing every skill and what it does.
Backup matters. Your skills are the operating system of your business. If you lose them, you lose months of refined thinking. The same way [your Substack Notes strategy](https://thrivewithcarrie.substack.com/p/substack-notes-strategy-2026) is only as strong as the system behind it, your skills are only as strong as the folder they live in.
How to install and run a Claude Skill
To install a skill in Claude Cowork, drop the skill file into your connected Skills folder. Cowork reads it the next time you start a session. To install a skill in claude.ai, zip the skill folder, go to Customize > Skills, click the plus button, and upload it. Once installed, you trigger the skill by typing a phrase that matches its description, or by saying "use the [skill name] skill."
Installation is the part that scares most non-developers. It should not.
**Cowork installation (under 60 seconds):**
1. Open the Skills folder you connected to Cowork.
2. Drop your .md file inside it.
3. Start a new Cowork session.
4. Type a phrase that matches the skill's description.
5. Claude finds the skill and runs it.
That is it. No upload. No restart. No technical setup.
**Claude Chat installation (3 to 5 minutes):**
1. Put your skill folder on your desktop.
2. Right-click > Compress > zip file.
3. Open claude.ai > Customize > Skills.
4. Click the plus button > Create skill > upload zip.
5. Wait for the install confirmation.
For the full step-by-step from Anthropic, the [Claude help article on creating custom skills](https://support.claude.com/en/articles/12512198-how-to-create-custom-skills) walks through both paths.
Running a skill once it's installed
You do not have to call the skill by name. Claude reads the description and triggers the right skill automatically when your request matches.
That said: if Claude is not picking up the right skill, you can force it by typing "use the [skill-name] skill" or "trigger [skill-name]." This is the override.
How to know your skill is running
Look for the skill loading message at the start of Claude's response. In Cowork it shows a small banner. In Chat it appears as a system message. If you do not see a confirmation that the skill loaded, the skill is not running and you are getting a generic Claude response.
This is the single most common mistake new users make. They think the skill is running. It is not. Then they wonder why the output is generic. Always check the load confirmation.
Where to find Claude Skills you can use as a starting point
The fastest way to start with Claude Skills is to fork an existing one and edit it for your business. Anthropic maintains a public skills repository on GitHub at [github.com/anthropics/skills](https://github.com/anthropics/skills) with dozens of example skills you can study and adapt. You can also ask Claude to search GitHub for community skills using a prompt like "search GitHub for public Claude skills related to [your topic]." Always read the full skill before you run it.
You do not have to build every skill from scratch. The Claude ecosystem already has hundreds of pre-built skills you can adapt.
Where to look first
- **Anthropic's public skills repo** at [github.com/anthropics/skills](https://github.com/anthropics/skills). This is the official source. Skills here are vetted, documented, and safe.
- **The Claude Skill Builder built into Claude itself.** Ask "show me the example skills available" inside Claude and it will surface the ones already on your machine.
- **GitHub search.** Type "claude skills" or "SKILL.md" into GitHub search. You will find hundreds of community-built skills, ranging from excellent to broken.
- **Creator marketplaces.** Some creators sell skill packs through Gumroad and Substack. These are pre-built for specific use cases like newsletters, sales pages, or cold email.
How to find skills on GitHub without leaving Claude
Tell Claude this:
> Search GitHub for public Claude skills related to [your topic]. List the top 10 by stars, with the repo URL and a one-sentence summary of what each does.
Claude will run the search and return a curated list. Pick one, read the SKILL.md file in full, and decide if it is worth adapting.
One word of caution
Read every skill before you run it. Top to bottom. Twice if it has multiple files.
A poorly written skill can produce content that does not sound like you, contradicts your brand rules, produces results that don't align with your beliefs and methods, or wastes hours of your time. A maliciously written skill can do worse. Execute code, send data, or modify files in ways you did not intend.
Treat every skill from the internet the way you would treat a contract. Read it. Test it on a low-stakes project first. Confirm it does what you want before you run it on a real deliverable.
The good skills will save you hundreds of hours. The bad ones can cause havoc.
Claude Skills vs. Claude Projects: which one should you use?
Claude Projects are containers that hold context, files, and a custom system prompt for an ongoing area of work, useful for "this is my newsletter project" or "this is my book." Claude Skills are reusable, repeatable workflows that run a specific task, useful for "write my Tuesday newsletter every week." Most solo creators want both. Use a Project as your home base. Run Skills inside it.
This is the question I get most often from creators new to Claude.
Claude Projects in plain language
A Project is a workspace. You set it up once. You give it custom instructions ("you are my newsletter editor; here is my brand voice"). You upload reference files (your style guide, your customer avatars, your offer catalog). Then every conversation inside that Project automatically inherits the context.
Use a Project when: the work is ongoing, the context is heavy, and you want continuity across sessions.
Best for: book writing, course creation, brand management, ongoing client work.
Claude Skills in plain language
A Skill is a workflow. It runs a specific task. It produces a specific output. It does not need to live inside a Project to work.
Use a Skill when: the task is repeatable, the output is consistent, and you want the same result every time.
Best for: weekly newsletters, sales emails, social posts, lead magnets, sales pages.
How to run them together
This is the setup that pays off for solo creators. Make a Project for your business. Add your brand voice document, your offer catalog, and your customer avatars to the Project knowledge. Then run your Skills inside that Project.
**Result:** every Skill runs with the full context of your business already loaded. The output sounds more like you, more on-strategy, more on-offer.
Without Projects, every Skill starts from zero context. With Projects, every Skill starts with your full operating manual already in memory.
Common mistakes that kill your Claude Skills (and why testing matters)
The five mistakes that kill Claude Skills are: vague descriptions that do not trigger, missing examples, skills that try to do too much in one file, no testing before production use, and copy-pasted skills from the internet that conflict with your brand voice. The fix is the same in every case. Write specific descriptions. Include real examples. Scope skills tightly to one task. Test on a low-stakes project before you ship.
The skills that fail share the same patterns.
**1. Vague descriptions.** If your description says "writes content," Claude will trigger this skill on every prompt that mentions writing. The skill will fire when you do not want it. Or worse, it will not fire when you do. Be specific. Include exact trigger phrases.
**2. No examples.** A skill without examples is a skill that produces generic output. Examples are how the skill learns your voice. If you skip them, you are rolling the dice every time.
**3. Too much in one file.** Skills that try to write a newsletter, design the carousel, create the email, and build the sales page all in one file produce average work on every output. Split them. One skill, one job.
**4. No testing.** You wrote the skill. It looks great. You ship it on a real launch. The output is wrong, the brand voice is off, and you spent two hours rewriting everything by hand. Always test on a low-stakes project first.
**5. Copy-pasted skills from the internet.** A lot of public skills are written by developers for developers. The voice is wrong. The structure is wrong. The output is wrong for your business. Adapt before you use.
The fix for every mistake is the same: be specific. Use real examples. Scope tightly. Test before you ship.
How I test a new skill
I run it three times on real work. Once on an old asset I already shipped (so I can compare). Once on a current asset I am working on. Once on a deliverable I would be happy to throw away if the skill produces garbage.
If all three pass my review and deliver the result I want, the skill goes into production. If two out of three pass, I revise. If only one passes, I scrap it.
Are Claude Skills worth the time if you're a solo creator?
Yes, if you do any of the same tasks more than once a month. The break-even on a well-built skill is usually three to four uses. After that, every run is pure time saved. The creators who get the most value from Claude Skills are not technical. They are systems thinkers running content businesses where the same workflows repeat every week.
Here is the math.
Building a skill takes 15 to 60 minutes the first time. Writing the trigger, the rules, the steps, and the examples. Testing it. Tweaking it.
Once it is built, every run takes 10 to 20 minutes (depending on how complex the deliverable is) instead of two to four hours of manual work.
If you ship one paid newsletter a week, you save roughly 8 to 12 hours a month per skill. Over a year, that is 100+ hours per skill.
I run 36 skills for different tasks. The math works out to multiple full-time hires worth of saved time per year. And the output is more consistent than what I produced manually three years ago.
The question is not "is it worth it." The question is "which workflow do you build first."
The skills with the highest ROI for creators
In order:
1. Whatever you do every single week (newsletter, podcast intro, weekly recap)
2. Whatever you do every single launch (sales emails, sales page, launch sequence)
3. Whatever you do every single client call (call prep, follow-up, proposal)
4. Whatever you do every single month (monthly review, performance report, content audit)
Build the weekly skills first. Build the launch skills second. Build the client skills third. Build the monthly skills last.
How to start using Claude Skills this week
The fastest way to start is to pick one task you do every week, open Claude, and tell Skill Builder to create a skill for that task. A solo creator can have their first working skill live in 30 minutes. You do not need a developer, a budget, or a technical background. You need one repeatable workflow, 30 minutes, and the willingness to test it twice.
Do not try to build 36 skills your first week. Build one.
Pick the task you do most often. The one you are sick of doing manually. The one where you feel yourself opening the same template, copying the same prompts, fighting the same blank-page dread.
Your 5-step plan for this week
1. **Today:** open Claude (Cowork if you have it; Chat if you don't). Type "I want to create a new skill" and answer the questions. Build a draft skill in 30 minutes.
2. **Tomorrow:** test the skill on a real piece of work. Compare the output to what you produced manually last time. Note where the output is great. Note where it falls short.
3. **Day three:** revise the skill. Add a missing example. Tighten a vague rule. Add a banned-word list. Run it again.
4. **Day four:** ship something with the skill. A newsletter, an email, a social post, whatever the skill is for. Use the output (with light edits) on a real deliverable.
5. **Day five:** decide if the skill earned its keep. If yes, keep building skill #2 next week. If not, revise once more or scrap and rebuild.
The creators who win with AI are not the ones who buy the most tools. They are the ones who build the smallest set of skills they use every week.
One skill. This week. Then build the next one.
Claude Skills FAQ
**Can you use Claude Skills in Claude chat?**
Yes. In claude.ai, go to Customize, then Skills, click the plus button and upload your skill folder as a zip. Claude installs it in your account and triggers it when your prompt matches the skill's description.
**Do you need to know how to code to build a Claude Skill?**
No. A skill is a markdown file of plain-English instructions. Claude's built-in skill-creator writes the file for you through a conversation, so you answer questions instead of writing syntax.
**How long does it take to build your first Claude Skill?**
15 to 30 minutes for a working first version, and two or three more runs to get it right. My rule is three tests on real work before a skill goes into production.
**What is the difference between a Claude Skill and a Claude Project?**
A Project holds context: files, brand documents, a system prompt for an ongoing area of work. A Skill runs a task the same way every time. Keep the Project as your home base and run Skills inside it.
**Where do Claude Skills live on your computer?**
In Claude Cowork, in a local folder you connect once (mine is Desktop/Claude Cowork/Skills/). In Claude Code, in .claude/skills inside the project. In Claude Chat, inside your Claude account.
**Can one skill file work in Chat, Cowork and Code?**
Yes. The SKILL.md format is the same in all three. Only the storage location changes, so you write the skill once and point each product at it.
---
Written by Carrie Loranger, Substack strategist with 18 years in corporate marketing (Fortune 500 and B2B), known for helping writers turn one newsletter into a portfolio of paychecks. Her publication 9-To-Thrive is a Substack Bestseller and a Top 50 Substack Business publication, and she has helped hundreds of writers set up, grow, and monetize on Substack. Start with her origin story: [The meeting that ended my corporate career and started my portfolio business](https://thrivewithcarrie.substack.com/p/start-here-turn-one-newsletter-into).
Want the rest of the playbook?
This post gives you the what. The Academy gives you the how, one module at a time, with a worksheet for every lesson and the order I followed to grow from zero to 12,600+ subscribers.
These are my results, not typical ones. Most people grow more slowly.
Paid members get every course in The Academy, my bestselling digital products and every monthly challenge. VIP adds 1:1 time with me and Academy LIVE group coaching.
Want this done with you? See 1:1 Substack coaching and the Substack Audit at carrieloranger.com.


Ok listen, I’m no novice when it comes to Claude. That said, this is INCREDIBLY well-laid out and I got some new things to try out of it.
More people should read this as a primer. Well- played Carrie!
? What