Vigyata.AI
Is this your channel?

25 Claude Cowork Tips to 10x Your Productivity

2.7K views· 71 likes· 33:38· Mar 20, 2026

🛍️ Products Mentioned (3)

💼 Business owner or operator with a team? We build AI automation systems that cut costs and scale ops — done for you: https://ryanandmattdatascience.com/ai-consultant/ 🚀 Want to make money with AI skills? Join our free community — real projects, real client strategies, and the exact stack we use: https://www.skool.com/data-and-ai Most people use Claude Co-work like a smarter chat window — but it's actually a desktop agent that can access your files, connect to your entire tool stack, run tasks while you sleep, and spin up multiple sub-agents to work in parallel. In this video, I cover 25 tips to help you get way more out of Claude Cowork. Whether you're new to Cowork or already using it daily, these tips will help you save hours, automate smarter, and stop leaving features on the table. TIMESTAMPS 00:00 Intro 00:25 Tip 1: Chat vs. Co-work — when to use each 01:08 Tip 2: Turn on memory so Claude remembers you 02:45 Tip 3: Set up global instructions 04:08 Tip 4: Find all your plugins, skills & connectors 05:14 Tip 5: Work across multiple folders at once 05:53 Tip 6: Run Co-work without a folder selected 06:25 Tip 7: Use a claude.md file for folder-specific instructions 07:49 Tip 8: Use slash commands 08:48 Tip 9: Assign tasks from your phone with Dispatch 09:56 Tip 10: Review Claude's plan before it executes 10:21 Tip 11: Duplicate sensitive files before editing 13:21 Tip 12: Keep your computer awake during long tasks 14:15 Tip 13: Queue your next task while Co-work is running 15:50 Tip 14: Set up connectors (Gmail, Notion, Calendar & more) 17:23 Tip 15: Add connectors directly in conversation 18:41 Tip 16: Install plugins to save hours 20:22 Tip 17: Find more plugins at claude.com 22:10 Tip 18: Use parallel sub-agents for big tasks 23:13 Tip 19: Schedule tasks two different ways 26:14 Tip 21: Use the Ideas section for pre-built prompts 27:37 Tip 22: Batch related work into one session 28:15 Tip 23: Edit and customize your plugin skills 29:07 Tip 24: Co-work auto-selects skills from your prompt 30:07 Tip 25: Build and update skills from scratch in chat 31:40 Bonus tips + turning skills on/off 32:04 Working around Co-work limitations with n8n OTHER SOCIALS: 🌐 Website & Blog: https://ryanandmattdatascience.com/ Ryan’s LinkedIn: https://www.linkedin.com/in/ryan-p-nolan/ Matt’s LinkedIn: https://www.linkedin.com/in/matt-payne-ceo/ Twitter/X: https://x.com/RyanMattDS *This is an affiliate program. We receive a small portion of the final sale at no extra cost to you.

About This Video

Most people treat Claude Co-work like a smarter chat window: ask a question, get an answer, move on. In this video, I show why that mindset leaves a ton of value on the table. Co-work is a desktop agent—it can access your files, connect to your tool stack, run multi-step work while you’re away, and even spin up parallel sub-agents to knock out big tasks faster. I walk through 25+ practical tips that we actually use, not theory. I cover when to use Chat vs Co-work (tokens matter), how to turn on memory, and how to set global instructions so every session behaves the way you want. Then we get into the workflow stuff that saves hours: managing plugins/skills/connectors from the “Customize” briefcase, working across multiple folders, running Co-work with no folder selected, and using a folder-level claude.md for project-specific rules. I also show slash commands, Dispatch for assigning tasks from your phone, reviewing Claude’s execution plan before destructive actions, duplicating sensitive files, and keeping your computer awake so scheduled/long tasks don’t die. On the automation side, we talk connectors (Gmail/Notion/Calendar), installing and editing plugins, finding additional plugins online, using parallel sub-agents, scheduling tasks two ways, using the Ideas library for pre-built prompts, and batching related work into one session to avoid reloading context. If you want Co-work to feel like an ops teammate instead of a chatbot, these tips are the playbook.

Frequently Asked Questions

🎬 More from Ryan & Matt Data Science