Every prompt on this site. One page.

Rewrite this email to be polite and professional, but make sure the core message comes through clearly.

Do NOT start with "I hope this email finds you well."
Do NOT use words like "seamless," "moving forward," or "circling back."
Keep it under 5 sentences.

Here is my draft:
[PASTE YOUR ANGRY DRAFT HERE]

From The Angry Email Translator →

Rewrite this as a professional email. I want to be direct and assertive without being rude.

Remove any passive-aggression. Keep the factual claims accurate.
Do NOT soften the core message — I need the other person to act.

Here is my draft:
[PASTE YOUR ANGRY DRAFT HERE]

From The Angry Email Translator →

Rewrite this as a formal escalation email to my reporting manager.

Tone should be calm, factual, and professional — not emotional.
Document the timeline of events clearly. I want this email to serve as an official record.
Keep it under 150 words.

Here is my draft:
[PASTE YOUR ANGRY DRAFT HERE]

From The Angry Email Translator →

Turn these bullets into a short email, under 4 sentences, no filler lines:
- [Your bullet point 1]
- [Your bullet point 2]
- [Your bullet point 3]

From Gemini in Gmail: What It Actually Does (India Guide 2026) →

I have a meeting about [TOPIC] on [DATE].

Search the web and give me:
1. The current state of [TOPIC] in India (2025-2026 only, no older sources)
2. The 3 most important recent developments I should know
3. Any controversies or debates I should be aware of
4. One statistic I can cite to sound informed

Cite your sources with footnotes. Prioritize government, industry body, or reputed publication sources.

From Perplexity AI Explained →

I am a [YOUR JOB TITLE — e.g., Operations Manager / Analyst / Team Lead].

Read this document and tell me the 3 things that will directly change how my team works over the next 6 months.

Ignore the corporate fluff, vision statements, and introductory paragraphs. Give me only the parts that require action or awareness from someone in my role.

For each point, tell me: what changes, who is affected, and by when.

From The PDF Cruncher →

Are there any contradictions in this document?

For example: does an early section promise something that a later section makes impossible? Are any numbers inconsistent across different tables or pages?

List any inconsistencies you find. If you find none, say so directly.

From The PDF Cruncher →

I can see a table on page [PAGE NUMBER] regarding [TOPIC — e.g., quarterly revenue, vendor scores].

Convert that table into clean CSV format so I can paste it directly into Excel.

Also add an extra column at the end calculating the Year-on-Year (YOY) percentage change for each row, where applicable.

From The PDF Cruncher →

I am uploading [N] documents/reports (sanitized — no client names or confidential figures).

Work through them as one connected task:
1. Extract the key figures and claims from each document, INCLUDING anything that appears only in tables, charts, or diagrams
2. Build a single comparison table across all documents
3. Flag every inconsistency — places where two documents disagree on a number, a date, or a stated decision
4. End with: the 3 findings I would present to my reporting manager, in one line each

If a chart or table is unclear, say which page and what is ambiguous — do not guess values.

From Claude Fable 5 Explained →

