Write something
Pinned
24d •
Start here: onboard Claude, then show us the before and after
Welcome. This community is about one thing: getting Claude Cowork to work like a trained employee instead of a new hire you re-explain everything to every chat. Here is how to get going. 1. Grab the free rules file first. Open the Classroom and take Give Claude Your Rules, two short lessons, about 15 minutes. You fill in a few blanks, paste one file into Claude, and every chat follows your rules from then on. Every member has it. 2. Next, take Pick the Right Claude. Twelve short lessons, about 45 minutes. It settles which model and effort level to use for each job. Every member has it. 3. Post once under General discussion: what your business does, and the one job you would hand a trained employee first. That is the job we point your setup at. 4. When you want the setup, upgrade to Premium and take the 30-minute path in Onboard Claude. Lessons 1.1 and 1.2 install Cowork and make your folder. Lesson 10.1 makes the project and connects one tool, 10.2 is the paste (about a dozen questions, then tap Build it), 10.3 is the three things left after it runs, and 10.5 is what to do once you are done. 5. Run the before-and-after test in lesson 7.5. Same request, once in an incognito chat and once in your new setup. Post the pair here under Before and after, with client names, prices, and anything private blacked out. It is the fastest way to see what you built, and it helps the next person decide to build theirs. 6. Come back for the middle modules when you want to understand what got built. Each lesson is short, and most have a download you can keep. Three house rules: - Be specific. "My skill will not load" gets a guess. "My skill will not load, here is the line that says when it should run" gets a fix. - Post your setups, your rules, and your fixes, with anything private blacked out. A rule that saved you an hour will save someone else one too. - No pitching. This is a workshop, not a feed. If you get stuck, post under Stuck? Ask here with the lesson number and what your screen showed, and we work it out in the thread.
0
0
2d •
Give the job and let it ask
The instinct with a new tool is to over-brief. You type everything you can think of, in case it helps, and half of it turns out to be wrong or beside the point. The setup flips that. You give the job, and Claude asks the questions the files cannot answer, one at a time, as tappable choices with the recommended option first. A handful of questions on a real job is the shape to expect. Two minutes of tapping is cheaper than an hour of reviewing the wrong build. And when it asks something the folder already answers, that is a gap in the folder. Answer it, then add the answer to the file that should have held it, and the question does not come back. How many questions did Claude ask on your last real job?
0
0
3d •
Brief a job in seven lines
A one-line request is fine for a reply or a lookup. For anything with more than one step, the way you brief the job decides the quality of what comes back. The handoff prompt is the brief a good manager gives a good employee, and it takes two minutes to fill in: 1. Job, in one sentence. 2. Why, and who will see it. 3. Inputs, meaning the files, links, and tools to pull from. 4. Output, the exact thing you want back. 5. Format, including the file types you can open. 6. Rules that matter here. 7. Done means, which is how you will judge it. It ends with one line. Run the front gate, ask me what the files cannot answer, then recap and wait for my go. That last line is what keeps a big job from starting on a guess. What is the next job on your list that deserves a seven-line brief?
0
0
4d •
Friday pairs, week three
The thread for this week's before-and-after pairs. One real job, run once in an incognito chat and once inside your setup, with the same one-line request. Post both with anything private blacked out. If you have posted a pair before, run a different kind of job this time. A quote instead of a reply, or a weekly update instead of a quote. Each job type shows a different part of the setup working, or not working, which is the point. And if the after came back wrong somewhere, post that too. A wrong after is the fastest route to a fix, because the thread can usually spot which file is missing what. What did you run this week?
0
0
5d •
A skill that never loads unless you name it
You built a skill, it works when you ask for it by name, and Claude never reaches for it on its own. The cause is almost always the description. Claude sees the name and description of every skill you have turned on. When a request matches a description, it opens that skill. So the description has to carry the phrases you would say out loud, like "prep me for," "pull the numbers," or "does this sound like me." If it describes the job in words you never use, it will not fire. The fix is to rewrite the description with your own phrases, keep it under 200 characters, reinstall, and test it with three requests worded the way you talk. What is a job you ask for often enough that it should be a skill by now?
0
0
1-21 of 21
skool.com/teach-claude-your-business
Onboard Claude Cowork like a new hire and it works like a trained employee: your rules, your voice, files you can open, checked before it says done.
Powered by