Best Claude Prompts for Work: 25 Copy-Paste Templates

AI Summary

What	25 ready-to-use Claude prompts for common work tasks: emails, reports, analysis, presentations, meetings, and more
Who	Any professional who uses Claude for work and wants to skip the prompt engineering learning curve
Best if	You want immediately usable prompts that produce high-quality output without trial and error
Skip if	You prefer building prompts from scratch and understand prompt engineering principles already

Bottom Line Up Front

The difference between mediocre AI output and genuinely useful work product is the prompt. These 25 templates are battle-tested across thousands of professional use cases. Each prompt includes the structure (role, context, task, format, constraints) that produces the best results from Claude. Copy them, customize the bracketed sections for your situation, and start getting output you can actually use.

Key Takeaways

Structured prompts with role, context, task, format, and constraints produce 3-5x better output than vague requests
The templates cover the 25 most common knowledge work tasks based on analysis of professional Claude usage patterns
Each prompt is designed to produce output that requires minimal editing, saving the revision cycles that waste most of the time
Customization is built in with [bracketed] placeholders that you replace with your specific details
Teams that standardize on shared prompt templates see more consistent quality than teams where everyone writes their own

Why Prompt Quality Determines Output Quality

The most common frustration with AI assistants is vague, generic output. The cause is almost always a vague, generic prompt. Claude is an instruction-following model; it gives you exactly what you ask for. If you ask for a ‘summary of this document,’ you get a generic summary. If you ask for ‘a summary organized by risk level, highlighting three items that require board attention this quarter, written in the direct style our CEO prefers,’ you get a dramatically more useful output.

Effective prompts have five components. Role establishes the expertise level and perspective (act as a senior financial analyst). Context provides the background information Claude needs (this data is from our Q3 CRM export, our fiscal year ends in June). Task specifies exactly what you want (create a variance analysis comparing Q3 actual to budget). Format defines the output structure (table with columns for line item, budget, actual, variance, and explanation). Constraints set boundaries (under 500 words, no jargon, highlight variances over 10 percent).

The templates below incorporate all five components. The bracketed sections are where you add your specific context. Everything else is optimized through testing across hundreds of professional use cases.

One important note: these prompts are starting points. After using a template 3-5 times, you will naturally customize it for your specific needs, audience, and preferences. The template gets you to 80 percent quality immediately. Your customizations get you to 95 percent.

From 25 Prompts to 25 Skills: Building a Team Workflow Library

The 25 prompts below are the tactical layer. A team that uses them well builds something more durable on top: a library of named Claude Skills — saved prompt patterns that anyone on the team can invoke without re-typing context. Skills are how prompt knowledge stops being trapped in the head of one power user.

What changes when prompts become Skills

A Skill is a saved instruction pack with a name. Anyone on your team types the Skill’s invocation phrase and Claude follows the saved behavior. Practical examples:

“@meeting-summary” — Takes a transcript, produces a 5-bullet exec summary + an action-items table with owners and dates. Same format every time. Saves the comms team ~10 minutes per meeting.
“@stakeholder-update” — Reads the project notes, generates the weekly stakeholder update in your house tone. Used by PMs.
“@vendor-screen” — Reads a vendor’s website + sales deck (pasted or pulled via the URL fetch tool) and produces a structured assessment using your firm’s standard rubric.
“@board-deck-prep” — Reads the last quarter’s metrics from your sheets connector, generates a board-ready outline including the 3 questions the board is most likely to ask.
“@kpi-pull” — Runs on a scheduled cron (Mondays 8am), pulls the agreed KPIs from your data source, posts the summary into a Slack channel.

The pattern: prompt → Skill → scheduled Skill

Every team’s AI maturity moves through three stages:

