profile

VICTORIA PREW

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.

Nov 02 • 3 min read

🔊 Learn Claude in Four Hours


[thriving in chaos] [victoria prew]

Learn Claude in Four Hours

Read 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

  • Generic output is a context problem, not a model problem.
  • Four steps fix it: About Me doc, Projects, connected apps, Skills.

[step one]

Build your About Me doc

One hour

This is the file that decides whether your output sounds like you or like an AI model. Everything after it is plumbing.

  • Don’t write it yourself. You’ll be vague and modest about your own work without noticing.
  • Ask Claude to interview you instead. 25 questions, one at a time, covering five areas: what you do, what you’re trying to do, how you want to be talked to, your tone of voice, and how you work.
  • The questions on how you want to be talked to carry the most weight. How blunt should it be when something is bad? Should it ask first, or have a go? What should it never do?
  • Dictate your answers rather than typing. Three times the detail in half the time.
  • Save it as an .md file and upload it into every Project’s knowledge.

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 Projects

One hour

A Project holds two things: knowledge, meaning your files, and custom instructions. Both load at the start of every chat inside it.

  • Four to six Projects: work, business, content, health, family, money.
  • Write the instructions properly. A clear goal with a number, where you are now, what good output looks like, a quality bar, and an explicit never list. Mine says never use an em dash.
  • Load your About Me doc into each one.
  • Cap the knowledge at five files.

The mistake: when output drifts, people add more files. Remove them instead.


[step three]

Connect your apps

One hour

MCP lets Claude connect to your tools and read your data directly, instead of you pasting everything in.

  • Start with four: Gmail, Slack, Google Calendar, Google Drive. You can also connect Canva, Figma, Granola, Notion, GitHub and Zoom.
  • Set the permissions properly. Read access open. Write access, meaning anything that sends, posts, deletes or pays, set to ask me first.
  • Test each one with a real question. “Summarise my emails” is weak. “Using my Gmail, find every thread from the last seven days where someone is waiting on me, grouped by how overdue” is strong.
  • Name the connector in the prompt. “Using my Gmail” routes it. “Check my email” often doesn’t.

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 thing

One 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.

  • Switch on the built-in Skills: documents, spreadsheets, slides, PDF.
  • Use skill-creator to turn a task you repeat weekly into a reusable Skill. It interviews you on how you do it now, then writes and installs it.

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.


Read next ...