Claude CoWork for Executive Assistants

What is Claude CoWork?

Claude CoWork is the practice of using Claude as a context-aware executive support partner inside your daily workflow. It is not just "ask AI to write an email." It is setting Claude up so it understands how your executive works, what gets escalated, what can be delegated, and how to turn a flood of context into a clean next step.

Claude-native prompts. The prompts in this guide use Claude's native XML tag structure (<context>, <instructions>, <format>, <avoid>) for more precise, consistent output. These tags help Claude parse your intent with less ambiguity. They also work in ChatGPT, but they are optimized for Claude.

This is where executive assistants are getting the most value from AI right now: inbox triage, meeting prep, follow-up drafting, and daily priority planning. The weak version of an AI assistant is a fancy note taker. The useful version helps you reduce context-switching and create momentum without losing judgment.

Install the Executive Assistant Plugin

This guide works on three Claude surfaces. The plugin is the fastest path on two of them. Pick whichever you use:

If you're on Cowork (desktop or mobile app)

Claude Cowork is Anthropic's agentic workspace — Claude completes work autonomously and returns finished deliverables. The Executive Assistant plugin packages the workflows below as native skills and slash commands.

1. Open the Cowork plugin directory in your desktop app.
2. Filter by Cowork, search for "Executive Assistant", and click Install.
3. The plugin's slash commands and ambient skills are now available in any Cowork task.

If you don't see the plugin in the directory yet, install via custom marketplace: paste https://github.com/alexclowe/awesome-claude-cowork-plugins in your Cowork plugin settings.

If you're on Claude Code (CLI)

Install from your terminal:

claude plugin add alexclowe/awesome-claude-cowork-plugins/executive-assistant

The plugin's slash commands and skills load on next session.

If you're on Claude.ai (web chat only)

Plugins aren't directly installable on the web chat surface. You have two options:

1. Use the prompts in this guide directly in a Claude Project (covered in the next section). Same outputs, more typing.
2. Upload the plugin's skills as a zip via Settings → Features → Custom Skills (Pro/Max/Team/Enterprise plans). Higher friction; only worth it if you want the auto-activating skills, not the slash commands.

What the plugin gives you (any surface)

Slash command	What it does
/inbox-triage	Sort the inbox into priorities, recommended replies, and messages that truly need escalation
/meeting-brief	Create concise prep briefs with context, stakeholders, objectives, risks, and talking points
/follow-up-draft	Turn meeting notes into recap emails with action items, owners, deadlines, and unresolved questions
/daily-priorities	Build a daily action plan from meetings, deadlines, inbox pressure, and executive preferences

Auto-activating skills (no command needed — Claude applies them when relevant):

• Executive Operations — Calendar judgment, priority triage, stakeholder coordination, travel logistics, and meeting preparation
• Communication & Coordination — Inbox drafting, concise summaries, action-item tracking, tone matching, and polished follow-up communication

The plugin works standalone for one-off tasks. Pair it with the surface-specific setup below for persistent context across every task — that combination is the full Claude CoWork setup.

Setting Up Claude for Executive Support Work

Surface note: The Project setup below is for claude.ai web users. Cowork users have their own task-context mechanism (set context once when starting a Cowork task). Claude Code users get the plugin's ambient skills automatically — no Project setup needed. The workflows themselves are surface-agnostic — paste the prompts wherever you're working. The best setup is a dedicated Claude Project for executive support.

Step 1: Create a Project. In Claude, create a Project called something like "Executive Support Desk."

Step 2: Add custom instructions. Use something like:

You are my executive support assistant. Here is my working context:

<executive-profile>
- Executive role: [CEO / COO / Founder / Chief of Staff support]
- Priorities this quarter: [top 3 priorities]
- Communication style: [brief, direct, warm, formal, etc.]
- Escalation rules: [what should always be surfaced]
- Typical stakeholders: [board, customers, hiring managers, leadership team]
</executive-profile>

<working-rules>
- Assume I need concise answers first, details second
- Distinguish between executive work and coordination work
- When drafting replies, match tone without sounding robotic
- Always separate confirmed decisions from assumptions
- Always call out deadlines, owners, and unresolved questions
- Never invent context that was not provided
</working-rules>

