Workshop Modules
Your Claude Business Brain Playbook

Enter the access code from your workshop email.

You built your Business Brain✦Talk to Claude, don't just chat✦Your context travels with you✦Done over perfect✦Five files, briefed before every task✦Cowork like it's your new hire✦You built your Business Brain✦Talk to Claude, don't just chat✦Your context travels with you✦Done over perfect✦Five files, briefed before every task✦Cowork like it's your new hire✦
Your Claude Business Brain Playbook
⌂ Home
▶ Replay ☰ Transcript
1 Chat vs Cowork
2 Build Your Business Brain
3 Make Your First Lead Magnet
4 Connectors and Skills
5 Stay Portable, Stay Safe
✦ Resources
☀ Claude Girl Summer

Your Claude Business Brain Playbook

From the June 11 workshop with Anne Murphy and Sarah Mary.

Five short modules, each ending with a checkpoint that tells you you're ready for the next. The menu gets you to the replay, your resources, and everything else any time.

Start — Chat vs Cowork →
  • 1

    Chat vs Cowork

    The desktop app running — or a working fallback — and the right surface for the job.

    →
  • 2

    Build Your Business Brain

    Five context files Claude reads before it does anything for you.

    →
  • 3

    Make Your First Lead Magnet

    One draft lead magnet built from the brain that sounds like you.

    →
  • 4

    Connectors and Skills

    One connector live and one skill drafted from your SOP.

    →
  • 5

    Stay Portable, Stay Safe

    Your context in files you keep, and a clear line on what never enters a hosted model.

    →
Resources

Resources

Everything from the workshop you can keep using — the Skill Builder, the guides, and the companions.
  • Business Brain Template

    The five files to copy and paste, ready to drop into your project.

    Coming soon
  • Claude in Chrome

    The guide to running Claude right inside your browser.

    Coming soon
  • Moving from ChatGPT to Claude

    What changes and how to bring your work across.

    Coming soon
  • Your Next 30 Days

    A roadmap for what to build first and what comes after.

    Coming soon
  • Skill Builder — User's Guide and Skill

    The agent that builds your other agents. Describe a task you repeat and it hands you a finished skill folder.

    Coming soon
  • Mentor at Scale Blueprint

    Anne's playbook for mentoring more people without being in the room.

    Coming soon
  • The Claude Stack — A Preamble

    The setup that makes everything else work, before you build a thing.

    Coming soon
  • Words and Phrases AI Ruined (For Now)

    The giveaway words that make writing sound machine-made, and the ones to strip.

    Coming soon
← Home
Module 1

Chat vs Cowork

You'll have the Claude desktop app running — or a working fallback — and you'll know which surface to use for which kind of work.

There is technically one Claude — one brain in the middle. The web app and the desktop app are surfaces into that same brain. This module gets you onto the right surface for building.

Chat or Cowork

Chat is for questions and back-and-forth, like talking with an intelligent friend. Cowork is like having an employee — it can open folders on your computer, create files, and complete tasks on your behalf. Your business brain gets built in Cowork because Cowork writes files you keep.

How to Do This

  1. Download the desktop app at https://claude.ai/download and install it.
  2. Open the app and sign in with your existing Claude account.
  3. Find the tabs on the left and click Cowork.
  4. Leave Code alone for now. Cowork covers everything in these modules, and Claude Code is the more capable next step when you outgrow it.

If the Install Fails on Windows

This came up live in the workshop. If the installer keeps asking you to download again and the app never appears on your machine, skip it for today.

  1. Go to https://claude.ai in your browser and use Projects there.
  2. The brain-building conversation in Module 2 works in the web app too — you'll paste the same prompts into a Project. The file moves, like folders on your computer, wait until the desktop app works.
  3. Try again in a few days with a freshly downloaded installer. When it installs, Module 2 shows where your files live so you can move them over.

One Note on Models

New models arrive constantly and most of the noise around them is for people making videos, not people getting work done. The default model is fine. Heavier models complete harder tasks and spend more tokens — tokens are how usage is metered, so more tokens means more of your plan used. That's the entire decision.

Checkpoint

You can open the Cowork tab, or a project in the web app. That is the whole job of this module.

