COWORK PRIMER

Claude with your tools loaded.

The Lens playbooks describe the work. Cowork is what lets the agent see the work, the inbox, the calendar, the transcripts and the pipeline already on your desk. This page is the bridge, from a useful chatbot to a daily-driver assistant that knows what's happening in your week and can act on your behalf with permission.

Read time 8 minutes

1 · What Cowork is

Cowork is Claude Code's mode for running with your real workplace tools loaded as context. Instead of a chat window with no memory of your week, the agent reads from your Gmail, Slack, Notion, Linear, HubSpot, Granola transcripts, Google Calendar, Figma files and GitHub repos. It sees the actual emails sitting in your inbox this morning, the actual call transcript from yesterday, the actual deal stages in your CRM. Then it can summarise, draft replies, update records, file tasks and produce the next artefact, with your approval before anything ships.

The mechanism underneath is MCP, the Model Context Protocol. Anthropic published the spec, and every major tool vendor now ships an MCP server. The server exposes a tool's data and actions in a structured way the agent can read. Once a server is connected, the agent can list your Gmail threads or update a HubSpot deal as easily as it can run a shell command.

Cowork combines three things into one working surface.

The agent, Claude in its Code form, which can reason across the loaded context and call tools to act.
The MCP connectors, one per tool, that the agent uses to read state and take actions on your behalf.
The plugins, packaged collections of skills like the ones in The Lens, that tell the agent how to do named workflows well.

For Saoirse at Cascadia Endurance, that means asking Claude what's on her plate this morning and getting back a real answer drawn from her actual calendar, her actual unread inbox and the actual Slack threads that mention her name, instead of generic productivity advice.

2 · Install Cowork and set it up

Five steps end to end. The whole sequence takes about thirty minutes if you're connecting accounts as you go.

Install Claude Code

Claude Code is the desktop client that hosts Cowork. Download and install from claude.com/code. Sign in with the same account you use for claude.ai. On first launch it walks you through giving filesystem access and a working folder.

Add the Manual Focus plugin marketplace

In Claude Code, run the marketplace command to point the plugin manager at the Lens skills and any other Manual Focus plugins we publish.

/plugin marketplace add Scylark/manual-focus

Install the Lens plugin

One command installs all 26 Lens skills at once (including the setup-the-lens onboarding orchestrator that handles the rest of setup the moment you ask, and the video-script-to-heygen utility for rendering playbook explainers on demand), so the agent recognises positioning audits, eval-gated drafting, race recap pipelines and the rest the moment you describe a task that fits.

/plugin install the-lens@manual-focus

Ask Claude to set up The Lens

This is the easy mode. The Lens ships an onboarding skill that walks you through everything else in this section, in order, on your actual data. It asks what work you're doing this week, recommends the Cowork plugins matched to your role, pulls your existing brand documentation in from Notion, Google Drive, Figma or wherever else, writes a structured .lens/ directory in your workspace and generates a task list of the foundational assets you still need. Twenty to forty minutes end to end.

set up the lens

Or run the slash command directly.

/setup-the-lens

Cowork has its own setup wizard too

Anthropic ships a guided setup for Cowork. The Lens setup skill will use it where it can, but you can also run it directly if you want to install Cowork plugins before starting on Lens work. The two wizards play nicely with each other, neither installs the other's plugins automatically but each one knows what the other needs.

/setup-cowork

The wizard asks what kind of work you do, suggests a starter plugin set, and then opens the connector flow for each tool it recommends. Each connector takes you through an OAuth prompt in your browser, the same way you'd authorise any SaaS integration, and the credentials live in Claude Code's secure store rather than in your prompts.

Connect the MCP servers you need first

You don't have to wire up everything on day one. The priority order in section 4 is the one that pays back fastest for a marketing operator. Start with email, calendar and call transcripts, then add the others as the workflows surface what you're missing.

3 · The plugins that matter most

Cowork plugins are packaged collections of skills, the same shape as the Lens skills but built for different jobs. The right starter set depends on the role you're playing. Three common shapes.

Solo marketer or fractional CMO

One person running the function across one or two brands. The four plugins below cover daily voice work, campaign planning, the personal back office and the post-call loop from sales conversations.

