Source: raw/How_to_Use_Claude_Cowork_2.0_Full_Workflow_Automation_Guide_2026.md (auto-caption transcript; “Claude work”/“co-work” normalized to Cowork)

Creator: AI Master (YouTube @iamAImaster) · URL: https://www.youtube.com/watch?v=zo1izxXPbQ4 · Published: not in the transcript (after the September 2026 chat/Cowork merge) · Sponsors: GoHighLevel (mid-roll, a 30-day trial link) and the creator’s own AI Master platform

AI Master’s “Cowork 2.0” beginner guide builds one folder, “Cowork Home,” and grows it into a working system: context files, global instructions, a project, a skill, scheduled tasks, connectors and browser use. Each step is a concrete workflow with a review point. Most features are covered elsewhere in the wiki (see Related). This article keeps the folder layout, the six workflows and the checks the creator does after each one. The video was recorded after Pro and Max moved to “One Claude,” where chat and Cowork merge and Claude decides whether a request is a quick answer or a task. Team and Enterprise “keep the separate switch for now.”

Key Takeaways

  • Setup first, because generic results mean Claude knows nothing about you. The folder is Cowork Home/ with context/ (what Claude should know about you), inbox/ (files you drop in) and output/ (finished files). Grant Claude this folder, not your whole Documents folder, and keep sensitive files out.
  • Three context files: aboutme.md (what you do, for whom, which tools), preferences.md (document length, headings, tables, date format, and whether Claude should ask or decide when something is unclear) and writingstyle.md (tone, a couple of real emails, banned words). Have Claude interview you with about 12 questions. Tell it not to invent anything, “otherwise it can fill your about me with a fancier job title than the one you actually have.”
  • Global instructions hold the rules every task needs (Settings → Cowork), such as “plan first” and “never delete.” Each task prompt can then be about the task only. Test the setup by asking Claude what it knows about you and how you like your documents. A mismatch usually means it lacks access to the folder.
  • First job: inbox cleanup as a setup test. Ask for sensible subfolders and readable names without losing a file. Leave the delete and plan rules out of the prompt on purpose, then check the proposed plan follows the global instructions. Afterwards you should have new folders, renamed files and a log of where everything went.
  • Receipts to spreadsheet, report and deck in one session. Put 10–15 receipts in inbox/receipts/. Ask for one total per currency, a “needs review” sheet for unreadable items with a reason, and a stop to check the numbers before anything else. In the demo Claude caught an order confirmation and an invoice for the same purchase, plus an unreadable scan. Approve the slide outline before the deck is built. Then check one number in the deck against the spreadsheet, “because copying numbers from file to file is exactly where small mistakes slip in.”
  • Course folder to study guide and quiz. Use one topic’s materials, not the whole semester. The output was key concepts, a glossary, quiz questions and references to the original PDFs. Unclear terms went to “questions for the teacher” instead of invented explanations. Claude then quizzed the user, checked answers against the sources, and kept a review list for next time.
  • A project for weekly planning. A project has its own files, instructions and memory. One created in the sidebar is saved to your account and syncs across devices. One made from a local folder stays on that computer. Put your real working pattern in the instructions (the demo used a 6-hour daily limit). When plans change mid-week, describe the change in the same project. Anything that can’t fit goes to didn't fit.md “instead of quietly disappearing.”
  • Keep exact facts in files, not shared memory. Shared memory across chat and Cowork is arriving. But for working hours or unfinished tasks, “keeping it in the file is still the safer option, because you can always open it and check.”
  • Make a skill from a real run. Run meeting notes through once, check the action-items table against the notes, fix the result, then ask Claude in the same session to turn what worked into a skill. Every fix ends up in the skill. Read the plain-text skill file, then test it in a fresh task with different notes.
  • Scheduled task form fields: name, prompt, approval setting, frequency (hourly, daily, weekly, weekdays, or manual), and optionally model and project or folder. The demo was a Monday 9:00 AI briefing across ChatGPT, Claude, Gemini and other tools. It prioritizes meaningful developments, explains why each matters, links sources, and does not invent updates in a quiet week. Use Run now to test. Scheduled research can run in the cloud with the computer off. Tasks that depend on local files “may have different requirements.”
  • Read-only daily briefing from Gmail and Calendar. Connect both, then ask for tomorrow’s briefing with an explicit rule not to send email or change the calendar. The demo found five meetings and four action items, and flagged a review ending at 11:45 against a task due at noon. Output went to a markdown file in output/.
  • Two browsers. Settings → Preferred browser → Built-in browser handled a Notion, Evernote and Obsidian comparison, including switching monthly and yearly pricing and dismissing a cookie banner. Details it couldn’t find were marked “not found.” Chrome (Claude in Chrome) handled an Amazon search with filters (under $50, 4+ stars) and product pages. It flagged color-dependent prices and a frequently returned product. Check prices and specs yourself.
  • Plugins vs skills for beginners. A plugin bundles skills, connectors and settings, and is how teams share. But “two or three skills built from your own work will do more than a pile of installed ones.”

Try It

  1. Build Cowork Home today: create the three folders, have Claude interview you for the three context files, and add your no-delete and plan-first rules to global instructions.
  2. Run the inbox cleanup and read the plan before approving. This is the habit everything else depends on.
  3. Add one workflow at a time: receipts → project → skill → scheduled task. The creator’s advice is to add a project, a skill and a schedule “only once that feels routine.”
  4. Write task prompts in three parts: what to work with, what the finished result looks like, and where the boundaries are.
  5. Remember the risk. “Claude can make mistakes, and external content can contain instructions that weren’t meant for you.” Be careful when granting access to sensitive files, email and websites.

Open Questions

  • The exact global-instructions text and task prompts were shown on screen, not read aloud, so they are not in the transcript.
  • Which plans can run cloud scheduled tasks. The video says scheduled research can run with the computer off but doesn’t say which plans or settings this needs.
  • The final dashboard. The video combines the outputs into “one simple dashboard” from a prompt that isn’t in the transcript.