Getting Started with Claude Cowork — 7-Step Onboarding + 5 Use Cases + Plugin Build (Notion Walkthrough)

Source: ai-research/notion-claude-cowork-getting-started-2026-05-02.md (Notion Platform Walkthrough at notion.so/jonathonc/Getting-Started-with-Claude-Cowork-use-cases-plugins-34525679607682429ad68187913534fc, fetched via claude_ai_Notion MCP 2026-05-02; recipe dated 2026-02-16; 5-min page property but the actual content is a 15-min onboarding + extensive use-case + plugin-build extension). Parent vault page: AI Recipe Vault.

A non-developer-friendly walkthrough that takes a Pro-account user from “I’ve heard of Cowork” to a finished autonomous file-organization task in 15 minutes, then layers on five non-obvious use cases (Hiring Manager, Group Travel Agent, SEO Auditor, Customer ICP Builder, Content Strategist) and a deep plugins/skills section that ends with Claude building its own plugin from scratch (the “Lead Magnet Launch Kit” example). British spelling throughout (organise, personalised, “AI Recipe Vault” container) suggests UK-templated origin — same authoring pattern as the sister Cowork + Apify scraping recipe.

Key Takeaways

• Cowork lives in Claude Desktop, not the web. Step 1 forces the install. Once installed, Cowork and Code tabs appear next to the regular chat. The walkthrough deliberately puts non-developers off the web app entirely so they don’t try to use Cowork features that aren’t there.
• Folder-scoped permissions are the safety affordance. Step 2 has a “Allow Claude to change files in [folder name]” prompt. Source emphasizes: “Claude can only access the folders you explicitly give it permission to. It’s not going to go rummaging around your hard drive.” Two recommended approaches: dedicated Cowork/ folder (safe sandbox) or point straight at the messy folder you actually want fixed (Downloads, Screenshots, Invoices).
• Sonnet 4.5 is the recommended default model. Source explicitly: “good performance, doesn’t burn through credits.” Opus 4.6 (note: written before W16 which made Opus 4.7 the default on Max/Team Premium) is reserved for “the heavy stuff.” Pairs with the Intermediate Course Module 4 model-tiering guidance and the Advisor Strategy.
• Step 3’s first task — file organisation — is intentional. Source says start with file/document management because “they’re the easiest way to see immediate value and build confidence.” The first prompt template is intentionally un-fancy: Go through my screenshots, rename them so it's obvious what they are, and then place them in a folder structure that makes them easier for me to find in the future. No prompt engineering, just plain instructions. This is the “treat Claude like a smart assistant” framing.
• Step 6 (Claude in Chrome) is the qualitative jump. Adding the Claude in Chrome extension turns Cowork into a tool that browses for you. Active Claude tabs glow orange in Chrome. Source frames this as “where things get properly powerful” — combine with file access + connectors and you get the full multi-source workflow surface (e.g., the Use Case 5 content-strategist flow that spans Notion + YouTube + your existing ICP doc).
• Five use cases demonstrate compounding capabilities, not isolated tricks. The Hiring Manager use case (raw CVs → scoring framework → leadership spreadsheet) is files-only. Group Travel Agent (booking confirmations + screenshots + WhatsApp messages → shareable itinerary) uses files + light reasoning. SEO Auditor adds Chrome browsing. Customer ICP Builder adds the Gmail connector + dashboard generation. Content Strategist combines Notion + YouTube browsing + cross-referencing prior work. The escalation is the lesson — Cowork is a stack, not a tool.
• Plugins vs Skills clarified with the chef-vs-recipe analogy. A skill is a set of custom instructions for one task (“recipe card for cooking one meal”). A plugin bundles multiple skills + tool connections + connectors (“experienced chef who knows the whole recipe book and works in a team kitchen”). Cowork ships with department plugins (Marketing, Finance, Legal, Data, Bio Research, Sales, Productivity); each plugin is install + manage to inspect bundled skills, commands, connectors. See the dedicated Cowork Plugins article for the full marketplace map.
• Customising existing plugins is the leverage move. Don’t write plugins from scratch — Customise an installed one with natural language: “I want to add my content atomizer skill to this marketing plugin.” Claude updates the plugin in place. This is the operator-level power user move.
• Claude can build its own plugin from a business-context prompt. Final section walks through asking Claude Based on what you know about my business, what plugins would be most valuable for me to build? (ideally with a Claude Project loaded for context), picking one, and running Build me that plugin. The example — “Lead Magnet Launch Kit” — is exactly the same content domain as Brandon Storey’s lead-magnet course and the LinkedIn Engagement Machine recipe; saving it via Save Plugin makes it immediately available in the sidebar with no upload/download.
• Limitations are explicit. No memory across Cowork sessions (keep continuity files in your working folder). No chat sharing. Desktop-only — no web/mobile. App must stay open + computer awake during execution. Tasks consume local resources because they run on your machine. Source labels it “still a Research Preview” — date-anchor when reading.

The 7-Step Onboarding Spine