brand-voice, generates and enforces brand voice guidelines across every draft.
marketing, campaign plans, email sequences, content briefs and channel strategy.
productivity, daily briefings, inbox triage, task management.
sales, used here for the call-summary skill so customer-call transcripts become CRM updates and follow-up drafts.

In-house GTM team

Marketing leader inside a 20-to-200-person endurance brand with a sales counterpart and a product team to coordinate with. Add the full sales and product-management plugins on top of the solo set.

Everything above, plus
sales in full, pipeline reviews, account research, draft outreach, daily briefings, competitive intel.
product-management, spec writing, sprint planning, stakeholder updates, metrics reviews, research synthesis.

Agency or design studio

A small team shipping work for several brands at once, with design output and a need to keep every client's voice distinct. Add design tooling and the brand-voice-enforcement skill on top of the GTM stack.

Everything above, plus
design, design critique, accessibility review, UX copy, design-system audits, research synthesis.
brand-voice-enforcement as a standalone skill, applied to client content drafts as a gate before delivery.

Each plugin installs the same way the Lens does.

/plugin install brand-voice
/plugin install marketing
/plugin install productivity
/plugin install sales

Once installed, every plugin can be customised to your organisation's vocabulary, tools and workflows. The /cowork-plugin-customizer command walks through which connectors you have wired up, which skills inside the plugin make sense for your role and which to disable. The plugin you end up running is yours, not a generic install.

4 · MCP connectors to wire up first

Connectors are where Cowork stops being a fancy chatbot and starts being a real working surface. Each one opens a tool to the agent. The priority order below is what we've seen pay back fastest for a marketing operator at an endurance brand.

Email, Gmail or Outlook. The single highest-leverage connector. Reading and drafting replies collapses inbox triage from an hour to fifteen minutes.
Calendar, Google Calendar or Outlook. Without it the agent can't tell you what's on your plate today or prep you for the call at three.
Slack, or whatever your team uses for chat. Mentions, threads you're in, the channels you watch. Surfaces what's heating up without you needing to scroll.
Your CRM, HubSpot, Salesforce, Close or Apollo. Pipeline status, deal stages, the last touch on each account. Lets the agent update records after calls and surface deals that have gone quiet.
Notion or your knowledge base. The brand's institutional memory. Wiki pages, briefs, the positioning doc, the voice guide. Lets the agent ground drafts in the actual brand, not a generic version.
Granola or Fireflies, the call-transcript surface. Once meeting transcripts are connected, every call becomes a CRM update, a follow-up draft and a task list in one prompt.
Linear or Asana, the task surface. Lets the agent file work, update statuses and pull the right ticket into context when you're drafting against it.

You don't have to install everything on day one. Start with email, calendar and transcripts, see what the agent surfaces in a week of normal work, and add connectors as the gaps become obvious. Two or three connectors is enough to feel the shift. Seven is enough to make Cowork the place you start every morning.

5 · Three ways Cowork shows up day to day

Three illustrative shapes, all running on the same Cowork stack at Cascadia Endurance.

Monday morning, the briefing

Saoirse opens Claude Code with her coffee and asks "what's on my plate today?" The agent reads her calendar, scans the last 24 hours of unread mail, checks the Slack channels she watches and surfaces the three things that need attention before lunch. Two press enquiries that came in over the weekend, the gear launch brief sitting in her review queue, a Slack thread about the race weekend logistics with unresolved questions. She has a clean read of her day in five minutes instead of forty.

Wednesday afternoon, the call loop

Saoirse finishes a discovery call with a prospective retail partner. Granola recorded the transcript. She opens Claude Code and asks for the post-call loop. The agent reads the transcript, drafts the HubSpot update with the right attributes (account size, decision-maker, next step, timeline), drafts the follow-up email in the Cascadia voice, and files a Linear ticket for the sample shipment that came up in the conversation. She reviews each artefact, edits where her judgement says so, and sends. The whole loop takes ten minutes instead of the hour it used to.

Friday afternoon, the rollup

End of week. Saoirse asks for the pipeline rollup and the content cadence check. The agent pulls deal movement from HubSpot, the week's published content from the Notion editorial calendar, the social posts that went live, and the open Linear tickets in the content pipeline. It produces a written rollup for the founder, drafts next week's editorial slate based on the cluster plan, and queues three social posts for review on Monday. Saoirse spends fifteen minutes reviewing instead of two hours compiling.