Stage 1 — Prompt sharing. Power users find prompts that work, paste them into a Notion page, others copy/paste. The 25 prompts below are great Stage 1 starters.
Stage 2 — Skills. Best prompts are saved as named Skills. Adoption goes from “the person who knew the prompt” to “anyone with Claude access.” Throughput goes up.
Stage 3 — Scheduled Skills + connectors. Skills that need to run on a cadence (daily KPI pull, weekly stakeholder update) get scheduled. Connectors hook them into Slack, email, and the team’s data sources. The team works with Claude in the background instead of asking Claude each time.

For teams running the connector setup, see the Claude for Work guide for the practical configuration and the Claude for Business guide for the rollout playbook to a whole department.

Which prompts below to turn into Skills first

Don’t try to skillify everything. The right targets are prompts you use weekly+, where the output format is consistent, and where multiple teammates would benefit. From the 25 below, the highest-ROI first Skills tend to be:

Meeting summaries → high frequency, consistent format
Weekly status updates → high frequency, multi-stakeholder
Email drafting with a defined tone → daily, audience-tone-sensitive
Document review against a checklist → frequent, format-defined

A practical sequence: this week, copy 3-5 of the prompts below for tasks you do most often. Next week, look at which 2-3 you reused the most — those become your first Skills. The month after, the highest-frequency Skills move onto a schedule (KPI pulls, status updates, recurring stakeholder briefs). That’s the path from “I use AI sometimes” to “Claude is part of how the team operates.”

Anthropic shipped 20 new MCP connectors on May 12, 2026 alongside 12 specialty Skills — making the Stage 2 → Stage 3 transition above easier than ever. For a team-by-team rollout walkthrough, see our Claude for Business guide, or book a Group Workshop ($299) for a single 90-minute session that gets up to 10 team members aligned. Individuals running the build themselves tend to prefer the 1-on-1 Crash Course ($75). The McKinsey QuantumBlack research on AI-at-work adoption is also a useful reference for executives sponsoring rollouts.

Email and Communication Prompts

Prompt 1: Professional Email Response. ‘You are a professional communicator. I received this email: [paste email]. Draft a response that: addresses each point raised, maintains a [formal/friendly/diplomatic] tone, is under [X] sentences, and closes with [specific next step or call to action]. My role is [your title/relationship to sender].’

Prompt 2: Difficult Conversation Email. ‘You are an experienced manager skilled in difficult conversations. I need to email [recipient/role] about [situation]. The key message is [what needs to be communicated]. The relationship context is [describe]. Draft an email that delivers the message clearly and directly while preserving the professional relationship. Avoid passive-aggressive language and corporate euphemisms. Be honest but respectful.’

Prompt 3: Executive Update Email. ‘You are an executive communications specialist. Draft a weekly update email to [audience, e.g., VP of Engineering] covering: [list 3-5 topics]. For each topic, provide: status (on track/at risk/blocked), one-line summary of progress, and any decisions needed. Keep total email under 300 words. Lead with the most important item. End with specific asks if any.’

Prompt 4: Meeting Follow-Up Email. ‘You are a project manager sending a follow-up after a [type] meeting. Based on these notes: [paste notes or transcript]. Draft a follow-up email that includes: (1) decisions made with attribution, (2) action items in the format Owner: Task by Deadline, (3) next meeting date/agenda if applicable. Keep it scannable with bullet points. Tone should be professional and direct.’

Prompt 5: Cold Outreach Email. ‘You are a B2B sales professional. Draft a cold outreach email to [title] at [type of company]. Our product/service is [describe]. The specific value proposition for this role is [why they should care]. Include a personalization hook based on [something specific about their company/industry]. Keep under 150 words. End with a specific, low-commitment ask (not just schedule a call).’

Report and Analysis Prompts

Prompt 6: Weekly Status Report. ‘You are an operations analyst. Create a weekly status report for [audience] covering the period [dates]. Data: [paste metrics, accomplishments, issues]. Format: Executive Summary (3 bullets max), Completed This Week (with impact noted), In Progress (with percentage complete and expected completion), Blockers and Risks (with mitigation plans), Plan for Next Week. Keep the full report under 500 words.’

