640+ Best Google Gemini Prompts
for Gemini 1.5 Pro (2025)

You have access to a large corpus of research material I'm about to provide. Your task is to perform expert-level synthesis across ALL documents simultaneously — something only possible with your extended context window. After reading all materials, provide: 1. CONSENSUS MAP: Topics where 3+ sources agree (cite which sources, exact agreements) 2. CONTRADICTION LOG: Every place sources disagree. For each contradiction: state both positions, identify which has stronger methodology/evidence, and flag if the contradiction is unresolved in the literature 3. TEMPORAL PROGRESSION: How has thinking on [TOPIC] evolved chronologically across these sources? 4. MISSING PERSPECTIVES: What important viewpoints, demographics, or methodologies are NOT represented in this corpus? 5. STRONGEST CLAIMS: The 5 claims with the most cross-source support — with citation chain 6. WEAKEST CLAIMS: 3 claims that appear in sources but have thin evidential support 7. META-ANALYSIS SUMMARY: If you had to write the abstract for a meta-analysis of this corpus, what would it say? Be a scientist, not a journalist. Distinguish correlation from causation. Note sample sizes where relevant. Topic I'm researching: [YOUR RESEARCH TOPIC] [PASTE ALL RESEARCH MATERIALS BELOW — Gemini can handle up to 1M tokens]

Act as a senior market research analyst at McKinsey. Conduct a comprehensive market research analysis for [MARKET/INDUSTRY]. Structure your report as follows: EXECUTIVE SUMMARY (150 words max) Key finding, market size estimate, and single most important strategic insight. MARKET SIZING - Total Addressable Market (TAM): [your estimate with methodology] - Serviceable Addressable Market (SAM): [narrowed to realistic target] - Serviceable Obtainable Market (SOM): [realistic capture in 3 years] COMPETITIVE LANDSCAPE Identify the top 5-7 players. For each: - Market position and estimated share - Core value proposition - Target customer segment - Pricing model - Key strengths and weaknesses CUSTOMER SEGMENTS Define 3-4 distinct buyer personas with: demographics, pain points, buying triggers, willingness to pay, and decision-making process. MARKET TRENDS (next 2-3 years) Top 5 trends with: evidence it's happening, speed of adoption, business impact (High/Medium/Low). WHITE SPACE OPPORTUNITIES 3 specific gaps in the market not currently served well, with reasoning. STRATEGIC RECOMMENDATIONS If I'm entering this market, the top 3 moves I should make in the next 6 months. Market to analyze: [MARKET OR INDUSTRY] My company/product context: [BRIEF DESCRIPTION]

You are a senior business intelligence analyst. Analyze the data I provide and produce a professional insight report. DATA CONTEXT: - What this data represents: [DESCRIBE YOUR DATA] - Time period covered: [DATE RANGE] - Business context: [WHAT DECISIONS THIS DATA SHOULD INFORM] ANALYSIS FRAMEWORK: 1. DATA QUALITY AUDIT Flag any: missing values, outliers, suspicious patterns, potential data quality issues. Note these upfront so I know what to trust. 2. KEY METRICS SUMMARY The most important numbers at a glance (top 5-7 KPIs with period-over-period change where calculable). 3. TREND ANALYSIS What's growing? What's declining? What's stable? For each significant trend: identify when it started, estimated rate, and whether it appears accelerating or decelerating. 4. ANOMALIES & OUTLIERS Identify anything statistically unusual. For each anomaly: describe it, hypothesize 2-3 possible causes, and suggest how to investigate further. 5. CORRELATIONS Are there relationships between variables in this data? Note any that are surprising or counter-intuitive. 6. BUSINESS IMPLICATIONS Translate findings into plain English business conclusions. What should leadership know? What decisions does this data support? 7. RECOMMENDED NEXT STEPS The 3 most data-backed actions to take based on this analysis. [PASTE YOUR DATA BELOW]

Analyze this email thread and produce a professional meeting/thread summary. OUTPUT FORMAT: THREAD SUMMARY (3-4 sentences) What this thread is about, who is involved, and the overall status. DECISIONS MADE ✅ List every decision that was reached in this thread, even informally. Include who made or approved each decision. OPEN QUESTIONS ❓ Anything raised but NOT yet resolved. Include who needs to answer and any implied deadline. ACTION ITEMS 📋 | # | Action | Owner | Deadline | Priority | For each action item extracted from the thread. KEY CONTEXT Any background information in this thread that future readers would need to understand the decisions (contract terms, constraints, technical details mentioned). RECOMMENDED NEXT STEP What is the single most important thing that needs to happen to move this forward? [PASTE EMAIL THREAD BELOW]

Act as an expert presentation designer and business communicator. Create a complete Google Slides deck outline for: [PRESENTATION TOPIC] PRESENTATION CONTEXT: - Audience: [WHO WILL SEE THIS] - Goal: [WHAT SHOULD THEY THINK/DO AFTER] - Duration: [PRESENTATION LENGTH] - Tone: [FORMAL BOARD MEETING / CASUAL TEAM UPDATE / SALES PITCH / etc.] For each slide provide: SLIDE [N]: [Title] - Key Message: (the one thing this slide must communicate) - Bullet Points: (3-5 supporting points — specific, not generic) - Visual Suggestion: (what image, chart, or graphic would work best) - Speaker Notes: (2-3 sentences the presenter should say, NOT just repeat the bullets) - Transition to Next: (one sentence connecting this slide to the next) MANDATORY SLIDES TO INCLUDE: 1. Title slide (hook statement, not just the topic name) 2. Agenda / what we'll cover 3. [Core content slides — you determine based on topic] 4. Summary / key takeaways 5. Clear CTA / next steps slide 6. Q&A / contact slide Presentation topic: [TOPIC] Number of slides target: [SLIDE COUNT]