Replay Markers

  • ~14:00 Surfaces overview and chat vs Cowork
  • ~18:00 The Windows install fix, live

Times are close, not exact. Replay link coming soon

Resources

Module 4 puts you on your first skill. When you're ready to build them the way a team would, Skill Builder is the resource that takes you there.

Skill Builder — the agent that builds your other agents

Every craft gets written down so the next person does not start from scratch. Skill Builder is how you write down the way you work, once, so your Claude does it the same way every time — and the next skill gets easier to build than the last.

You describe a task you keep doing the same way, and it turns that into a reusable skill using a proven, repeatable method, checks the result against the five things that make skills fail, and hands you a finished skill folder.

It's built for any task you repeat — a morning brief, a follow-up, a proposal, a content pipeline. And fair warning, it won't build a skill for a one-time task, and it won't cram a whole workflow into one skill. If you describe something that is really three skills, it splits them and chains them. That is the method working, not a refusal.

How to Trigger It

Open a fresh conversation and say any of these, then describe the skill you want.

  • "Build a skill that…"
  • "I need a skill for…"
  • "Rebuild this skill"
  • "Is this skill any good"
  • "Help me build an agent that…"

What You Get Back

  1. The Scope. One clear job per skill. If you cannot say it in a sentence, it splits.
  2. The Trigger. The description is written first and tested against the phrases you use, so the skill fires when you need it and stays quiet when you don't.
  3. The Anatomy. The steps, the exact output format, how it chains to your other skills, and the gotchas it should avoid.
  4. The Check. It runs the skill against the five skill killers and fixes anything it catches.
  5. The Folder. A complete skill folder, ready to drop into your gallery and run.

What You Can Do With It

  • Turn a repeated move into a permanent one so you get the same quality without re-explaining.
  • Audit a skill you already have and have it fixed against the method.
  • Build a team of agents that chain together instead of a pile of one-off prompts.
  • Record the lesson — every time a skill gets something wrong, tell it to add the gotcha so it never repeats.

What Runs Before and After

Before. Nothing required — bring a task you repeat.

After. Whatever you build. The first skill shows you what to build next.

The Skill Builder Skill

This is the skill itself, ready to paste into your own gallery and run.

--- name: skill-builder version: 2.2.0 description: > Use when anyone needs to create, rebuild, audit, evaluate, or chain skills. Fires on "build a skill," "rebuild this skill," "is this skill any good," "create a skill for," or "I need a skill that." Walks through skill anatomy, checks against the 5 Skill Killers, and produces a complete skill folder. --- # Skill Builder — Skills Creator v2 How to build skills for any team, any workflow, any tool. ## The Scoping Rule One clear job per skill. If you cannot describe what the skill does in one sentence, it is probably two skills. ## The Build, In Order 1. Name and description — write the trigger first, loud and third-person. 2. Context required — every file the skill reads, full paths. 3. Instructions — numbered steps, tight where it counts, loose elsewhere. 4. Output format — show a literal template, do not describe it. 5. Works With — declare upstream, downstream, pairs-well-with, standalone. 6. Gotchas — capture every failure pattern. This is the highest-signal section. 7. Constraints — what NOT to do, specific to this skill. ## The 5 Skill Killers 1. Vague description. 2. Over-defined process. 3. Stating the obvious. 4. Missing gotcha section. 5. Monolithic blob over 500 lines. ## Constraints - Don't build skills that duplicate one already in your gallery. - Don't create skills for one-time tasks. - Every content-producing skill runs brand enforcement before output.

Take It Further

  • Which tasks do you repeat every week that you would hand to an employee on day one? Write them down — they become your first Cowork tasks in Module 4.
  • Which of those tasks would you NOT hand to a new employee on day one, and why? That list is your review checklist when Module 4 puts Claude on them.
← Home Next — Build Your Business Brain →
Module 2

Build Your Business Brain

You'll have a Cowork project with five context files Claude reads before it does anything for you.

The business brain is a folder of plain files on your computer. Build it once and every future task starts already briefed on your business. It's yours and it travels with you — refine it over time instead of rebuilding it.