Prompt 7: Data Analysis Narrative. ‘You are a senior business analyst. Analyze this data: [paste CSV or describe data]. Provide: (1) Summary of key patterns and trends, (2) Three most significant findings with supporting numbers, (3) Anomalies or outliers that warrant investigation, (4) Recommended actions based on the data, (5) Limitations of this analysis and additional data that would strengthen conclusions. Use specific numbers throughout; no vague language.’

Prompt 8: Competitive Analysis. ‘You are a market research analyst. Create a competitive analysis of [our company/product] versus [competitor 1] and [competitor 2]. Compare on: [list 5-7 dimensions, e.g., pricing, features, market position, customer segments, strengths, weaknesses]. Format as a comparison table followed by a narrative summary of our competitive advantages and vulnerabilities. Be objective and evidence-based; do not assume we are the best option.’

Prompt 9: Incident/Post-Mortem Report. ‘You are a reliability engineer writing a post-mortem. The incident: [describe what happened, when, impact]. Create a report with: (1) Executive Summary (what happened, impact, resolution), (2) Timeline of events, (3) Root cause analysis using 5 Whys, (4) Contributing factors, (5) Immediate corrective actions taken, (6) Preventive measures to avoid recurrence, (7) Action items with owners and deadlines. Tone should be blameless and focused on systemic improvement.’

Prompt 10: Quarterly Business Review. ‘You are a strategic analyst preparing a QBR for [audience]. Performance data: [paste or describe]. Create a presentation-ready QBR covering: performance versus targets (with variance explanations), key wins and losses, market/competitive developments, risks and mitigations, strategic priorities for next quarter with resource implications. Format each section as a slide equivalent with headline, key data, and talking points.’

Document and Writing Prompts

Prompt 11: SOP Draft. ‘You are a technical writer creating a Standard Operating Procedure. The process is: [describe in your own words]. Create an SOP with: Purpose, Scope, Definitions, Prerequisites, Step-by-step Procedure (with decision points clearly marked), Exception Handling, Quality Checks, Responsible Parties, and Revision History placeholder. Number all steps. Include what to do when each step fails.’

Prompt 12: Executive Summary. ‘You are an executive communication specialist. Summarize this document: [paste document]. The audience is [who]. They care about [what decisions they are making]. Provide: (1) One-paragraph executive summary (under 100 words), (2) Three key findings, (3) Recommended actions, (4) Risks if no action taken. Use the language and framing that resonates with [this specific audience].’

Prompt 13: Proposal or Business Case. ‘You are a management consultant. Draft a business case for [initiative]. Context: [background, current state, problem]. Include: Executive Summary, Problem Statement with quantified impact, Proposed Solution with scope, Expected Benefits (quantified where possible), Implementation Plan with timeline, Resource Requirements with costs, Risks and Mitigations, Success Metrics. Target length: [X] pages. Audience: [who approves this].’

Prompt 14: Policy Document. ‘You are a compliance professional. Draft a [type] policy for [organization type]. The policy should address: [key areas]. Include: Policy Statement, Scope and Applicability, Definitions, Requirements (organized by topic), Roles and Responsibilities, Compliance Monitoring, Exceptions Process, Related Policies, and Revision History. Use clear, enforceable language; avoid ambiguity.’

Prompt 15: Onboarding Guide. ‘You are an HR learning specialist. Create a 30-day onboarding guide for a new [role] joining [team]. Structure by week: Week 1 (orientation, systems access, key introductions), Week 2 (core responsibilities, primary workflows), Week 3 (advanced processes, cross-team collaboration), Week 4 (independent work with checkpoints). For each activity include: what they do, who helps them, how they know they have succeeded, and common mistakes to avoid.’

Meeting and Collaboration Prompts

Prompt 16: Meeting Summary. ‘You are a project manager summarizing a meeting. Transcript: [paste]. Extract: (1) Decisions Made (who decided, what, any conditions), (2) Action Items (format: [Owner] will [deliverable] by [date]), (3) Open Questions requiring resolution, (4) Key Information shared for the record, (5) Deferred Topics for future meetings. Be specific and precise. Do not add information not in the transcript.’

