Copy-paste prompts and complete setups from people who use Cowork every day. No theory, just what works.
CEO or founder managing multiple roles. You have 90 seconds before your day explodes. You need to queue work from anywhere, not just at your desk.
Create: Active Work → Today's Work. This is where Claude queues tasks and outputs pile up. You review from this single folder.
Connect your email and calendar. Claude can now read incoming messages and your day's schedule to prioritize intelligently.
Install Claude on your phone. As of the July 2026 mobile release, you can start the whole session from your phone at 6 AM and it runs in the cloud — your Mac can be closed. The catch: a cloud session can't touch your local desktop folders. Route these outputs to a connector (Drive, Notion) if you want to review them on your phone. See the note below.
Prioritized email drafts ready to send. A content calendar in HTML with story ideas, sourced and themed. Files organized by project and task type, all before you sit down at your desk.
Inspired by Christian Pean MD, Techy Surgeon
Anyone starting with automation. You don't need ten tasks. Start with three. Let them run for a week and feel the difference before you add anything else.
Connect your email and calendar so Claude can read them as part of each scheduled task.
Make sure Cowork has permission to run scheduled tasks. This happens during setup, but verify in Settings if tasks don't fire.
A morning HTML briefing with your day's priorities. Pre-meeting prep with talking points and questions. End-of-day summary with follow-ups flagged and ready for tomorrow.
0 9 * * 1-5 for weekdays at 9 AM, 30 8 * * 1 for Mondays at 8:30 AM.
Inspired by Christian Pean MD, Techy Surgeon
Consultant, lawyer, agency professional. You produce the same type of deliverable repeatedly. You want consistent quality and fast turnaround.
Add your report template (.docx). Include 2 strong past examples as reference. Add the client brief and any reference docs. Include project instructions: "Include executive summary. Never exceed 15 pages. Structure: summary → findings → recommendations → next steps → appendix. Output as .docx."
A templated Word document with executive summary, findings, recommendations, next steps, and appendix. All formatted to your style, based on the template and examples you provided.
Inspired by Ruben Hassid, How to AI
Founder prepping for investor meetings. Analyst sizing a market. Sales rep researching accounts. Anyone who needs research they can actually trust.
Most people ask Claude to 'research X' and get a generic summary with no sources. This approach uses a recursive research loop, the same methodology behind dedicated research skills that produce 15-30 page cited dossiers. The difference is structure: Claude decomposes the research into sub-questions, probes sources in priority order, tracks confidence on every claim, and separates evidence from inference.
| Step | What Happens |
|---|---|
| Probe | Search sources in priority order: official site → social channels → reviews → press/third-party |
| Decompose | Break each section into 3-6 sub-questions. No claims without citations. |
| Recurse | For each sub-question, inspect sources, write a mini-brief with citations + confidence |
| Synthesize | Combine mini-briefs into the final section. Resolve conflicts between sources. |
Inline citations with source, date accessed, and confidence (High / Medium / Unconfirmed). No naked claims.
Company-stated claims vs. third-party corroboration vs. inference. Each labeled explicitly.
If not publicly disclosed, write "No public disclosure found as of [date]" instead of guessing.
Person Research:
Company Research:
Industry/Market Research:
A 10-25 page Word document with inline citations, confidence scores, a source pack (12-25 annotated links), comparison tables, and an executive summary. The output quality depends on the prompt structure, the recursive loop and evidence rules are what separate this from a generic 'research X' request.
Research methodology by Steve Gustafson
Anyone with data who needs visuals fast. You have the data. You don't care about the technical implementation. You want a dashboard you can share.
That's it. No plugins, no connectors, no special configuration. Just add your data file to the project folder.
A single-file HTML dashboard with Chart.js, dropdown filters, summary cards, responsive design. Fully interactive. Share via email or Slack. Works in any browser.
Claude can touch a spreadsheet or a deck several different ways. Reaching for the wrong one wastes time. Use this map, and see the full Claude in Office guide for the why behind each.
| You want to… | Use | Why this one |
|---|---|---|
| Edit a live workbook / model that already exists | Claude in Excel (add-in) | Only this edits real cells and traces dependencies in your open file. |
| Generate a fresh, formatted workbook from data or a brief | Cowork xlsx skill | Builds a new .xlsx from scratch with formulas and styling, no add-in needed. |
| Edit / restyle an existing deck slide-by-slide | Claude in PowerPoint (add-in) | Works inside your template; keeps layouts and master styles intact. |
| Build a new deck from data, with a narrative | Cowork pptx / exec-deck skill | Generates a full .pptx from a spreadsheet; the skill bakes in the blueprint→polish method. |
| A shareable, interactive view of a dataset | CSV → HTML dashboard | One self-contained HTML file with filters and charts, opens in any browser. |
| A designed, on-brand deck or page | Claude Design | Image-led visual polish and working code, when look-and-feel is the point. |
| A finished invoice / report / receipt to send | PDF agent / invoice-pdf skill | Layout, totals, and structure handled; returns a shareable PDF. |
Executive managing multiple domains. Anyone who wants the complete automated intelligence system. Start with three tasks. By week four, you have a personal operating system.
This isn't a single workflow, it's what happens when you combine the previous five into a system. Start with the Essential Three (Workflow 2). Add one domain-specific task per week. By week four, you have a personalized operating layer that handles your morning briefing, meeting prep, recurring research, deliverable production, and end-of-day wrap-up, without you re-explaining anything.
Morning briefing, meeting prep, evening debrief. Just these. Get comfortable with the rhythm. Notice what changes in your day.
Pick from the menu below based on your role. One task only. Don't add more until you see the value from this one.
By now you see which automations actually save time vs. create noise. Add the second one based on what worked.
You now have a personalized operating system. Iterate weekly. Remove what doesn't work. Add what does.
Scan emails for stale sales conversations. Flag deals going cold. Alert on inactivity over 2 weeks.
Monitor 3-5 competitor sites for pricing, features, blog, and hiring changes. Deliver as a weekly summary.
Compile customer emails and tickets by priority. Flag escalations. Summarize by issue type.
Scan relevant government sources weekly for policy changes. Alert on changes that affect your business.
Scan emails for invoices. Extract amounts, vendors, dates. Flag items over your threshold for review.
A complete context file + recommended scheduled task library tailored to your actual work. Over time, scoped memory learns your patterns and the outputs get sharper. By week 8, Claude knows your priorities better than most people around you.
Inspired by Christian Pean MD, Techy Surgeon
Founder building the board update. Consultant turning a model into a client readout. Anyone who has the numbers and needs a deck that tells the story, not a wall of pasted charts.
Drop the source .xlsx or .csv into the project folder, or open it directly with the Claude PowerPoint add-in.
Add a brand template (.pptx) and one strong past deck as a reference so Claude matches your house style.
"Board audience. Max 12 slides. Every slide scannable in five seconds." A one-line brief sharpens every step that follows.
A branded .pptx where the deck has an argument, the charts are sourced from your actual data, and the headlines state conclusions instead of labeling axes. A first draft you'd edit, not rebuild.
Method adapted from the Claude × Office playbook (Guillermo Flor, PMF) • structured by Steve Gustafson
Anyone who runs back-to-back calls and loses the thread on follow-ups. Consultants who owe every prospect a recap. Founders who decide five things in a meeting and remember two by evening. The email that should go out in ten minutes instead goes out in three days, or never.
Claude writes a profile of how you actually email, then follows it every time. You build it once and reuse it forever. The prompt is below.
Download it at granola.ai. It's a notepad, not a bot, nothing joins your call. It transcribes in the background on Zoom, Meet, and Teams, then hands you clean notes when the meeting ends. In Claude, go to Settings → Connectors, search for Granola, and connect it. Now Claude can read any meeting you've had.
Settings → Connectors → Gmail. This is how Claude reads your sent mail to learn your voice, and drops the finished draft where you'll find it.
First, build your voice profile (once):
Save that output as project instructions. This is the step that makes your emails sound like you and not like a chatbot.
Then, after every meeting:
A draft sitting in Gmail, attendees already in the To field, written in your voice: what you decided, who owns what, the single next step. You read it once and send. The email is waiting before your coffee gets cold.
Method from Ruben Hassid's meeting-email framework (How to AI) • Granola is a third-party tool (granola.ai) • structured by Steve Gustafson
Every workflow above teaches you how to build something. Almost nothing online teaches you what to do when one quietly breaks. Three failure modes cover most of it. Here is each, and the fix.
Inspired by Nick Saraev, Maker School
You don't need all seven. Pick the workflow closest to your daily pain. Set it up. Run it for a week. Then come back for the next one.