The Five Files

  • About My Business
  • My Audience
  • Offers and Pricing
  • Brand Voice
  • Current Priorities

Sarah's template includes two optional additions, Messaging and Rules of Engagement — add those after the first five are solid. Short on time today? Build About My Business and Brand Voice first, then finish the other three in your next session.

How to Do This

  1. In the Cowork tab, click Projects — Projects lives inside Cowork — then Create new project. Create the project first — work started in a loose chat or task can end up disconnected from your Projects tab, which happened live in the workshop.
  2. Name it something like My Business Brain.
  3. Open Sarah's template page and copy the setup prompt. template page coming soon No link handy? Tell Claude — "Create a folder called Business Brain with five files named About My Business, My Audience, Offers and Pricing, Brand Voice, and Current Priorities, then interview me to fill the first one."
  4. Paste it into the project chat. Claude creates a folder on your computer with the five files inside.
  5. Copy the first section prompt, About My Business, and paste it in.
  6. Answer by voice — click the mic in the chat box. Talking it out gives Claude richer material than typing ever will. No mic showing? Type your answers instead.
  7. Let Claude interview you. When it writes the file, open it from the context pane on the right — Cowork's sidebar showing every file it's reading — and read it back. Correct anything that doesn't sound like you. Claude pulls from what it can find about you online, so check the file for things you never said.
  8. Repeat for each remaining section. Jot rough answers now and refine later — iteration is the whole method.

Working in the web app instead? Paste the same prompts into a Project there. Claude keeps your five sections in the conversation rather than a folder on your computer — when the desktop app works later, ask Cowork to write them into a folder.

Teach It Your Voice

  1. Open the tells-of-AI list — the words and phrases that make writing sound machine-made. list coming soon
  2. In the project chat, paste the link and say "Extract the words to avoid from this page and file them where they belong." Claude reads the page, picks the Brand Voice file, and adds them itself.
  3. For rules you want everywhere — not just this project — click your name in the bottom-left, open Settings, and add them as global instructions. Module 5 covers this in full.

Make It Portable

The five files are plain files on your computer, not locked inside Claude. One distinction before you copy anything — Cowork works from the folder on your computer. The Drive copy is your backup and your portability, never the working folder. That's why files landing in Drive appears under the fixes below.

  1. In the context pane on the right, click the folder to open its location on your computer.
  2. Copy the folder to Google Drive, or wherever you keep shared documents.
  3. Now any AI you choose can read the same context. If you change tools someday, your brain comes with you.

Where Things Went Sideways Live

Every one of these happened in the workshop, and every one has a fix.

  • The files landed in Google Drive instead of on your computer. Download the five files, put them in one folder on your desktop, then click the plus in the project chat and choose that folder.
  • Your project is missing from the Projects tab. You likely started in a task or chat instead of a project. Create a project, then attach your existing folder with the plus sign. Your work is safe — it lives in the folder, not the chat.
  • The files won't open in Notepad. Open them from Cowork's context pane instead, or install Visual Studio Code, which is free and reads them cleanly.
  • Claude says the workspace folder is empty. The project is pointed at the wrong folder. Click the plus, choose the folder with the five files in it, and open one to confirm your words are inside.

Checkpoint

Open each of the five files. If every one opens and reads like you wrote it, the brain is built.

Replay Markers

  • 26:11 Sarah drops the template prompts and the build begins
  • 26:00–1:10:00 The build, section by section, with live questions
  • ~1:10:00 The files-landed-in-Drive fix
  • ~1:39:00 The project-missing-from-Projects fix

Times are close, not exact. Replay link coming soon

Resources

The setup prompt and all section prompts live on Sarah's template page. template page coming soon

Teaching the AI your full writing style goes deeper than the tells list — the step-by-step guide is here. guide coming soon

Take It Further

  • Have someone interview you for the brain instead of self-reporting. In the AI Consulting Accelerator, pairs interview each other and pull out answers neither would have written alone. Who would you ask?
  • Open an incognito browser and ask any AI chat tool what it knows about you and your business. What's missing or wrong is your next visibility project — the agents can only find what's published.
← Back Next — Make Your First Lead Magnet →
Module 3