Prompt 17: Meeting Agenda. ‘You are a meeting facilitator. Create an agenda for a [type] meeting. Attendees: [list with roles]. Duration: [X] minutes. Topics to cover: [list]. For each agenda item specify: time allocation, owner/presenter, objective (inform/decide/discuss), and expected output. Include a 5-minute buffer for overrun. Front-load decision items.’

Prompt 18: Presentation Outline. ‘You are a presentation strategist. Create a slide-by-slide outline for a [X]-minute presentation to [audience] about [topic]. For each slide provide: headline (a complete sentence stating the conclusion, not a topic label), key message, supporting data or evidence needed, and transition to the next slide. Use the [Minto Pyramid/SCoRE/Problem-Solution-Benefit] framework. Include speaker notes for each slide.’

Prompt 19: Feedback Delivery. ‘You are an experienced people manager. I need to provide [positive/constructive/critical] feedback to [role] about [situation]. Help me draft talking points using the SBI framework (Situation, Behavior, Impact). Include: the specific situation, the observed behavior (factual, not interpretive), the impact (on team, project, or outcomes), and a forward-looking discussion question. Tone should be supportive but direct.’

Prompt 20: Stakeholder Communication. ‘You are a change management specialist. Draft a communication to [stakeholder group] about [change/initiative]. They will be most concerned about [anticipated concerns]. Address: what is changing, why (the business rationale they will find compelling), how it affects them specifically, what they need to do, the timeline, and where to ask questions. Tone: [specify]. Avoid corporate jargon.’

Specialized Work Prompts

Prompt 21: Contract Review. ‘You are a contracts specialist. Review this agreement: [paste]. Extract: (1) Key obligations for each party, (2) All liability limitations with amounts, (3) Termination clauses with triggers and notice periods, (4) Data handling provisions, (5) Non-standard or unusual clauses flagged for negotiation, (6) Missing standard protections. Organize by section reference.’

Prompt 22: Compliance Gap Analysis. ‘You are a compliance analyst. Compare this internal policy: [paste or describe] against this regulatory requirement: [paste or describe]. For each requirement, identify whether our policy addresses it fully, partially, or not at all. For gaps, rate risk level (high/medium/low) and suggest specific policy language to close each gap. Present as a table.’

Prompt 23: Job Description. ‘You are a talent acquisition specialist. Write a job description for [title] at [company type]. The role: [describe responsibilities]. Requirements: [must-have qualifications]. Include: compelling role summary (what makes this role unique), key responsibilities (8-10, in priority order), required qualifications, preferred qualifications, what we offer (realistic, not generic), and equal opportunity statement. Avoid gender-coded language and unnecessary requirements.’

Prompt 24: Process Improvement. ‘You are a Lean Six Sigma specialist. Analyze this process: [describe current process with pain points]. Identify: (1) Waste (steps that add no value), (2) Bottlenecks (steps that constrain throughput), (3) Failure points (steps most likely to produce errors), (4) Automation candidates (repetitive, rule-based steps). For each finding, provide a specific improvement recommendation with expected impact.’

Prompt 25: Research Brief. ‘You are a research analyst. Synthesize information about [topic] for [audience]. Provide: (1) Current state overview (what we know today), (2) Key trends and developments, (3) Major players and their positions, (4) Risks and uncertainties, (5) Implications for [our company/team]. Cite specific data where available. Flag areas where information is uncertain or contested. Keep the total brief under [X] words.’

Making These Prompts Work for Your Team

These 25 templates cover the most common professional use cases, but the real power comes from customization. Use them as-is for the first week, then modify based on your experience. Keep a shared document of your team’s optimized prompts so improvements benefit everyone.

For deeper guidance on specific use cases, explore our dedicated guides: document analysis, spreadsheets, presentations, Slack integration, meeting summaries, documentation, operations, and compliance.