Step	What It Achieves	Key Action
1	Install Claude Desktop	claude.ai/downloads, log in with existing account
2	Open Cowork + connect a folder	Cowork tab → “Choose a folder” → confirm permission → pick model (Sonnet 4.5 default)
3	Run first file-organisation task	Plain-English prompt against Screenshots or Downloads folder
4	Review what Claude built	Open the folder, sanity-check structure + filenames; iterative correction in same chat
5	Create files and spreadsheets	Invoices use case: rename + organise + auto-generate CSV/Excel tracker
6	Add web browsing with Claude in Chrome	Install extension → permission per site → orange-highlighted active tabs
7	Explore connectors / plugins / projects	+ button → Connectors (Gmail, Drive, Notion) / Plugins / Include project

The 5 Non-Obvious Use Cases (Verbatim Prompts)

The full prompts are in the ai-research source. Headline of each:

1. The Hiring Manager — folder of CVs → scoring framework from JD → ranked leadership-ready spreadsheet
2. The Group Travel Agent — booking confirmations + screenshots + WhatsApp messages → day-by-day itinerary with travel + payments + timings
3. The SEO Auditor — Search Console data + Chrome browsing of top 5 pages → action list per page (outdated content / SEO issues / content gaps)
4. The Customer Intelligence Builder — Gmail folder of customer emails → Word-doc ICP report + interactive HTML dashboard (pains, dreams, goals, content recommendations)
5. The Content Strategist — Notion competitor list → YouTube browsing → trending-topic synthesis + ICP cross-reference → 30-day content pipeline DB in Notion (3 videos/week, themed)

Plugins & Skills Path (Compressed)

• Browse Cowork’s department plugins: Marketing, Finance, Legal, Data, Bio Research, Sales, Productivity. Install is one-click.
• Inspect an installed plugin via Manage — see bundled skills, commands (slash-prefixed), and connectors.
• Activate a plugin via + → Plugins → select. Right side shows available commands. Example: /write-email-sequence Can you write a welcome sequence for people that sign up to my AI recipe vault?
• Customise existing plugins by adding skills in natural language: “I want to add my content atomizer skill to this marketing plugin.”
• Add from GitHub / URL / upload via Browse Plugins → Personal → +. Recipe references “Awesome Claude Plugins” repo as a 100+-skill third-party source — note this overlaps with the Claude Skills Hub (claudeskills.info) and agents catalogs documented elsewhere in the wiki.
• Build your own by asking Claude what would be most valuable for your business (with a Project loaded for context), then Build me that plugin. Save in place — no upload step.

Practical Tips (Verbatim)

• Start with file and document management tasks — they’re the easiest way to see immediate value and build confidence.
• Be specific with your instructions — you don’t need fancy prompts, but clear goals make a massive difference.
• Keep the desktop app open — if you close it, the task stops. Your computer needs to stay awake too.
• Watch your usage — Cowork burns through credits faster than normal chat because it’s running multi-step autonomous tasks. Use Sonnet 4.5 for everyday tasks, save Opus for the heavy stuff.
• Use dedicated folders — keep things controlled. Give Claude access to specific folders rather than your entire Documents directory.
• Batch related work — if you’ve got multiple similar tasks, do them in one session rather than spread across several.

Caveats

• Date-anchor the model + feature claims. Recipe is dated Feb 16, 2026. Sonnet 4.5 / Opus 4.6 was the recommended pair at the time; W16 (April 13–17, 2026) shipped Opus 4.7 as the new default on Max/Team Premium with xhigh effort. Adjust the model-picker step accordingly. Computer Use / Cowork Dispatch landed W13 / Mar 23 2026 — both feature in Step 6 and beyond, but the recipe doesn’t surface Dispatch by name (uses “Claude in Chrome” as the desktop-driving surface).
• Source is curated, not authoritative. Like the sister Cowork + Apify scraping recipe, this lives in jonathonc’s personal Notion as an “AI Recipe Vault” entry — UK-style English, polished but unsigned. Not a Claude.com / Anthropic-published walkthrough. Treat as starting framework + curated reference, not vendor-sanctioned best practice.
• Lead Magnet Launch Kit example is plugin-author-as-prompt. The “ask Claude what plugins would be valuable, then ask Claude to build one” workflow is presented frictionlessly. In practice, the resulting plugin is only as good as the business context provided (hence the “Project loaded” pre-condition). Without context, it produces generic scaffolding. See Skill Design Patterns for what production-quality plugin design actually requires.
• GitHub-plugin-install instruction is loose. Recipe says “search GitHub for Awesome Claude Plugins” — no specific repo URL. The wiki’s curated equivalents are skills (canonical), agents (184 agents / 78 plugins), and claudeskills.info (658+ skills). Use those instead of generic GitHub search.
• 5-min page property is wrong. Notion property says “Time: 5 minutes.” Actual content is ~15 min onboarding + 5 use-case prompts + plugins/skills section + custom-plugin-build section. Plan for 30-45 minutes if you actually run all of it.

Try It