Make Your First Lead Magnet

You'll have one draft lead magnet built from your business brain — and it will sound like you, because the brain did the briefing.

The brain pays off the first time you make something from it. The workshop used a lead magnet as the example, but the same steps produce social posts or a one-pager just as well.

Draft It Inside the Project

How to Do This

  1. Open your business brain project in Cowork.
  2. Ask for the lead magnet in plain language. "Create a lead magnet checklist for my audience, drawing on everything in this folder." Claude already has your offers and your voice in context — that's the point of Module 2.
  3. Read the draft against your Brand Voice file. Anything that doesn't sound like you goes back with a specific note.
  4. Iterate freely. You didn't pour days into this draft, so regenerating costs you nothing but a prompt. Put it out, get feedback, and tweak — done is so much better than perfect.

Go Interactive with Live Artifacts

A flat PDF is a fine lead magnet. An interactive one — a quiz that scores the reader, or a dashboard you keep — is the next level, and Live Artifacts builds those.

How to Do This

  1. Find Live Artifacts in the desktop app's left-hand navigation — the same place you found Cowork — and open it.
  2. Create a new artifact.
  3. Click the plus at the bottom, choose Add folder, and pick your business brain folder.
  4. Confirm the folder appears in the context pane on the right — that pane always shows what Claude is reading.
  5. Ask for the interactive version. Everything it creates now draws on your audience and your goals.

Checkpoint

Read your draft next to your Brand Voice file and find three phrases that sound like how you talk. Anything that doesn't sound like you goes back for another pass.

Replay Markers

  • ~50:00 The first lead magnet built from the brain
  • ~1:33:00 Live Artifacts walkthrough

Times are close, not exact. Replay link coming soon

Take It Further

  • What would you publish this week if the flat version were good enough? It probably is — ship it and let the interactive version be round two.
  • What's the tenfold version — a quiz that scores the reader and sends you their answers, so the lead magnet also qualifies the lead?
← Back Next — Connectors and Skills →
Module 4

Connectors and Skills

You'll have one connector live and one skill drafted from a process you already run.

Three plain definitions, because the gatekeeping around these words is worse than the words. A connector gives Cowork access to a tool you use, like your calendar or your CRM. A skill is an SOP — numbered steps for one specific job. An agent is a skill running on a schedule without you kicking it off. That's it. Anyone who runs a business already thinks this way.

Connect Your Tools

How to Do This

  1. In Cowork, open Customize on the left, then Connectors.
  2. Connect Google first if you live in Gmail and Calendar — most tasks touch one of them.
  3. Browse the rest and connect only what you use weekly. Each connector is access you're granting, so add them as the work demands, not all at once.
  4. If your tool has no native connector — GoHighLevel came up live — ask Claude in the chat to set up a custom connector. It guides you through the link and the authentication. Some tools don't offer a compatible connection yet — if Claude says it can't be done, move to the next tool on your list.

Build a Skill from an SOP You Already Have

How to Do This

  1. Pick one process you repeat the same way every time, like your meeting follow-up or your invoice chase.
  2. In the project chat, say "I want to create a skill" and describe the steps. The built-in skill creator handles the format. Anne's skill-builder prompt is the more meticulous route once you're hooked. prompt coming soon
  3. Run the skill on a live example and check the output before you trust it. To run it, type a slash in the chat to see your skills and pick it — or just describe the job, and Claude pulls in the right skill on its own. If the result is off, the fix is in the instructions — tighten one step and run it again.

One safety rule. Never install a skill from a stranger on the internet. A skill is instructions Claude follows with access to your files and your connected accounts, and a bad one can hide steps you'd never approve. You don't need anyone else's — describe yours to Claude and build it yourself.

Schedule It — This Is the Agent Part

This section can wait for a second sitting — come back when a task has earned a schedule.

How to Do This

  1. Open your business brain project. The tasks and schedules area sits alongside the project chat — that's where you create a task. Name it and write the instructions, then set the frequency.
  2. The workshop example was a daily brief — read my calendar and inbox, deliver a morning summary to me.
  3. Keep schedules to what you'll act on. Scheduled runs spend tokens whether you read the output or not, so anything optional stays on manual.

