Start Here
Why your first session feels generic
Cowork is the agentic mode in the Claude desktop app. It's not a chatbot you ask questions. It's an employee that reads your files, runs multi-step work, and finishes real deliverables on its own. But like any new hire, on day one it knows nothing about you. Give it a vague task and it guesses. Onboard it properly and it outperforms people you'd pay six figures.
I'm not a developer. Zero coding background. So everything in here is point-and-click and copy-paste. No terminal, no code, nothing scary.
One honest note up front, because I don't do bait-and-switch: Cowork is a paid feature inside the Claude desktop app on Pro or Max. It's desktop only. macOS or Windows, not the browser, not your phone. If you don't have the app yet, grab it at claude.com/download. If you're already on Pro, you're ready right now.
What you'll build
- Connect your tools (5 min)
- Build your context files (10 min)
- Set your global instructions (5 min)
- Install your first 5 skills (5 min)
- Create your first scheduled task (5 min)
Make it through all five and there's a bonus section at the end most people never find. It's the move that makes your setup get smarter on its own every week. Don't skip to it. It only works once the first five are done.
Part 1 · 5 min
Connect your tools
Do this before you type a single real prompt. Almost everyone skips it and then wonders why Claude feels generic.
Open the Claude desktop app and switch the mode at the top from Chat to Cowork. Then find the connectors (the + near the message box, or Settings → Connectors) and plug in the apps you actually live in:
- Google Workspace (Drive, Gmail, Calendar). Non-negotiable. Most of your real context lives here.
- Slack or Teams. If your team talks there, Claude needs to see it to understand your work.
- Notion, Asana, Linear, or Monday. Wherever your projects and docs actually live.
- Zoom. Claude can pull meeting context and recordings.
Each one runs a quick sign-in once, then Claude can read and act on it.
Why this goes first: in Part 2, Claude is going to write your setup files for you by reading your existing docs. If your tools aren't connected yet, it has nothing to pull from and you're stuck typing everything by hand. Connect first, configure second.
Quick test: ask Claude to find a recent document in your Drive. If it finds it, you're good. Move on.
Part 2 · 10 min
Build your context files
Context files are documents Claude reads at the start of every session. They're how it knows who you are without you re-explaining yourself every single time. This is the difference between a chatbot and an assistant that actually sounds like you.
You need three:
aboutme.md: who you are, what you do, who you serve, the people and tools around you.brand-voice.md: how you write and want to sound.working-preferences.md: how you want Claude to work with you.
Here's the part that feels like cheating: you don't write these. Claude does. You paste one prompt, it turns into a sharp onboarding interviewer, drills you with questions, and then writes all three files itself.
Do this:
- Make a new folder on your desktop. Call it
Claude Cowork. - Drag it into the Cowork window. When Claude asks for access, click Allow.
- Paste the prompt below and press enter.
- Answer its questions in detail. This is the whole game. Lazy answers get you a lazy assistant. Specific answers get you one that sounds like you and knows your business.
Copy-paste prompt: The Context File Builder
You're going to help me build the "operating system" for working with you inside this
folder. The goal: a set of context files you read at the start of every task so you
always know who I am, how I work, how I write, and how I want things done.
Work in two phases. Do not skip ahead.
## PHASE 1: Interview me
Interview me to understand me deeply enough to do my work the way I'd do it. Rules
for the interview:
- Ask 2-3 questions at a time, not a giant wall. Wait for my answers before moving on.
- Go DEEP. When an answer is vague, ask a follow-up until it's specific and usable.
- Use plain language. No jargon.
- Keep going until you genuinely understand me, not until you've hit a quota.
Cover all of these areas, roughly in this order:
1. IDENTITY: My name, my role, my company or business, and what I actually do all day
in one honest sentence.
2. RESPONSIBILITIES: The main things I'm on the hook for. What lands on my plate that
nobody else can do.
3. GOALS: What I'm trying to make happen this quarter and this year. What "winning"
looks like for me right now.
4. THE REPETITIVE WORK: The tasks I do over and over that I'd hand off first. Be
specific: ask me to walk you through one of them start to finish.
5. VOICE & WRITING: How I want things to sound when you write as me or for me. Ask me
to PASTE 1-3 samples of writing I'm proud of, then tell me back the patterns you
notice (sentence length, tone, words I use, words I'd never use) and confirm them
with me.
6. TOOLS & STACK: The apps, platforms, and tools I work in every day.
7. PEOPLE: Who I work with, who I report to, who I serve, and how I refer to them.
8. WHAT "GOOD" LOOKS LIKE: Show me an example of a deliverable I love and one I hate,
or describe the difference, so you know the bar.
9. PET PEEVES & ANTI-PATTERNS: The things I never want you to do. Phrases I hate,
formats I hate, behaviors that drive me up the wall.
If I give you a short answer on something that matters, push back gently and ask for
the detail. Don't let me off the hook on voice or on the repetitive work. Those two
matter most.
## PHASE 2: Build the files
When you have enough, tell me you're ready to build, and then create this exact
structure inside this folder:
Claude Cowork/
README.md
ABOUT ME/
aboutme.md
brand-voice.md
working-preferences.md
OUTPUTS/
TEMPLATES/
Write the files like this:
- ABOUT ME/aboutme.md: the full picture of me. Identity, responsibilities, goals,
the people I work with, my tools.
- ABOUT ME/brand-voice.md: exactly how I write and want to sound, WITH the patterns you
pulled from my samples and a couple of do / don't examples.
- ABOUT ME/working-preferences.md: how I want you to work. Formatting, how to handle
uncertainty, what to ask before doing, my pet peeves and hard rules.
- README.md: a short plain-English explanation of how this folder works so future-me
(and future-you) can find everything.
- Leave OUTPUTS and TEMPLATES empty for now.
Everything you write must match my voice and the rules above. When you're done, give me
a one-paragraph summary of what's in each file. When it finishes, open the folder and read what it wrote. Fix anything it got wrong. You now have a second brain Claude reads on every task.
The shortcut most people miss: if you connected Google Drive in Part 1, tell Claude to scan your existing docs, bios, and about pages while it interviews you. It'll draft 80% of this from stuff you already wrote. You just edit.
Part 3 · 5 min
Set your global instructions
Your context files live in one folder. But what about the sessions where you don't open that folder? That's what global instructions are for.
Global instructions run in every session, before you select anything. Think of it as the executive brief Claude reads before it does a single thing. Your name, your business, how you work, and the rules it doesn't get to break.
Do this:
- Go to Settings → Cowork → Global instructions → Edit
- Delete anything in the box
- Paste the template below and fill in the
[bracketed]parts so they're actually about you - Click Save
You can also just ask Claude to write this for you: "Read my ABOUT ME files and condense them into an 800-word global instructions brief using this structure." Then paste what it gives you.
Copy-paste template: Global Instructions
# Who I am My name is [your name]. I'm a [your role] at [your company / "myself"]. I use Cowork to [the main outcome you want, e.g. "produce client deliverables, draft content, and run my weekly admin"]. # How I work - Tone: [how you want Claude to sound, e.g. "direct, plain, no corporate jargon"]. - Format: lead with the answer, then the detail. Short sentences over long ones. - When you're unsure what I want, ASK me one clear question instead of guessing. - When you make an assumption to keep moving, say so at the top of your reply. # Output defaults - Emails: short, bullet points, no fluff. - Content: paragraphs in my voice. - Research: tables or clear lists, sources noted. # Voice (the 3-4 things that matter most) - [e.g. "Direct and blunt, never corporate."] - [e.g. "Short sentences. Specifics over vague claims."] - [e.g. "Never use the words: synergy, leverage, unlock."] # Key business context [What I'm working on right now. What matters most this quarter.] # Rules you don't break - Never delete, overwrite, or move a file without asking me first. - Never invent a fact, a number, or a source. If you don't know, say so. - Keep a one-line note of what you did at the end of any task that changed files.
Save it, and every new session starts with Claude already knowing your name, your business, your voice, and your rules. No more "I'm [name], I run a company called..." ever again.
Part 4 · 5 min
Install (and build) your first 5 skills
Skills are saved playbooks that turn Claude from a general assistant into a specialist. Without them, Claude can chat. With them, it can research a prospect, draft content in your voice, prep you for a meeting, or run a multi-step workflow end to end without you re-explaining it.
Most guides tell you to go dig through a marketplace and hope something fits. Here's the better move: have Claude build the exact skills your work needs, tuned to how you actually do things. Anthropic ships a skill for this called Skill Creator. It interviews you about a task and writes the skill file for you. No code, no folders, nothing to learn.
First, install Skill Creator on desktop:
- In the Claude desktop app, start a new Cowork conversation.
- Type
/in the message box to open the skill menu. - Browse to Skill Creator and click install.
One-time setup: skills need "Code execution and file creation" turned on in Settings → Capabilities. Every skill you build from here shows up in that same / menu, and Claude auto-loads the right one when it's relevant.
Now let Claude find your quick wins and build them. Paste this prompt. It interviews you about your week, ranks your repetitive tasks by how much time each one saves, then uses Skill Creator to build your top 5, one at a time.
Copy-paste prompt: The Skill Finder + Builder
I want you to help me find and build my first Claude Skills using the Skill Creator skill. A Skill is a saved playbook you reuse without me re-explaining it. The goal is to build the 5 that will save me the most time. Work in three phases. Do not skip ahead. ## PHASE 1: Interview me Ask me 2-3 questions at a time, wait for my answers, and dig deeper when an answer is vague. You're hunting for the repetitive work in my week that's worth automating. Cover: - The tasks I do every day or every week, start to finish. - The work I procrastinate on or forget until it's too late. - Anything I've had to explain to you (or a coworker) more than once. - The format my outputs usually take: emails, reports, posts, research, etc. Ask me to walk you through one or two of these tasks step by step, exactly how I do them today. Use plain language. No jargon. ## PHASE 2: Find the quick wins Once you understand my work, rank my repetitive tasks by payoff. Score each on: - How often I do it (daily beats monthly). - How much time it eats each time. - How repeatable and rule-based it is (the more mechanical, the better it works as a Skill). Give me a short ranked table, then recommend the top 5 to turn into Skills first and tell me in one line why each one made the cut. ## PHASE 3: Build them with Skill Creator For each of the 5, use the Skill Creator skill to build it. Follow its process: identify the task, extract exactly how I do it today, OPTIMIZE it into a better version before writing (ask me what a better version would look like, don't skip this), then write the Skill and save it. Build one at a time. After each, tell me the exact name to call it by next time, then move to the next one. Start with Phase 1 now. Just the first 2-3 questions.
Answer its questions like you mean it. The tasks you name in that interview become skills you'll lean on every week for as long as you run Claude. Fewer skills you actually use beats a giant list you ignore.
Want to grab a few ready-made ones too? There are great pre-built skills you can install straight from that same / menu. I broke down the five I'd hand anyone in 5 Claude Skills Everyone Should Install, and the full install-and-build playbook lives in The Complete Claude Skills Guide.
Part 5 · 5 min
Create your first scheduled task
This is where Cowork stops being an assistant and becomes an employee.
Scheduled tasks run automatically on a schedule you set. No prompting. Claude does the work and delivers the result while you're doing something else. Start with one:
- Morning briefing (weekdays, 8 AM): check inbox for anything urgent, scan today's calendar, list your top 3 priorities.
- Weekly recap (Fridays, 4 PM): summarize what got done, flag what's overdue, highlight the wins.
- Meeting prep (30 min before any call): pull attendee context, check prior history, give you 3 talking points.
Do this: find scheduled tasks in Cowork, set a plain-language schedule, and write a specific prompt. This part matters more than the schedule. "Summarize my inbox" gives you generic mush. This gives you something you'll actually use:
Copy-paste prompt: Morning Briefing Task
Check my Gmail for unread messages from clients. Flag anything that mentions a deadline or needs a response today. List them by priority, with a one-line summary and the sender for each. If nothing's urgent, just say "all clear."
Want more ideas? Ask yourself three questions:
- What do I do every day or week that's repetitive?
- What do I always forget until it's too late?
- What would save me the most time if it happened automatically?
Every answer is a scheduled task waiting to be built.
The Full Setup
Start to finish, in 30 minutes
- Connect tools (5 min): Google Workspace plus your core stack
- Build context files (10 min): let Claude interview you and write them
- Set global instructions (5 min): the always-on brief
- Install 5 skills (5 min): match your most repetitive tasks
- Create your first scheduled task (5 min): start with a morning briefing
Thirty minutes. Claude goes from "generic chatbot" to "knows your business, your voice, your tools, and runs tasks while you sleep."
The people who get the most out of Cowork aren't the ones with the most skills installed. They're the ones who spent 30 minutes on setup. You just did.
Now the part most people never get to.
🔓 Bonus: Unlocked
The self-improving setup
You finished all five. Here's the move that separates people who use Claude from people whose Claude quietly gets better every single week without them managing it.
It's built on one idea: anything you do twice should become a skill. Most people never turn that into a habit because remembering to build skills is its own chore. So you make Claude do it for you.
Step 1: Add this to your Global Instructions (paste it at the bottom of the box from Part 3):
Copy-paste add-on: Get Smarter Over Time
# Get smarter over time - Whenever I ask you to do something that has a clear, repeatable shape, notice it. After you finish, ask me: "Want me to turn this into a Skill so you never have to explain it again?" - If I say yes, write the Skill, save it, and tell me the name to call it by next time. - Once a week, if you spot a task I've done more than once, suggest turning it into a Skill or a scheduled task on your own.
Now Claude actively hunts for repetitive work and offers to automate it. Every week your setup gets a little sharper and you didn't lift a finger. (Skills need "Code execution and file creation" turned on in Settings → Capabilities first.)
Step 2: Run a one-week calibration. Your first week won't be perfect. The morning briefing will miss something. The voice won't be exact. That's not a bug, it's the point. Every time Claude gets something wrong, tell it right then:
- "That email was too formal. Match the samples in brand-voice.md."
- "The morning briefing is too long. Cut it to 5 bullets max."
- "Save this format as a template so you reuse it."
By the end of week one you'll have made a handful of tiny edits. By week two, it feels like Claude has worked with you for months.
That's the secret. Not more skills. A setup that fixes and upgrades itself while you go do the actual work. Now go run a real task and watch Claude show up already knowing what to do.
Work with Me
Want me on your problem for an hour?
Book a 1:1 call and we build the fix live — the workflow you want automated, the tool you can’t crack, whatever’s stuck. Direct, hands-on, no pitch waiting at the end.