Cowork Prompt Library

Twenty prompts, seven clusters — paste any one straight into Cowork's prompt bar. Each lists what to expect and the capability it exercises. Find three that fit your week, fire them, keep the ones that hit.

Most assume you've finished First 60 Minutes with Cowork. If not, start there.

Three prompts that exercise Cowork's folder access. The folder you approved during onboarding becomes the workspace.

Organize my Downloads folder by file type — group everything into subfolders by extension (PDFs, images, archives, code, etc.).

Cowork previews a grouping and asks before moving anything, flagging edge cases. Capability: folder access (read + write).

Find every PDF in this folder that looks like a duplicate of another (same file size, modified within 24 hours of each other). List the candidates.

Returns a table of candidate pairs with paths, sizes, timestamps — no deletes, you decide. Capability: folder access (read).

Rename every screenshot in this folder so the filename starts with YYYY-MM-DD based on the file's date.

A dry-run preview of old → new with conflicts flagged and a confirm step before any rename. Capability: folder access (read + write).

Three prompts that exercise the doc-coauthoring skill (or your plugin's equivalent) plus your working folder. Bring your own topic.

Draft a one-pager on [topic]. Audience: [audience]. Use the doc-coauthoring skill and save it as a Word doc in my working folder.

A structured doc (lede, three sections, close) saved with a clear filename and a link to open it. Capability: skills directory + folder access (write).

Take these rough call notes and turn them into structured action items, with owners and due dates: [paste notes].

A clean list of items with owners and dates, plus an unclear — needs your call section rather than invented detail. Capability: skills directory (productivity / task-management).

Summarize this PDF in five bullets and three questions I'd want to ask the author. [attach file]

Five bullets that capture the argument, plus three questions you couldn't have written without reading the doc. Capability: file attachment + skills directory (research-summarizer or equivalent).

Three prompts that exercise the Google Calendar and Gmail connectors. Read-only scopes cover all three; send scope is a separate decision for prompt 3.

What meetings do I have this week? Group by day and flag any with people I haven't met before.

A day-by-day list with new attendees flagged, checked against your past meeting history. Capability: Calendar connector (read).

Find every email from the last 7 days where I'm the only recipient and I haven't replied. List sender + subject.

A short, scannable table — sender, subject, date — no drafts, no auto-actions. Capability: Gmail connector (read).

Draft a polite decline to [person]'s meeting request, and propose two 30-min slots next week when I'm actually free.

A draft that sounds like you, two genuinely-free slots, and an explicit send button rather than auto-send. Capability: Gmail + Calendar connectors (read; send scope optional and explicit).

Three prompts that exercise web search and, where helpful, attached files. Best after installing a research-oriented plugin or skill.

Research [company]. Give me a one-page brief: what they do, recent news, leadership, and three angles for first contact.

A one-screen brief with clickable citations and three contact angles tied to something specific. Capability: web search + skills directory (research / sales).

Compare [Tool A] and [Tool B] on pricing, features, and support model. Flag what's not obvious from their marketing pages.

A tight three-column table with source citations and a worth knowing section for the non-obvious gotchas. Capability: web search.

Read these three customer interview transcripts and surface three themes with supporting quotes. [attach files]

Three themes, each with two or three direct quotes and a note on which transcripts it appeared in. Capability: file attachment + skills directory (research-summarizer / synthesis).

Three prompts that exercise the /schedule slash command — turning a one-off prompt into something that fires on a cadence. Caveat: routines run on the machine where Cowork is installed and awake.

/schedule every weekday at 6am — summarize yesterday's emails grouped by sender, and list the top three things I need to handle today.

A daily digest short enough to read with coffee, with a top-three callout from the most time-sensitive senders. Capability: Gmail connector + /schedule routine.

/schedule every Monday at 9am — give me a digest of all my Slack mentions from the previous week, sorted by channel and unanswered count.

A per-channel recap with an unanswered count and the message text for the highest-priority ones. Capability: Slack connector + /schedule routine.

In one hour, remind me to leave for [appointment]. Check traffic to the destination before the reminder fires.

A reminder with the current ETA, a flag if you should leave earlier, and a route link. Capability: /schedule (one-shot) + web/maps lookup.

Three prompts that exercise create_artifact — a live, queryable page that updates from your connected data, not a one-time snapshot.

Build a live page showing my pipeline this week — open opportunities by stage, with next action and last-touched date.

A pinnable page with stage columns, opportunity cards, and the next-action field — refreshable. Capability: CRM connector + create_artifact.

Build a single morning-glance page: today's calendar, unread Slack mentions, unanswered emails — all in one view.

Three tight sections in one artifact, no scrolling on a laptop screen, with counts you can act on. Capability: Calendar + Slack + Gmail connectors + create_artifact.

Build a live page tracking my active job applications: company, role, stage, last contact, next step.

A clean table you'd keep open in a tab, updatable in place or via chat, with an add a new one affordance. Capability: create_artifact (and optionally Gmail for last-contact extraction).

Two prompts that exercise the Claude in Chrome bridge — Cowork reading (or driving) a browser tab. Higher consent threshold; read carefully before granting browser scope.

Walk me through configuring a Supabase project. I'll click; you tell me what to click next, and read the page for me when I get stuck.

Contextual next-step guidance read off the actual screen, recovering when you click somewhere unexpected, never auto-clicking. Capability: Claude in Chrome bridge (read + guided assist).

Open the Vercel dashboard, navigate to my [project name] project, and read me the production env vars one at a time so I can paste them into a doc.

Each var named and read in sequence, pausing for you to paste — and never pasting values anywhere on your behalf. Capability: Claude in Chrome bridge (read).

Fire three prompts this week, keep the ones that hit, drop the rest. When a capability starts earning its keep, open the Cowork reference page for the deep dive — this page is just the on-ramp.

At Vesta Medical, Marcus (CEO) read this library three times before running a single prompt. The week he actually fired three — morning email digest, weekly Slack recap, live pipeline page — was the week Cowork became part of how he ran the company. The reading is cheap; the firing is what changes anything.