Learn Claude in Four HoursRead this on victoriaprew.com​ Read time: 3 minutes Hey! Most people are using the most powerful tool they own like a search engine. They type a question, they get a generic answer, and they decide the whole thing is overhyped. I've created a free worksheet that will get you ahead of 90% of people using Claude. You need to configure it once. Four steps, about an hour each, and you could do all of it this weekend. TODAY AT A GLANCE
[step one] Build your About Me docOne hour This is the file that decides whether your output sounds like you or like an AI model. Everything after it is plumbing.
Be specific. “Grow the business” gives you nothing. “Two million to three and a half million in recurring revenue by Q4, and the bottleneck is churn at month four” changes every answer after it. [step two] Set up your ProjectsOne hour A Project holds two things: knowledge, meaning your files, and custom instructions. Both load at the start of every chat inside it.
The mistake: when output drifts, people add more files. Remove them instead. [step three] Connect your appsOne hour MCP lets Claude connect to your tools and read your data directly, instead of you pasting everything in.
The mistake: skipping the permission setting because you’re moving fast. Read alone gives you most of the value and almost none of the risk. [step four] Add Skills, then build one thingOne hour. Give this one the most time. A Skill’s description tells Claude when it’s relevant, so write it around the task and the conditions that should trigger it, not around yourself.
Most people stop at step three. This is where Claude starts doing repeatable work for you. [then build your daily brief]] One scheduled job that replaces the first forty minutes of your day. Fifteen minutes to set up. Here’s the prompt: “Set this up as a scheduled task that runs on weekdays at 7am. Using my calendar, Gmail and connected task manager: What’s on today? Flag anything I haven’t prepared for. Who’s waiting on a reply from me? Order by how overdue they are. What moved yesterday, and what didn’t? What’s one thing on today’s list I could drop without consequence? Keep it under 300 words. Bullets only, no preamble. If a section has nothing useful to report, leave it out. Never pad the brief.” Give it a week before you change anything. The first few will be wrong and it tightens fast once you tell it what you didn’t want. [the guide] I’ve put the whole thing into a free guide: the 25 questions with useless and useful answers side by side, weak and strong Project instructions to copy, the test prompts for every connector, the Skill and daily brief prompts, the eight ways this goes wrong with the fix for each, and a checklist at the end.
Have a good week, Victoria |
Victoria Prew is an award-winning entrepreneur and CEO who has raised over $10M in venture capital funding (when 2% of VC goes to female founders), scaling tech-first marketplace HURR to become a UK revenue leader.