Checkpoint

One connector authenticated. One skill drafted from your SOP and tested on a live example.

Replay Markers

  • ~1:33:30 Scheduled tasks and the daily brief
  • ~1:44:00 Connectors, skills, and plugins walkthrough
  • ~2:11:00 Anne's skill-builder prompt

Times are close, not exact. Replay link coming soon

Take It Further

  • If a capable assistant started Monday, which job would you hand over first? That's your first scheduled task — and you are the boss accountable for what it produces.
  • Ask Claude directly, "What access or resources would make you more useful to this business?" and see what it asks for. You'll learn what your setup is missing faster than any tutorial.
← Back Next — Stay Portable, Stay Safe →
Module 5

Stay Portable, Stay Safe

You'll know exactly what leaves your machine and what your exit looks like if you ever switch tools.

Independence closed the workshop and it closes this series. Your business brain is a folder of files you keep — no platform decides whether you get to take it with you.

Keep Your Exit Open

How to Do This

  1. Keep a copy of the brain folder in Google Drive, as set up in Module 2.
  2. Update the Current Priorities file on a rhythm — weekly or monthly, whatever matches how fast your goals move. The other four files change only when the business does.
  3. If you switch tools someday, point the new AI at the same folder. Nothing gets rebuilt.

Know What Leaves Your Machine

How to Do This

  1. Understand the boundary. The project folder controls what Claude can touch on your computer — it does not make the content private. Anything you type or upload — and anything you let Claude read — goes to Anthropic.
  2. Write down what never enters a hosted model. Client confidential data was the live example in the workshop. A line you've decided in advance beats a judgment call made mid-task.
  3. For data that can't leave your machine at all, locally hosted models exist — Ollama was the one named in the workshop. They run on your computer and send nothing to a third party.

Set Your Global Rules

Folder rules live in the project. Personal rules live in Settings. Your vacation planning doesn't need your brand voice.

How to Do This

  1. Click your name in the bottom-left corner of the desktop app and open Settings.
  2. Add instructions for Claude that apply everywhere — your no-go words, your formatting preferences.
  3. In that same Settings area there's a second instructions box labeled for Cowork, below the general instructions for Claude. Use it for how Cowork should behave across every project, like asking before it deletes anything.

Checkpoint

You can point to where your five files live outside Claude, and you can say out loud what never goes into a hosted model.

Replay Markers

  • ~1:38:00 Drive folders and portability
  • ~1:53:00 The data security conversation

Times are close, not exact. Replay link coming soon

Resources

The full writing-style guide pairs well with your global instructions. guide coming soon

Take It Further

  • What would break in your business if this account disappeared tomorrow? Whatever your answer is, get it into files you keep.
  • Ask Claude to draft a one-page AI data policy from your Rules of Engagement file — then edit it yourself, because the accountable human in this setup is you.
← Back Finish — Back to Home →

Claude Girl Summer

Four live workshops, one summer of building. Every session is hands-on, and you leave each one with something made.

Tie-Dye

Build Your Business Brain

Everything comes out in your colors. Five context files Claude reads before every task — built live, kept forever.

Held June 11 · modules on this site
Talent Show

Claude and Sales

Your offer takes the stage. Follow-up that goes out on time, a pipeline you can see.

Date coming soon
Stargazing

Claude and Business Intelligence

Find the constellations in your numbers. Dashboards and data visualization, built inside the workspaces where you already work.

Date coming soon
Arts and Crafts

Cool Projects, No Syllabus

A run of builds you'd never file under work — and the same skills go straight back into your business.

Date coming soon

Come as a Day Camper — any session à la carte — or go Sleepaway and take all four for the price of three.

Gather With Us →
← Home

Connect and Get Unstuck

Reach Anne and Sarah any time you hit a wall.

Connect with Anne Connect with Sarah
CREATE 2026

The Human-Centered AI Conference for Women. The whole community in one place.

Salt Lake City · October 16–18, 2026

Gather With Us →

Built by Anne Murphy and the matriarchal agentic team at She Leads AI

© 2026 She Leads AI · hello@sheleadsai.ai