You are a senior business writer producing an executive-level report. Write a complete, professional report on: [REPORT TOPIC] REPORT STRUCTURE: COVER PAGE INFO Title: [REPORT TITLE] Prepared for: [AUDIENCE] Date: [DATE] Prepared by: [YOUR NAME/COMPANY] EXECUTIVE SUMMARY (250 words max) A standalone section that gives a busy executive everything they need to know: situation, key findings, recommendation, and business impact. BACKGROUND & CONTEXT Why this report exists, what problem or opportunity it addresses, scope and methodology. KEY FINDINGS Numbered findings (5-8), each with: - Clear finding statement - Evidence supporting it - Business significance ANALYSIS Deep-dive into the most important 2-3 findings. Explore causes, implications, and connections between findings. STRATEGIC OPTIONS Present 3 possible paths forward. For each: pros, cons, resource requirements, risks, and timeline. RECOMMENDATION Clear recommendation with supporting rationale. Why this option over the alternatives? IMPLEMENTATION ROADMAP 30/60/90-day action plan with milestones, owners, and success metrics. APPENDIX Any supporting data, methodology notes, or sources. Report topic: [TOPIC] Key data/context to include: [RELEVANT DATA OR BACKGROUND] Recommended option (if you already know it): [OPTIONAL]

You are a senior Python data engineer. Build a complete, production-ready data pipeline for: [PIPELINE DESCRIPTION] REQUIREMENTS: - Input: [WHERE DATA COMES FROM] - Output: [WHERE DATA SHOULD GO] - Transformations needed: [WHAT CHANGES TO THE DATA] - Error handling: Full try/except with meaningful error messages and logging - Scale: [EXPECTED DATA VOLUME] DELIVERABLES (provide all of these): 1. COMPLETE PIPELINE CODE - Modular functions (not one giant script) - Type hints on all functions - Docstrings for every function - Proper logging (use Python logging module, not print()) - Environment variable handling for credentials (never hardcode) 2. REQUIREMENTS.TXT All dependencies with pinned versions 3. CONFIGURATION FILE (config.yaml or .env.example) All configurable parameters separated from code 4. UNIT TESTS Test for: happy path, empty input, malformed data, connection failures 5. README.md Setup instructions, configuration guide, how to run, common errors 6. MONITORING APPROACH How to know if this pipeline fails or produces bad data in production Use this tech stack: [PYTHON VERSION + KEY LIBRARIES IF SPECIFIED]

Analyze the image I've provided. Perform a comprehensive extraction and analysis: 1. CONTENT INVENTORY List everything visible in this image — all text, numbers, labels, visual elements, people, objects, charts, etc. 2. DATA EXTRACTION (if applicable) If this is a chart, graph, table, or data visualization: extract ALL data points into a structured table format. Estimate values where exact numbers aren't labeled. 3. KEY INSIGHTS What are the 3-5 most important things this image communicates? 4. ANOMALIES OR NOTABLE ELEMENTS Anything unusual, surprising, or that stands out from what you'd expect? 5. CONTEXT INTERPRETATION Based on what you see, what is the purpose of this image/document? Who is the likely intended audience? 6. LIMITATIONS What can't you determine from this image alone? What additional context would help? My specific questions about this image: [YOUR SPECIFIC QUESTIONS]

You are an OKR expert who has implemented OKR frameworks at high-growth companies. Create a complete OKR framework for [TEAM/COMPANY] for [TIME PERIOD — Q1 2025 / H1 2025 / etc.] COMPANY/TEAM CONTEXT: - Mission: [MISSION STATEMENT OR GOAL] - Current stage: [EARLY STARTUP / GROWTH / ENTERPRISE] - Team size: [SIZE] - Key challenges: [TOP 1-2 CHALLENGES] FRAMEWORK STRUCTURE: COMPANY-LEVEL OBJECTIVES (2-3 max) For each objective: - Objective: [Inspiring, qualitative goal — what you want to achieve] - Why this objective: [Strategic rationale] - Key Result 1: [Specific, measurable, time-bound] - Key Result 2: [Specific, measurable, time-bound] - Key Result 3: [Specific, measurable, time-bound] - Success looks like: [What does achieving this change?] - Risk: [Main risk to this objective] TEAM-LEVEL OBJECTIVES (how they ladder up) Show how department-level OKRs connect to company OKRs. SCORING GUIDANCE How to grade key results at end of period. Explain the 0-1.0 Gemini scoring system. COMMON MISTAKES TO AVOID Top 3 OKR mistakes teams make, specific to this company's context. CHECK-IN CADENCE Weekly and monthly review questions for each objective. Company/team: [NAME] Time period: [PERIOD]