Better answers from ChatGPT,
Claude, and Gemini.

Rewrite the following text to be [more professional / more casual / clearer / shorter]. Keep the original meaning but improve flow and remove any filler. Text to rewrite: [PASTE YOUR TEXT HERE] After rewriting, list 2 small improvements you made and why.

Write a cold outreach email pitching my [SERVICE] to [TARGET CLIENT TYPE]. Rules: - Under 120 words - Open with a specific observation about their work (placeholder for me to fill) - One clear value proposition tied to revenue or hours saved - Soft CTA — not "book a call" — something lower friction - Sound human, not salesy Write 3 versions: confident, friendly, data-driven. Label each.

You are a social media copywriter who has written hooks for posts with millions of views. Generate 10 scroll-stopping hooks for [PLATFORM] about [TOPIC]. Each hook must: - Be under 15 words - Create curiosity or tension - Avoid clickbait — deliver on the promise - Work for [carousel / reel / thread / post] Rank them from "safe bet" to "high risk, high reward." Explain why each works.

Create a detailed customer persona for someone who would buy [YOUR PRODUCT/SERVICE]. Go beyond demographics. Include: - Name, age, role - Daily routine and frustrations - What they Google at 11pm (real anxieties) - What they've already tried to solve this - Their objections to buying - The exact moment they decide to purchase - How they describe the problem to a friend (their words, not marketing speak) Make this person feel real — I want to picture them.

Explain [COMPLEX TOPIC] in simple terms a complete beginner would understand. Use: - An everyday analogy - A short definition (1–2 sentences) - A real-world example - 3 things a beginner should know - 2 common mistakes beginners make Avoid jargon. If you must use a technical term, define it in parentheses.

I'm planning my week. Here's everything on my plate: [DUMP YOUR LIST]. Help me: 1. Sort items into Eisenhower quadrants (urgent/important matrix) 2. Suggest a 5-day schedule that batches similar work together 3. Flag the 1–2 things I should probably drop 4. Identify dependencies (what must happen first) Be honest about overload. If I have too much, say so.