Using Cowork

The Cowork working manual

The First Week with Cowork

6 lessons

  1. Stop Asking Cowork to Do Everything in One Sentence

    Most new users write prompts like Google searches. Cowork is closer to a colleague who needs context; a one-line ask gets a one-line-quality answer.

  2. Give Cowork Its Own Folder

    Cowork operates inside a folder you choose. If you pick "Documents" or "Desktop", you will end up with a mess that's hard to navigate next session.

  3. Cowork Without Connectors Is Half a Cowork

    The aha moment happens when Cowork can read your calendar, email, project tracker, and docs.

  4. The Five-Minute Morning Ritual

    Most AI tools die from neglect because nothing prompts you to open them. A daily anchor fixes that.

  5. Cowork Forgets Everything by Tomorrow. Here's the Fix.

    Every session starts blank. The fix isn't longer prompts. It's memory files.

  6. Read the Tool Call, Not Just the Answer

    Cowork's best users watch what it's doing, not just what it says.

Managing Cowork's Memory

6 lessons

  1. Memory Files Beat Long Prompts

    Pasting context into every message is the slow way to use Cowork.

  2. Write Cowork a 200-Word Biography

    Cowork answers like a stranger because it is one.

  3. The Cast-of-Characters File

    Every "who is Sarah again?" question burns a turn that could have been work.

  4. Decoding Your Company's Acronyms

    Cowork has no idea what your internal jargon means, and it won't admit it.

  5. Let Cowork Update Its Own Memory

    The best memory systems update themselves.

  6. The Quarterly Memory Audit

    Stale memory is worse than no memory; it confidently misleads.

Connectors: Where Cowork Meets Your Tools

9 lessons

  1. Cowork + Gmail: Triage 100 Emails in 90 Seconds

    Most inbox triage is sorting, not reading.

  2. Cowork + Calendar: Why You're Probably Double-Booked Right Now

    You can't see your own schedule conflicts. Cowork can.

  3. Cowork + Linear (or Jira): The Stuck-Issues Report

    Every backlog hides issues that haven't moved in weeks and no one's owning.

  4. Cowork + Slack: Stop Doomscrolling Channels

    Catching up on Slack is the modern email purgatory.

  5. Cowork + Google Drive: Find the Doc You Half-Remember

    Drive search is bad. Vibes-based retrieval is good.

  6. Cowork + Your CRM: The Friday Pipeline Review in Five Minutes

    Pipeline reviews die from formatting work, not from analysis.

  7. Connector Chaining: When One Tool Triggers Another

    The killer moves are cross-tool: "find the email about the launch, summarize it, and create a Linear issue."

  8. What Connectors Actually See and What They Don't

    A connector is not a free pass into the whole tool.

  9. The Read-Only-First Rule for Connectors

    Don't grant write permissions until you trust the workflow.

Skills & Plugins

6 lessons

  1. Skills Aren't Features. They're Specialized Brains You Switch On.

    Most users don't know skills exist. The ones who do still don't know how Cowork picks one.

  2. Don't Build a New Skill. Borrow Someone Else's First.

    Plugin marketplaces already contain 90% of what most people need.

  3. Your First Custom Skill: A Personal SOP in Markdown

    A skill is just a markdown file that teaches Cowork how you do things.

  4. When Skills Don't Trigger (and How to Fix Them)

    Skills fail silently. They just don't fire, and you don't know why.

  5. One Skill Per Workflow, Not Per Topic

    A skill called "marketing" does nothing useful. A skill called "draft my weekly investor update" does everything.

  6. Plugins as Hire Decisions

    Every plugin you install is like adding a new specialist to your team: useful when relevant, noisy when not.

Scheduled Tasks & Automations

5 lessons

  1. Your First Scheduled Task: A Daily Briefing That Writes Itself

    Most people don't realize Cowork can run on a timer.

  2. The Watch-and-Notify Pattern

    Instead of you checking on something, Cowork checks for you.

  3. Weekly Patterns: Friday Wrap-Ups, Monday Setups

    Anchor automations to the rhythm of your week, not the rhythm of your enthusiasm.

  4. Don't Schedule Anything You Haven't Run Manually Three Times

    Scheduled tasks fail silently, and silent failures rot trust.

  5. Killing a Scheduled Task Without Guilt

    Most automations stop being useful within a few months.

Artifacts: Pages That Refresh Themselves

5 lessons

  1. The Difference Between a Reply and an Artifact

    A reply scrolls off screen. An artifact persists and re-fetches your data.

  2. Build a Personal Mission Control in 10 Minutes

    A single page showing today's calendar, unread email count, top tasks, and pipeline.

  3. Stakeholder Artifacts: A Status Page You Don't Have to Update

    Most status updates die in email threads.

  4. Filters That Stick: Make Your Artifact Remember Your Choices

    Artifacts can persist your last-used filter so you don't reconfigure each time.

  5. When Artifacts Are Wrong: The Probe-First Habit

    Artifacts that call connectors break when the underlying API shape drifts.

