How It Works in Claude

Eight of the eleven are. The name is the friendly label, and the skill is the actual recipe.

A skill is how to do one job, and it works anywhere in your Claude. A project is a shared workspace with its own instructions, files and chats. The studio adds the menu, the shared files and the rules every job follows.

One project per show would bring back the tab-switching this is meant to end. The podcast jobs and the shared files are the same for LHS and LHSFT, so the studio asks which show when it isn't clear. Growth Studio is separate because the certification, the new site and lead magnets use different files.

No. Claude shows their names in the text, like "Eddie here." The artwork lives on this site and can be used as page icons and covers in your Notion.

Yes. The names are in the project instructions and not in the skills, so a rename is a quick edit and no skill needs republishing.

No. Say hi and pick a number, or write what you need in plain words. Short commands like "card E571" work too if you end up preferring them.

Use one chat per episode, so each agent can see the transcript and Eddie's card. If a chat gets long, start a new one and paste in the card. Don't count on one chat remembering another. Anything that needs to carry over belongs in the project files.

Yes. Each person has their own chats. Usage limits are per person, so one person hitting a limit doesn't affect anyone else.

No. Every job ends with a package and the line "Nothing was published or sent." You paste it into Megaphone, Airtable, YouTube Studio or wherever it goes, the same way you do today.

Nothing passes through Claude by itself. Whoever runs a job copies the package to the next person, in the places you already use. So Hayley sends India the keyword file from her episode card, and Hannah gets her social set the same way she gets work today. Where episodes are tracked, Monday or Notion, is still Hayley's call.

• The edited video's transcript with timestamps. In YouTube Studio, go to Subtitles, open the auto-generated English track and download it. The editor's export works too.
• One line with the guest's name or "solo," the video's length, and anything different from usual.
• Hayley's keyword file, if she ran the card. It's optional.

• The session notes, Lisa's voice memo or a transcript. Any of them works.
• The attendee list if you have one, with only their name, license and state, and what they came for. Leave out anything else.
• The session date, if the notes don't show it.

Lisa still has to say whether a session transcript may be used, because the session page says it isn't recorded. Until she does, use notes or her voice memo. Program facts and links come from files inside the skill, so that's why tuition, dates and the enrollment link are needed once, up front.

Not to start. They get the finished package from whoever runs the job, in the place they already work. India runs her own YouTube job, so she'll use the studio directly.

You say so, or it asks. It won't guess, because the two shows have different audiences, keywords and rules.

Not yet. It's written for the LHS channel, and it would point LHSFT viewers to the wrong next step. Max adds an LHSFT version before India uses it for those.

Plan on a computer, in a browser or the Claude desktop app. The phone app hasn't been tested with these skills.

Growth Studio, once it's built after her lead magnets meeting. Until then, the recap and page brief skills can run in an ordinary chat once Lisa publishes them.

Claude has scheduled tasks that run in the cloud with no computer on, and a project can hold its own. Rocket also needs a way to read each number source. Only Semrush is connected so far. Whether this is on for your account hasn't been checked, so it's still a plan.

Nothing. Her projects stay exactly as they are and keep working while the studio is tested. When she's happy with the studio, she archives them herself, one at a time. Archiving keeps everything, and a project can be unarchived.

No. They stay in the old projects, where you can still read them.

That's the goal, and it's why her live projects were copied and read. Eddie has been rebuilt to her current title and description standard, and four details are waiting on her answers. Her project instructions set the standard for each job, so each skill gets compared with them before it goes live. Content Production Command Center still has to be shared before Blog Marley and Ewe-Tube can be compared.

A shorter list than you have now, with duplicates removed. Hayley confirms it before anything is uploaded. Right now one project holds three copies of the same keyword sheet. The draft list is in the instructions section below.

Other team members can't. Chats in a shared project stay private unless you share one yourself.

There's one exception to know about. A Primary Owner can export the organization's data, and that export includes conversations.

Not by default on a commercial plan like Team. The thumbs up and down buttons are the exception. Using one sends that whole conversation to Anthropic as feedback, stored for up to 5 years, and it may be used for training. So skip those buttons, and tell Max what went wrong instead. An owner can turn them off under Organization settings, then Data and privacy, using the "Rate chats" setting.

No. These studios are for podcast and marketing work only. Client or patient information stays out of them, and the instructions tell Claude to stop if someone pastes any. Whether your Claude plan is set up for health information hasn't been checked, so treat it as not.

Tell it in the chat and it will fix that draft. If it makes the same mistake twice, tell Max, so the skill itself gets fixed and the mistake doesn't come back.

Go to Customize, then Skills, and check that it's switched on under Organization skills. If it isn't listed, open the Your organization tab and install it. If it's on and still failing, the studio will name the skill and stop instead of guessing. Send that to Max.

Only Hayley and Lisa can edit them. The approved copy is kept outside Claude, so it can be pasted back in.

Tell Max what changed. Max updates and tests the skill, then Lisa uploads the new version in Organization settings, and everyone has it.

Everything stays in your account. Lisa publishes the skills, Hayley creates the project, and the instructions are plain text anyone with edit access can change.

Projects, skills and sharing are part of your Team plan. Each person who runs a job needs their own seat. Semrush needs a plan that includes its connector. If someone reaches their limit, an owner can choose to buy usage credits. Long transcripts use more of a person's allowance, and Settings, then Usage, shows where each person stands.

• Now, the team names, the menu and the rules in the draft instructions.
• Before each skill goes live, its real output, marked yes or no with a reason. Only you mark what sounds like you.
• Later, who signs off on titles and descriptions after the test. That's still your decision.

Her time goes to three things.

• The title test, marking 10 past episodes yes or no, with a reason.
• Reviewing each skill's work before it goes live.
• Uploading each approved skill, which takes a few minutes.

Setting up the project on a call with Max, answering the four Episode Card checks, sharing the last project, and running one real episode start to finish.

• Hayley answers the Episode Card checks, and Lisa uploads the new version.
• Lisa does the title test.
• Hayley and Max create the studio.
• Max tests it from a team member's seat.
• Hayley runs one real episode.
• The other skills go live one at a time, as each passes Lisa's review.
• Growth Studio follows Mandi's lead magnets meeting.