Claude Cowork walkthrough

Teach Claude Cowork how you work, then let it organize

Cowork's first guesses are generic because it doesn't know you yet. This walkthrough builds an operator brief from your own notes, puts it in your preferences, and shows the difference on a real job: sorting 164 CRM exports, then turning the process into a skill.

▶ Interactive · 9 steps6 minFor RevOps leads and operators
Click through it. Use Next, the arrow keys or the dots. Orange boxes show where to look.Expand ⤢ for full screen

Illustrative recreation of the Claude Cowork desktop app with fictional sample data. Not the actual product; screens and labels can change as Cowork ships updates.

Nine screens: context first, then work

Permission, proposal, brief, preferences, better categories, the move, a skill, research synthesis and a weekly briefing.

  1. Grant access to one folder

    Read the permission prompt; allow once while testing, always-allow only for folders you trust.

  2. Ask for a proposal first

    Have Claude survey the folder and propose a structure before moving anything.

  3. Build an operator brief

    Point Cowork at your notes and ask for a markdown brief on your role, definitions and output style.

  4. Paste it into preferences

    Settings > General > personal preferences, so every new task starts with your context.

  5. Rerun the categories

    The same question now returns categories that match how you work.

  6. Approve the move and index

    Subfolders, date-first names and an index file in one approval.

  7. Save it as a skill and schedule it

    Package the process as a skill and run it monthly.

  8. Synthesize research

    Point at one research folder and ask for themes, tensions with your playbook and tests.

  9. Ask for a weekly briefing

    Where am I, what matters, what am I missing, saved as an editable note.

How JayOh uses this

Context is the real unlock

The same principle drives everything we build with Claude: the model is only as good as the definitions and context you give it. See Claude for GTM for how we apply it across revenue teams.

  • Operator briefs for each leader so outputs match their definitions.
  • Shared definitions for pipeline, coverage and stages, written once.
  • Folder hygiene skills for exports, contracts and board drafts.
  • Weekly briefings that surface slipping work before it becomes a fire.
Guardrails we set first

Keep a human in the loop

  • Proposal before any bulk change.
  • Only the folders the task needs. Notes vaults are opt-in.
  • Briefs get a human edit before they become preferences.
  • Deletes stay manual. Archive, don't purge.
9screens in this walkthrough
164illustrative files sorted
6context-aware folders
11research notes synthesized

Common questions

Short answers before you set this up.

How do I give Claude Cowork context about me?

Ask Cowork to build a short brief from your own notes (role, definitions, metrics, writing style), edit it, then paste it into Settings > General > personal preferences. New tasks start with that context.

Can Claude Cowork organize and rename files?

Yes. Grant it a folder, ask for a proposed structure first, then approve the subfolders, naming rule and moves. Ask for an index file so you can search one document later.

How do I turn a Cowork task into a reusable skill?

After a run you are happy with, ask Claude to create a skill from what you just did and copy it to your skills. It can then run on request, automatically when the request matches, or on a schedule.

Where does Claude Cowork run?

Cowork runs in the Claude desktop app on Mac or Windows on a paid plan. It works on folders you grant it on your computer, can use connectors to apps like Gmail, Google Drive, Slack and HubSpot, and can control a browser or desktop apps when you allow it. The website is Chat, not Cowork.

Want Claude that knows how your revenue team works?

JayOh writes the definitions, briefs and skills that make Claude useful on day one, not week six.

Talk to JayOh