Step 3: Upload reference material. Add your executive's preferred email examples, recurring meeting templates, planning docs, and any internal style guides.

Step 4: Stay inside this Project. The value comes from keeping your context persistent.

Your Top 5 Workflows with Claude

1. Inbox Triage

The biggest daily win is deciding what deserves the executive's attention and what does not.

<task>Triage this inbox summary for a CEO.</task>

<context>
- Executive only wants board, customer, hiring, and major financial items surfaced
- Everything else should be delegated or drafted if safe
- Tone should be concise and practical
</context>

<input>
- Board member requesting pre-read materials before tomorrow's call
- Customer escalation from enterprise account
- Recruiter asking for interview availability
- Vendor contract follow-up
- Internal budget question
- Three newsletters
</input>

<instructions>
- Group into: needs executive attention, delegate, can wait
- Draft short replies where useful
- Flag anything risky or sensitive
- Keep the output skimmable
</instructions>

Before Claude: 30-45 minutes to sort, summarize, and draft.
After Claude: 5-10 minutes to review and send.

2. Meeting Briefs

Meeting prep is one of the highest-leverage uses of AI for executive assistants.

<task>Create a prep brief for tomorrow's Q2 planning meeting.</task>

<context>
- Participants: COO, Head of Sales, Finance Director
- Topic: pipeline is behind target; hiring plan may need to be reduced by 10%
- Board update is due Thursday
</context>

<instructions>
- Summarize why this meeting matters now
- List likely friction points
- Give 5 talking points and 5 questions the executive should ask
- End with a prep checklist
</instructions>

Before Claude: 20-30 minutes chasing context.
After Claude: 5 minutes to sanity-check and personalize.

3. Follow-Up Drafts

The useful output is not the transcript. It is the recap that creates motion.

<task>Draft a follow-up email and action tracker from these notes.</task>

<notes>
- Pause two vendor evaluations
- Move roadmap review to next Wednesday
- Finance to model three headcount scenarios by Friday
- Need customer impact note before leadership review
</notes>

<instructions>
- Separate confirmed decisions from open questions
- Create an internal action table with owners and deadlines
- Write a polished recap email from the executive
- Keep it concise and easy to scan
</instructions>

4. Daily Priority Planning

This is where Claude becomes a real CoWork partner instead of a writing toy.

<task>Build today's priorities for a founder.</task>

<context>
- Investor prep at 8:30
- Three hiring interviews
- Customer escalation at 2:00
- Dinner with partner prospects
- 37 unread emails
</context>

<instructions>
- Give the top 5 priorities
- Suggest what to delegate
- Flag anything unrealistic
- Show the order of operations
</instructions>

5. Stakeholder Drafting

Executive assistants often need to write in multiple tones in the same hour.

<task>Draft three versions of this message.</task>

<context>
Need to move a leadership sync because the executive was pulled into a customer issue.
Recipients:
- Internal leadership team
- External partner
- Candidate in interview loop
</context>

<instructions>
- Keep each version appropriate to the audience
- Preserve the same core facts
- Sound like a human, not a template
</instructions>

Prompt Engineering Tips for Executive Assistants

1. Tell Claude what gets escalated. Otherwise it will summarize everything with equal weight.

2. Distinguish decision support from drafting. "Write the email" and "tell me whether this needs the executive" are different jobs.

3. Ask for owners and deadlines explicitly. If you do not ask, most AI output stays fuzzy.

4. Use examples of the executive's tone. Even two or three good emails improve drafting quality significantly.

5. Ask Claude to separate certainty from assumption. This is especially important in scheduling and follow-up work.

6. Keep inputs de-identified where possible. Use roles, not private personal details, unless your policy explicitly permits the tool.

Privacy & Discretion

Executive support work often includes sensitive information. Be stricter than average.

• Do not paste personal data, compensation details, legal matters, health details, or board-sensitive information unless your organization's AI policy explicitly allows it.
• Review every draft before sending. Claude should speed up judgment, not replace it.
• Treat travel, security, investor, and personnel topics as higher-risk categories.
• If you are using Claude for external communication, confirm names, dates, and commitments before the message leaves your outbox.

Going Further

• Read Best AI Tools for Executive Assistants in 2026
• Explore the Executive Assistant Plugin for Claude
• Browse the full resource library for more workflow templates