None of these workflows replace her judgement. They remove the friction in the work she already knows how to do well, so the time she keeps gets spent on the work the agent can't do for her.

6 · The Productivity stack of The Lens

The 10 playbooks in the Productivity stack are written specifically for Cowork operators. Each one is a workflow you can run today once the right connectors are wired up.

Browse the Productivity stack →

daily-briefing-pipeline, the morning briefing that pulls calendar, inbox and Slack into one prioritised read.
email-triage-and-draft, batch processing the inbox with reply drafts ready for review.
meeting-prep-stack, account research, attendee context and a suggested agenda before every call.
call-follow-up-loop, transcript to CRM update to follow-up email to filed task, in one prompt.
slack-focus-pass, the channels-you-watch surface, with what's actually worth your attention pulled forward.
document-drafting-partner, the long-form drafting partner that grounds every doc in your existing voice profile and message house.
weekly-pipeline-rollup, the Friday view of deal movement, stuck accounts and the week's content cadence.
quarterly-okr-synthesis, the quarter-close ritual that turns notes, retros and metrics into the next quarter's OKRs.
personal-knowledge-base, the second-brain pattern that captures what you read, what you wrote and what you learned, in the place you can search later.
inbox-to-task-pipeline, the bridge from a one-line email request to a properly filed task with the right context attached.

These ten compose. The morning briefing surfaces what needs attention. Inbox triage clears the easy ones. Meeting prep loads the next call. The call follow-up loop closes the loop. The weekly rollup brings the whole week together. The cadence is the point.

7 · What Cowork is not

Four boundaries worth stating up front, so the install pays back without overshooting.

Not a replacement for your judgement

The agent drafts, summarises and proposes. The decisions about what to send, what to commit to and how to read the room stay with you. Cowork is a leverage layer over your work, and the work itself still belongs to you.

Not an autonomous agent running unsupervised

Cowork acts with permission. Every email draft, every CRM update, every task filed shows up for your review before anything goes out. The agent can prep a ten-step workflow in a minute, and you still approve each step that touches the outside world. The point is faster review, not removed review.

Not a fix for broken processes

If the underlying process is unclear, the agent will speed up confusion. If your CRM stages don't mean anything, the agent will update them faithfully and you'll have faster meaningless data. Wire Cowork into workflows that already work, and it compounds. Wire it into a broken process and you've just made the broken process faster.

Not a silver bullet for back-office overwhelm

The agent removes friction from workflows you already do well. It does not remove the underlying volume. If your week has too much in it, Cowork helps you process the load. It doesn't help you decide what to drop. That call is still yours, and the strategic playbooks in the rest of The Lens are where to start with it.

8 · Where to start

The five-step install plan most readers should follow.

Install Claude Code today. Download from claude.com/code, sign in, give it a working folder.
Install the Lens plugin. Two commands. /plugin marketplace add Scylark/manual-focus, then /plugin install the-lens@manual-focus. All 26 Lens skills are now available. Ask Claude "set up The Lens" and the welcome skill walks you through picking a starter playbook.
Run /setup-cowork and connect three things. Gmail (or Outlook), Google Calendar (or Outlook) and your CRM. The wizard walks through OAuth for each. Skip the rest for now.
Run the daily-briefing-pipeline playbook this Monday morning. One prompt, one read of your day. See where the agent is right and where it's missing context. That's the signal for which connectors to wire up next.
Add one new connector per week. Slack the second week, Granola the third, Notion the fourth. By week six you have a Cowork stack that collapses your daily back-office friction without ever having taken a whole afternoon to set up.

The reason this works is that each connector compounds the last. Email plus calendar is useful. Email plus calendar plus call transcripts is a different category of useful. Add Slack and the CRM and the agent is now reading the same surface you do, which is what makes the briefing actually match your morning instead of guessing at it.

Pick a workflow. Run it Monday.

The Cowork stack pays back the moment the first playbook runs against real data. The Productivity stack of The Lens is the fastest path to that first run, and the rest of the library composes on top once the briefing pattern feels natural.

Read the Productivity stack Browse the full library Browse the skills