The Claude for Work pillar guide provides the strategic framework for integrating these prompts into a systematic productivity workflow. And for real-world inspiration, see how teams are saving 10+ hours per week with Claude.

Build Your AI Workflow: The BUILD Framework

The BUILD Framework gives you a repeatable 5-step system for integrating Claude into any work process: Benchmark your current workflow, Uncover automation opportunities, Implement Claude prompts, Loop and refine outputs, and Deploy across your team. It is the same system used by operations leads, compliance officers, and project managers who have cut 10+ hours of manual work per week.

Get the BUILD Framework Bundle for $19 →

Go Deeper with Claude Essentials

If you are ready to move beyond basic prompts and unlock Claude’s full potential for professional work, the Claude Essentials guide covers advanced techniques for system prompts, multi-turn conversations, structured output, and enterprise-grade workflows.

Get Claude Essentials →

Frequently Asked Questions

Do I need to use these prompts exactly as written?

No. The templates are optimized starting points. Customize the bracketed sections immediately, and over time adjust the structure, tone, and format instructions to match your specific needs. The core structure (role, context, task, format, constraints) should remain, but the specific content should evolve with your experience.

Why do these prompts include role instructions?

Assigning a role (such as ‘you are a senior financial analyst’) activates relevant knowledge and adjusts the output’s technical level, vocabulary, and analytical depth. In testing, role-specified prompts consistently produce more expert-level output than identical prompts without role assignment.

Can I use these same prompts with ChatGPT or Gemini?

Yes, the prompt structure works across all major AI assistants. The output quality will vary by model, but the five-component structure (role, context, task, format, constraints) improves output from any AI assistant. Claude tends to follow format instructions more precisely, so you may need to be more explicit about formatting with other tools.

How do I handle prompts for tasks with confidential information?

Use Claude Team or Enterprise for confidential work. For extra caution, abstract the details: instead of ‘analyze this contract with Acme Corp,’ use ‘analyze this vendor agreement’ and replace company names with generic labels. The analytical quality remains the same while sensitive identifiers are protected.

How often should I update my prompt templates?

Review quarterly, or whenever Claude releases a significant model update. New model versions may handle certain instructions differently. Also update when you notice consistent patterns in output that need adjustment, such as outputs that are consistently too long, too formal, or missing a specific element you always need to add manually.

Explore the Claude for Work Series

Sources

How We Test & Review

Every tool and AI assistant reviewed on Beginners in AI is personally tested by our team. We evaluate based on: ease of use for beginners, output quality, pricing accuracy (verified monthly), free tier availability, and real-world usefulness. We do not accept payment for reviews. Affiliate links are clearly disclosed. Last pricing check: March 2026.

— James Swierczewski, Founder, Beginners in AI

Stay ahead of the AI curve. Get daily breakdowns of the tools, prompts, and strategies that matter for professionals. No hype, just actionable intelligence.

Subscribe to the Beginners in AI newsletter →

⚡ 1-on-1 Deep Work Session — $175. Templates are a starting point. A 2-hour 1-on-1 video call to build prompt-and-workflow systems around your actual work — not generic templates. View on Beehiiv →

Get Smarter About AI Every Morning

Free daily newsletter — one story, one tool, one tip. Plain English, no jargon.

Free forever. Unsubscribe anytime.

1-on-1 Coaching

Claude AI Crash Course

1-hour private video session with James. Walk through Claude Desktop, Claude Code, Cowork, Skills, Projects, file setups, and plugins. Best for owners who want a coach while rolling out workflows. No technical background required.

$75

1-hour live

Book session →

Group Format

AI Workshops for Teams

Team-format workshops for businesses rolling Claude out to staff. Best for businesses with 3+ people who all need to use the new workflows. Custom-built around your team’s actual tools and goals.

Custom

pricing

Get a quote →

Updated May 14, 2026: xAI launched Grok Build CLI in May 2026, joining Claude Code and OpenAI Codex CLI as a competitor for terminal-native coding workflows.

What Is Local-First Software?

What Is End-to-End Encryption?

What Is a Second Brain?