1. Walk Step 1 → Step 4 in one sitting. Install Desktop, point at your messiest folder (Downloads is the meme but Screenshots tends to win), run the file-organisation prompt, review. ~15 min. Doing this is what makes the rest of the recipe feel concrete.
2. Pick the use case that maps to your week. SEO Auditor for the seo-content cluster; Customer Intelligence Builder if you’re inheriting an inbox of customer emails; Content Strategist if you’re spinning up a content calendar against Cowork’s connector surface. Run that prompt verbatim. Notice what fails — that’s where you’ll customize.
3. Install one department plugin and use it on real work. Marketing for sequencing, Finance for reconciliation, Sales for pipeline. Compare the Cowork plugin output against your existing tool for that workflow. The honest comparison is the point.
4. Try the “build me a plugin” workflow with a Project loaded. Claude Project should contain at minimum: brand voice, ICP, pricing, sample outputs. Then ask Based on what you know about my business, what plugins would be most valuable for me to build? Take the most boring suggestion (the one that does the work you actually skip), say Build me that plugin, save it, run it next week.
5. Pair with the LinkedIn Engagement Machine. Run the LinkedIn Engagement Machine prompt chain inside a Cowork session that has Notion + Drive + Gmail connectors active. The lead-magnet step (Prompt 4 in that recipe) becomes a one-shot Cowork task instead of a manual format-and-export step.
6. Read the Cowork product overview if you haven’t. Claude Cowork (Product Overview) documents the pricing tiers, enterprise feature gate (April 8 2026), and the Dispatch async surface that’s adjacent to but distinct from this onboarding. Knowing the difference between Cowork (in-session async-ish) vs Dispatch (computer-use, phone→desktop hand-off) prevents conflating two different patterns.

Related

• Claude AI — topic landing
• Claude Cowork (Product Overview) — the entity page; pricing, enterprise tier, feature timeline
• Dispatch in Claude Cowork (Tutorial) — the phone-to-desktop async pattern complementing this in-session walkthrough
• Cowork Plugins — full marketplace map; this recipe gestures at the surface, the plugins article documents it
• Cowork for Marketing — marketing-specific Cowork patterns (this recipe touches Marketing plugin, but doesn’t dive)
• Cowork + Apify Scraping Recipe — sibling Notion AI Recipe; same authoring pattern, deeper integration with Apify connector for prospecting and PR-ready research reports
• The LinkedIn Engagement Machine — sibling Notion AI Recipe; LinkedIn content prompt chain that pairs naturally with the “build a Lead Magnet Launch Kit plugin” example here
• Lead Magnet Creation with Claude Code (Brandon Storey) — Builder-track equivalent of the “build a plugin in chat” pattern (Brandon does it via Claude Code skills + downloaded design skill; this recipe does it via Cowork’s in-app plugin builder)
• Seven Operator Use Cases for Claude’s New Stack (Rick Mulready) — Operator-perspective tour overlapping with the use-cases section here (Mulready’s Cowork Projects, Dispatch+phone, Computer-Use UX audit)
• Computer Use (Desktop + CLI) — the underlying capability behind Step 6 (Claude in Chrome) and Use Case 3 (SEO Auditor)
• Skills vs MCP vs Plugins — When to Use Which — decision guide; the chef-vs-recipe analogy in this recipe is the same teaching device
• Claude Code Skills Ecosystem — the skill side of the skill-vs-plugin distinction
• Marketing Skills Bundle (Corey Haines) — what the Marketing plugin in Cowork is reaching for at the skills layer
• social-media-skills (Charlie Hills) — alternative skill bundle covering the social/LinkedIn surface
• Week 13 (Mar 23–27) — Computer Use lands in Desktop / Cowork foundations
• Week 16 (Apr 13–17) — Opus 4.7 default on Max/Team Premium (post-dates this recipe’s Sonnet 4.5/Opus 4.6 model recommendation)
• Intermediate Course Module 3 — Connecting to Your Tools — broader decision tree for MCP / Connectors / Skills / Cowork
• Intermediate Course Module 4 — Multi-Agent Patterns — model tiering rationale beneath the Sonnet 4.5 default

Open Questions

• What does the recipe miss vs official Anthropic Cowork docs? Worth a side-by-side against claude.com/product/cowork (already in the wiki via Cowork product overview) to surface any vendor-canonical features this recipe omits or simplifies.
• Is the “Lead Magnet Launch Kit” plugin example a real artifact or generated-as-demo? Source describes it conversationally as “I asked Claude to build a Lead Magnet Launch Kit plugin… I give it a topic and who it’s for. It concepts the offer, outlines landing page copy, writes the email welcome sequence, and creates a distribution checklist.” If a real artifact survives somewhere, ingest it as a worked example of the sequential-workflow skill pattern.
• Computer Use vs Claude-in-Chrome distinction. The recipe uses “Claude in Chrome” as the only browser surface. Computer Use (W13/W14) is the broader desktop-driving capability. Worth clarifying when each is the right reach — Chrome extension is read-only-ish on web pages; Computer Use is the full desktop. Probably belongs in the Cowork Plugins article rather than here.