Inbox & Communication

6 lessons

  1. The "Reply Needed" Filter That Beats Your Inbox

    Search operators can't tell whether you owe someone a reply. Cowork can.

  2. Draft Replies in Your Voice, Not Cowork's

    AI-drafted emails sound like AI-drafted emails. Recipients can tell.

  3. The Quick-Thanks Trap

    AI is unnervingly good at writing replies you shouldn't be sending at all.

  4. Catching Up After Vacation Without Losing a Day

    1,200 emails, 14 Slack channels, three docs out of date.

  5. Find the Decisions Buried in Your Inbox

    Most decisions get made in email threads and forgotten within a week.

  6. What Happens to the Data You Connect

    The skeptical question every business user has: what happens to the data you connect or paste? Here's what's shared, what's retained, and how to handle confidential work.

Meetings: Before, During, After

5 lessons

  1. Five-Minute Prep for Any Meeting

    A standardized pre-meeting prompt is worth more than any single template.

  2. Recurring-Meeting Memory: Stop Re-Litigating Old Decisions

    Every recurring meeting reopens the same questions because nobody can find what was decided.

  3. Turn a Transcript Into Three Outputs in One Pass

    Notes, action items, and a follow-up email: most people produce them in three passes.

  4. Spot What You Missed: Patterns Across Many Transcripts

    One meeting tells you nothing. Twenty tell you everything.

  5. The 24-Hour Follow-Up Rule, Automated

    Most follow-ups never happen. Calendars don't help.

Research & Knowledge

5 lessons

  1. Why You Should Almost Never Ask Cowork a Single-Search Question

    One search returns one perspective.

  2. The Three-Source Rule for AI-Written Research

    Never trust a single-source answer on anything that matters.

  3. Build a Personal Wiki You'll Actually Use

    Most personal wikis die because adding to them is friction.

  4. Tracking a Topic Over Time

    A single research report is a snapshot. A scheduled re-run is a tracker.

  5. Translate This Document for My Audience

    Most knowledge fails because of audience mismatch, not content quality.

Writing with Cowork

5 lessons

  1. Cowork Writes Worse Than You Do, Until You Show It How You Write

    Voice is learnable. Cowork's defaults are not your voice.

  2. Outline First, Draft Second, Always

    AI-written drafts collapse because the structure isn't yours.

  3. The Reverse-Outline Edit

    Most editing feedback is too vague to act on.

  4. Don't Ask "Make This Better." Ask "What's the Weakest Paragraph?"

    A sharper question gets a sharper answer.

  5. When Cowork Should Write Nothing

    Sometimes the right move is for Cowork to push back, not draft.

Documents, Spreadsheets, Slides

5 lessons

  1. The Deck You Don't Want to Make

    PPTX from a doc, in one prompt, if you brief it right.

  2. Spreadsheets as Output, Not Input

    People ask Cowork to read spreadsheets. The reverse is more useful.

  3. PDF In, Searchable Knowledge Out

    A stack of PDFs is a stack of dead documents until they're queryable.

  4. The "Audit My Doc" Pattern

    Before sending a doc, ask Cowork what's missing, ambiguous, or contradictory.

  5. Templates as Memory

    Every time you ask for a deck or doc, you re-specify the structure.

Gotchas, Limits & Anti-Patterns

6 lessons

  1. Cowork Will Confidently Make Things Up. Here's How to Catch It.

    Every user gets burned by hallucination once. Most get burned again.

  2. One Long Session Isn't Infinite

    One long session isn't infinite. As the context fills, Cowork starts losing the middle; the fix is knowing when to start fresh.

  3. When "Just Ask Cowork" Is the Wrong Answer

    Not every problem is a prompting problem.

  4. The Connector That Lies to You

    Connector data can be stale, partial, or filtered without warning.

  5. Don't Let Cowork Decide What's Important

    Ranking and prioritization need your fingerprints. AI ranking feels objective and isn't.

  6. The Folder Sprawl Problem

    Cowork creates files. Without rules, your workspace turns into a junkyard.

Power-User Patterns

6 lessons

  1. Sub-Agents: When to Delegate Inside a Single Session

    Most users don't know Cowork can spawn focused workers.

  2. The Probe-Then-Build Loop

    Before asking for a finished thing, ask for the shape of the data.

  3. Reusable Prompts Are More Leverage Than Reusable Code

    A prompt you can run weekly is more leverage than a script most people will never write.

  4. Stacking Skills: When Two Specialists Beat One Generalist

    The research skill plus the docx skill produces a different output than asking once.

  5. The Show-Your-Work Habit

    Ask Cowork what it's about to do before it does it.

  6. From One-Off Workflow to Permanent Plugin

    Once a workflow runs three times, it's worth packaging.