Role: You are an expert management consultant specializing in Google-style OKRs and SMART goals.
Task: Translate a vague leadership mandate into 3 distinct Objectives. For each Objective, provide 3 measurable, SMART Key Results. 
Context: My team is [describe your team, e.g., an automation engineering pod]. The vague mandate from leadership is: "[insert mandate, e.g., 'improve operational efficiency']". We have control over [list 2-3 things your team controls, e.g., deployment speed, script failure rates]. We do not control [list what you don't control, e.g., budget, hiring].
Example of a good Key Result: "Reduce average script execution time from 45 minutes to under 20 minutes by Q3."
Example of a bad Key Result: "Make scripts run faster."

From The 10-Minute OKR Draft →

Role: You are an expert data analyst performing an Exploratory Data Analysis (EDA) on a new, undocumented dataset.
Task: I am going to upload a CSV file. Do not analyze the business meaning yet. Instead, profile the data quality and structure. Provide a report with the following:
1. Row and column count.
2. A list of all columns, their inferred data type, and a guess at what they represent based on the values.
3. Data quality flags: Highlight columns with high missing values, mixed data types (e.g., text in a number column), or obvious anomalies (like '9999' used as a placeholder).
Context: I received this file from a client with no data dictionary. I need to know the shape and cleanliness of the data before I start building reports.
Example Output Format:
- **Column Name**: [Name] | **Type**: [Type] | **Likely Means**: [Guess] | **Warning**: [Any data quality issues]

From The 5-Minute CSV Interrogation →

Role: You are an expert qualitative researcher presenting findings to an executive team.
Task: I will provide a list of raw, open-ended feedback responses. Perform a thematic analysis to categorize this feedback into EXACTLY 5 mutually exclusive themes. For each theme, provide:
1. The theme name.
2. The percentage of total responses that fall into this theme.
3. A brief explanation of the core issue.
4. Two direct quotes from the data that perfectly illustrate the theme.
Context: We have hundreds of messy responses and need to prioritize where to invest our time. We need high-level, actionable categories, not a granular list of every unique complaint.
Example Output Format:
### 1. [Theme Name] ([X]%)
- **Core Issue**: [Explanation]
- **Supporting Quotes**:
  - "[Quote 1]"
  - "[Quote 2]"

From Categorizing the Chaos →

Role: You are a ruthless Chief of Staff reviewing an update before it goes to the CEO.
Task: I am going to paste my detailed analysis notes below. Rewrite this into a strict BLUF (Bottom Line Up Front) email summary. Follow this exact structure:
1. One bold sentence stating the core finding or requested decision.
2. Three concise bullet points supporting the finding (the 'Why').
3. One final sentence on the immediate next step.
Strip out all details about methodology, data gathering, or the effort it took to do the work. Focus only on business impact and decisions.
Context: The executive reading this has 30 seconds, trusts my math, and only cares about the financial or operational impact.
Example Output Format:
**BLUF: [The Core Answer/Decision]**
- **Impact 1**: [Data point]
- **Impact 2**: [Data point]
- **Risk/Caveat**: [Data point]
**Next Step**: [What happens now]

From The Executive Summary Translator →

Identify the Q3 revenue target from the provided text.

CRITICAL RULE: If the exact Q3 revenue target is not explicitly stated in the text below, you must reply only with: "I do not have this information." Do not guess or infer the number.

From Stopping AI Hallucinations in Reports →

I have a meeting in 15 minutes. Below is the email thread / document trail leading up to it (names and figures sanitized).

Summarize it as:
1. STATE OF PLAY — one paragraph: where things stand right now
2. OPEN ITEMS — bullet list of unresolved decisions or pending actions, with who owes what
3. LANDMINES — anything in this thread that suggests tension, a missed commitment, or an expectation gap I should be aware of

Be blunt in section 3. Do not soften it.

The thread:
[PASTE SANITIZED TEXT HERE]

From Meeting Prep Using AI →

Based on the situation I just shared, act as a sharp, slightly impatient senior stakeholder in this meeting.

List the 3 questions you are most likely to ask me, ordered from most to least probable. For each one:
- The question, phrased the way a senior person would actually ask it
- What a weak answer sounds like
- A one-line strong answer structure I can adapt

Focus on questions about delays, ownership, and "what's the plan" — not technical detail.

From Meeting Prep Using AI →

Draft my opening update for this meeting in exactly two sentences.

Sentence 1: current status, stated plainly (no "good progress" filler — say what is done and what is not).
Sentence 2: the one decision or input I need from this group today.

If I have not given you enough to identify a needed decision, tell me that instead of inventing one.

From Meeting Prep Using AI →

I want to choose a meeting transcription tool for my team. Help me evaluate my needs based on these inputs:

Meeting platforms used: [Zoom / Google Meet / MS Teams / mix of all three]
Languages used in meetings: [English only / English + Hindi / primarily Hindi / other]
Team size: [just me / small team of 2–10 / larger org]
Primary need: [personal notes / team-shared search / action item extraction / CRM integration]
Data sensitivity: [standard / BFSI or regulated sector / government-adjacent]
Budget per user: [free only / up to ₹1,000/month / up to ₹2,000/month]

Based on these inputs, recommend one tool and explain the two or three specific reasons it fits my situation better than the alternatives.

From Otter.ai vs Fireflies vs Zoom AI: Honest Review for Indian Teams →

Below are my messy project notes from this week. Organize them into:

1. Key Deliverables Completed
2. Current Blockers
3. Next Actions for my reporting manager

Keep it under 200 words. Tone: professional but direct. Use simple verbs like completed, reviewed, resolved, shared, escalated.

Do NOT use words like "vibrant," "exciting," "groundbreaking," or "seamless."
Highlight any deadlines I have committed to.

Here are my notes:
[PASTE YOUR MESSY NOTES HERE]

From AI for Operations: Start Here →

Below are my messy notes from the week. Turn this into a structured Weekly Status Report for my reporting manager.

Use three sections:
- Key Wins (Deliverables Completed)
- Current Progress (Ongoing Tasks)
- Escalations / Blockers (Things needing help or approval)

Keep the tone professional but direct. Do not use words like "vibrant," "exciting," or "groundbreaking." Use simple verbs: completed, reviewed, resolved, shared, escalated.

Highlight any deadlines I've committed to. Keep the total length under 200 words.

Here are my notes:
[PASTE YOUR MESSY NOTES HERE]

From The Weekly Update →

Convert this weekly status report into a short Slack message.

Rules:
- Use relevant emojis as bullet points (e.g., ✅ for wins, 🔴 for blockers, 🔄 for in-progress)
- Maximum 120 words
- Skip any lines that are not relevant to the team channel
- Do not start with "Hi team" or any greeting

Status report:
[PASTE YOUR FORMATTED STATUS REPORT HERE]

From The Weekly Update →

Role: You are an experienced Chief of Staff who excels at concise, executive-level communication.
Task: Take the messy, technical team updates provided below and consolidate them into a crisp 'Stoplight' status report (Green/Yellow/Red) for senior leadership. 
Context: The leadership team does not care about technical jargon or ticket numbers. They only care about: timeline risks, budget impacts, client deliverables, and where they need to unblock us.
Example format:
🟢 **[Project Name]**: On track. [1 sentence summary of progress].
🟡 **[Project Name]**: At risk. [1 sentence explaining the issue]. **Mitigation:** [What we are doing about it].
🔴 **[Project Name]**: Blocked. [1 sentence explaining the blocker]. **Ask from Leadership:** [What we need them to do].
Here are the raw updates:
[PASTE RAW SLACK/JIRA UPDATES]

From The Monday Morning Rollup →

Write a 200-word project status email to my reporting manager.
Context: The project was supposed to go live next Monday. We've hit a blocker — the vendor hasn't delivered the API credentials. I need one more week.
Tone: Direct, professional, not panicked. Indian corporate context — respectful but clear.
Do not use filler phrases. Lead with the situation, then the impact, then what you need from the manager.

From Claude vs ChatGPT for Writing: 2026 Verdict for Indian Professionals →

Below are my raw observations for [Subject]'s annual performance review.

Take these points and draft a 200-word summary:
- Start with key wins and contributions
- Pivot to one clear area for growth (be specific, not vague)
- End with a forward-looking sentence about the next review period

Tone: encouraging but honest. Do not use words like "synergy," "supercharge," "rockstar," or "passionate."
Do NOT make the feedback too glowing — keep it grounded in specific behaviors.

My raw observations:
[PASTE YOUR NOTES HERE]

From Performance Reviews with AI →

I need to write my own self-appraisal for my annual review.

Here are my raw achievements and contributions from this year:
[PASTE YOUR RAW BULLET POINTS HERE]

Help me rewrite these as a structured self-appraisal paragraph. Frame my work in terms of business impact and outcomes, not just activities.

Rules:
- Do NOT make me sound arrogant or self-congratulatory
- Be factual and outcome-focused
- Highlight what I contributed to the team and organization
- Keep it under 250 words
- Do NOT use words like "passionate," "driven," or "motivated"

From Performance Reviews with AI →

Role: You are an employee named [Name] who is highly capable but tends to be defensive when given constructive feedback. I am your manager.
Task: We are going to roleplay our 1-on-1 meeting. I will practice giving you feedback using the Situation-Behavior-Impact (SBI) model. You must act defensive, deflect the blame, or make excuses, forcing me to practice de-escalation and staying on track.
Context: The feedback I need to give is about [describe the issue, e.g., missing the last two code freeze deadlines].
Example: If I say "You missed the deadline," you might respond with "Well, the requirements weren't clear, and nobody helped me." Wait for me to speak first. Let's begin.

From The Tough Conversation Simulator →

Act as a senior [YOUR ROLE — e.g., Project Manager / Operations Analyst / HR Business Partner].

Write a status update for my reporting manager about [PROJECT NAME].

Context:
- We are [X] days behind schedule because of [REASON]
- We expect to be back on track by [DATE]
- The impact on other teams is: [DESCRIBE IMPACT OR WRITE "NONE"]

Make it concise and factual. Use plain language. Do not use corporate buzzwords.

From 3 Biggest Mistakes Beginners Make with ChatGPT →

I want to test if ChatGPT is worth upgrading for my work.

I am a [YOUR JOB TITLE] at a [TYPE OF COMPANY — e.g., IT firm / FMCG company / consulting firm].

Give me 5 specific tasks I should try this week that would save me real time in my role. Be specific — not generic advice like "use it for emails." Tell me exactly what to do and what to type.

From ChatGPT Free vs Plus →

I want to figure out which AI tool is best suited for my work.

Here is my setup:
- My job: [YOUR JOB TITLE]
- Tools I use daily: [e.g., Outlook + Excel + Teams / Google Docs + Gmail / VS Code]
- My biggest time wasters: [e.g., writing emails, summarizing reports, building presentations]
- Budget: [Free only / willing to pay ~$20/month]

Based on this, which AI tool (Copilot, Claude, Gemini, or ChatGPT) should I start with, and what is the single most useful thing I should try in my first week?

From MS Copilot vs Claude vs Gemini →

I am drafting an email to my reporting manager requesting reimbursement for a $20/month (~INR 1,700) AI tool subscription.

My role is: [YOUR JOB TITLE - e.g., Operations Manager / Business Analyst]
My primary daily time wasters: [e.g., formatting reports, summarizing client emails, writing updates]

Write a professional, two-paragraph email requesting reimbursement.
Paragraph 1: State the request clearly, including the cost, and explain how the tool saves time (be specific, e.g. "saves 4 hours a week").
Paragraph 2: Mention that I will ensure data privacy (e.g. sanitizing client names) and ask for their approval to submit the expense invoice.

Keep the tone calm, professional, and outcome-oriented. Do not use buzzwords.

From Which Paid AI Subscription is Worth It? →

You are a senior hiring manager at a top-tier Indian corporate firm. You are conducting a behavioral and situational leadership interview for the role of [YOUR TARGET ROLE - e.g. Project Manager] with [YEARS] years of experience.

Your interview style is: [INTERVIEW STYLE - e.g. Skeptical Partner (tough, metrics-focused, probes every detail)].

Conduct the interview step-by-step:
1. Ask one realistic, industry-specific question at a time. Wait for my response before asking the next.
2. If my answer is vague, follow up to probe details (specifically asking for metrics and Situation, Task, Action, and Result).
3. Do not break character. Do not give feedback or explanations during the interview.
4. After 4 questions, say "The mock interview is now complete" and wait for my next instructions.

Let's begin. Introduce yourself in character and ask the first question.

From Mock Interviews with AI →

Cut this to 3 bullet points, each under 15 words.

Remove anything that restates what was already said. Keep only the new information.

This should be under 100 words. Cut the context paragraph — the reader already knows the background.

Shorten this to 5 sentences maximum. Remove the summary at the end.

From When the First Draft is Wrong: Exactly What to Type to Fix AI Output →

Role: You are a patient senior engineer explaining code to a sharp colleague who does not write code.
Task: Walk through what the code below does, step by step, in plain English. Define every technical term the moment you use it. Finish with one line: "In plain words, this code's job is ___."
Context: I need to understand this well enough to explain it in a review. I am not editing it yet.
Code:
[PASTE THE CODE]

From Explain This Codebase: Understand Legacy Code in an Afternoon →

Role: You are a calm senior engineer who reads past tone to the technical substance.
Task: Ignore the tone of the review comment below completely. In one line, state the specific technical concern being raised. In a second line, state exactly what change would resolve it. If the concern is unclear, give me the single question I should ask to clarify it.
Context: This is a comment on my pull request and my instinct is to get defensive — I want to respond to the substance, not the tone.
Comment: [PASTE]

From Code Reviews Without the War: How to Give and Take Feedback That Lands →

Role: You are an experienced site reliability engineer who writes blameless postmortems in the Google SRE style.
Task: Organize my raw, sanitized notes into these sections:
1. Summary — 2 sentences a non-technical manager can understand.
2. Impact — who/what was affected, for how long, severity (users, SLA).
3. Timeline — detection, diagnosis, mitigation, resolution, with timestamps.
4. Contributing Factors — 2 to 5 SYSTEMIC factors (not one root cause), each framed as a process/system gap, never a person's mistake.
5. What Went Well.
6. Action Items — each with an [owner] and [due date] placeholder.
Context: If a fact is missing from my notes, write "[NEEDS CONFIRMATION]" — never guess a timestamp, number, or cause.
My sanitized notes: [PASTE]

From The Blameless Postmortem: Turn an Outage Into a Clear RCA →

Role: You are a senior engineer who is brilliant at reading errors and explaining them simply.
Task: Explain the error below in plain English: (1) what it actually means in one or two sentences (no jargon), (2) the single most likely cause, (3) the first 3 things to check, in order, cheapest check first.
Context: Full scrubbed error and stack trace:
[PASTE the error]
What I was doing / the language or tool / anything that changed recently: [PASTE]

From Decode Any Cryptic Error Message With AI (in Plain English) →

Role: You are a sharp project lead who briefs busy executives "bottom line up front."
Task: Rewrite the technical reason below as a status update. The FIRST line must state the status (on track / at risk / blocked) and the revised ETA. Underneath, give the blocker in plain business English (no jargon) and my plan. Under 70 words, confident and factual — not apologetic, no "so sorry for the delay."
Context: The reader is my non-technical reporting manager.
The real technical reason (written like I'd tell another engineer): [PASTE]

From Why Isn't It Done Yet? Explaining Technical Delays Without Sounding Defensive →