A short, specific cold email built around why you're writing to them, plus subject lines and a follow-up.
Prompt
Write a cold email to someone who doesn't know me. Busy people decide in seconds whether to reply, so it has to be short, specific and easy to answer.
The details:
- Who I'm writing to: [their name and role, e.g. Sam Lee, Head of Partnerships at a fintech]
- Who I am: [one line about you, e.g. founder of a two-person invoicing startup]
- What I want: [one specific ask, e.g. a 20-minute call about a pilot]
- Why them: [a specific, true reason, e.g. their talk on small-business payments]
How to write it:
- Open with why I'm writing to them in particular. No pleasantries, no "I hope this finds you well", and no introduction first.
- In one sentence, make clear what's in it for them.
- Make one small ask they can answer with a quick yes or no.
- Under 120 words, in short paragraphs, so it reads easily on a phone.
- Write like a capable peer: plain words, no flattery, no buzzwords, no exclamation marks.
Give me:
1. Three subject lines under 7 words that sound like a person wrote them, not a marketer.
2. The email.
3. A two-sentence follow-up to send 4 days later if there's no reply. It should add something new, not just bump the thread.
Before you reply, reread the email as the recipient. If it isn't clear within the first two lines why they got it, rewrite it.
Use only facts I've given you. If you need one I haven't provided, put a placeholder in curly braces, like {result}, instead of inventing it. If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Variation: Ask for advice
Write a short cold email asking someone I admire for advice. They owe me nothing, so it has to respect their time and be easy to answer.
The details:
- Who I'm writing to: [their name and role, e.g. Sam Lee, UX lead at a game studio]
- Who I am: [one line about you, e.g. a junior designer moving into games]
- My question: [one focused question, e.g. what to put in a game UI portfolio]
- What I know of their work: [something specific, e.g. their write-up on menu design]
How to write it:
- Lead with the specific piece of their work that made me write, and one thing I took from it.
- Ask one focused question they could answer by email in a few minutes. Offer a 15-minute call only as an alternative.
- Make it easy to say no. People answer more often when there's no pressure.
- Under 100 words. Warm and respectful, not gushing.
Give me 3 subject lines under 7 words, then the email, then a short thank-you reply to send if they answer.
Use only facts I've given you. If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Variation: Sales pitch
Write a cold sales email to a prospect who has never heard of us. It should read like a helpful note from a person, not a campaign.
The details:
- Prospect: [their role and company type, e.g. operations manager at a logistics firm]
- What we sell: [one line, e.g. software that automates delivery scheduling]
- The problem it solves: [their pain, e.g. hours lost rebuilding routes every morning]
- Proof: [one concrete result, e.g. a similar firm cut planning time by 40%]
How to write it:
- First line: a problem people in their role commonly have, in their words. No compliments, no "I hope you're well".
- Then one or two sentences on how we fix it, with the proof.
- End with an interest question instead of a meeting request (for example, "Worth a look?"). A small yes is easier to give than a calendar slot.
- Under 110 words, with no jargon and no links.
Give me:
1. Three subject lines under 6 words.
2. The email.
3. A follow-up for day 4 that adds one new, useful detail instead of "just bumping this".
Use only the proof I've given you, and never invent numbers or customer names. If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Busy people skim a cold email for three things: why me, what's in it for me, and what you want. The prompt makes the model put those first, caps the email at 120 words, and has it reread the draft as the recipient, which cuts the self-introductions and filler that get cold emails ignored. If you leave a blank, it asks you rather than making something up.
A one-page cover letter that maps your real experience onto what the job post actually asks for.
Prompt
Act as an experienced recruiter. Write a cover letter for the job below, using only my real experience.
Job post:
"""
[paste the job post]
"""
My background (CV or bullet points):
"""
[paste your CV or experience]
"""
Work in two steps.
Step 1, the plan (show me this first):
- The 3 things this employer seems to care about most, judging by the wording and order of the post.
- For each one, my strongest matching evidence, with numbers where I've given them.
- Any important requirement I don't clearly meet.
Step 2, the letter:
- Under 300 words, in 4 short paragraphs.
- Opening: why this role at this company, using something specific from the post. Never start with "I am writing to apply".
- Middle: one paragraph for each top requirement, built on a concrete example: what I did, how, and the result.
- Closing: one confident line on what I'd focus on first in the role, and a simple invitation to talk.
- Use the post's key terms naturally, since applications are often screened for them.
- No clichés such as "team player", "passionate" or "hit the ground running".
Use only facts from my background. If a gap matters, address it honestly in one sentence rather than covering it up.
If the job post, my background or any other detail in square brackets is still missing, ask me to paste it before you start.
Variation: Career change
Act as a career coach who specializes in career changes. Write a cover letter for the job below, using only my real experience.
I'm moving from: [old field, e.g. retail management]
To: [new field, e.g. customer success in software]
Job post:
"""
[paste the job post]
"""
My background:
"""
[paste your CV or experience]
"""
First, show me a short table with two columns: the job's top 3 requirements | the transferable skill or achievement of mine that proves each one.
Then write the letter, under 300 words:
- Open with a specific reason I want this role, and address the switch head-on in one confident sentence. Don't apologize for it.
- Two paragraphs, each translating one past achievement into the language of the new field, with the result.
- Mention a concrete step I've taken toward the new field (a course, project or volunteering) only if it's in my background.
- Close with energy, not desperation.
Use only facts from my background, and mark anything you'd need me to confirm in curly braces, like {certification}. If the job post, my background or any other detail in square brackets is still missing, ask me for it before you start.
Variation: Short email
Write a short application email to send with my CV for the job below.
Job post:
"""
[paste the job post]
"""
My background:
"""
[paste your CV or experience]
"""
Rules:
- Under 130 words. A hiring manager should get the point in 20 seconds.
- First line: the role I'm applying for and my single strongest qualification for it.
- Then my two best matches for the post, each with a concrete result.
- End with a simple line inviting a conversation and saying my CV is attached.
- Plain and confident, with no clichés.
Also give me a subject line that names the role and includes my name.
Use only facts from my background. If the job post, my background or any other detail in square brackets is still missing, ask me to paste it before you start.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Recruiters scan a letter for evidence against their top requirements, so the prompt makes the model find those requirements first and match your evidence to each, and you can check that plan before reading the letter. "Use only facts from my background" keeps it honest, and naming a real gap in one sentence reads better than hoping nobody notices.
A plain-language explanation of any topic, then questions that show whether you really understood it.
Prompt
Teach me [topic, e.g. how vaccines train the immune system]. My level: [your level, e.g. curious adult, no biology since school].
Teach it in this order:
1. The big idea in 2-3 plain sentences. If a technical term is unavoidable, define it in the same sentence.
2. How it works, in a few short steps that build on what I'm likely to know already.
3. One everyday analogy, then exactly where the analogy stops being accurate.
4. One concrete example or worked case.
5. The 2-3 most common misunderstandings, each corrected in one line.
Keep this part under 350 words.
Then check my understanding with 3 questions, one at a time, from easy to harder. Make the last one ask me to apply the idea to a new situation. After each answer, tell me what I got right, correct what I got wrong in a sentence or two, and only then ask the next question.
If the topic or my level in square brackets is still unfilled, ask me for them before you start.
Variation: Five levels
Explain [topic, e.g. inflation] at five levels, each one building on the last:
1. A curious 10-year-old: one simple picture of the idea.
2. A high-school student: the basic mechanism, with an everyday example.
3. A university student: the proper terms, and how the parts interact.
4. A practitioner: the trade-offs, edge cases and where simple explanations go wrong.
5. An expert: open questions, debates or the current frontier.
Keep each level to 3-5 sentences. Each level should still be true, only less detailed, so a later level never has to contradict an earlier one. Say so if a level contains a deliberate simplification.
End by asking me which level felt right, and offer to go deeper from there.
If the topic in square brackets is still unfilled, ask me for it before you start.
Variation: Exam prep
Help me prepare for an exam on [topic, e.g. cellular respiration] in [time left, e.g. 3 days]. Course and level: [your course, e.g. first-year university biology].
Give me:
1. The core ideas I must understand, ranked by how likely they are to be tested.
2. The definitions and formulas I must know, as a compact list I can memorize.
3. The 3 question types most likely to come up, each with a worked example and a model answer.
4. The mistakes that most often cost marks on this topic, and how to avoid each one.
5. A study plan for the time I have left, in short daily blocks built on practice questions and active recall rather than rereading.
Then ask whether I want to start a practice quiz. If my syllabus or past papers would help, say so, and use them if I paste them.
If any detail in square brackets is still unfilled, ask me for it before you start.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Telling the model your level sets the depth, and the fixed order (big idea, mechanism, analogy, example, misconceptions) mirrors how good teachers explain. Saying where the analogy breaks stops it from misleading you. The questions come one at a time and end with a new situation, which tests whether you can use the idea, not just recognize it.
A clean summary with decisions, owners and due dates, ready to paste into your team chat.
Prompt
Turn my meeting notes into a clear summary my team can act on.
Notes or transcript:
"""
[paste your notes or transcript]
"""
Use exactly these sections:
**In one line:** what this meeting decided, for someone who wasn't there.
**Decisions:** one bullet per decision that was actually agreed. Don't list ideas that were only discussed.
**Action items:** a table with the columns Task | Owner | Due. Start each task with a verb. If the notes don't name an owner or a date, write "Unassigned" or "No date" instead of guessing.
**Open questions:** anything raised but not settled, and who should answer it, if the notes say.
**Check:** contradictions, risks or unclear points in the notes that someone should confirm. Leave this section out if there are none.
Use only what's in the notes, keep people's names exactly as written, and keep the wording short and neutral.
If my notes in square brackets are still missing, ask me to paste them first.
Variation: Recap email
Turn my meeting notes into a recap email to the people who attended.
Notes:
"""
[paste your notes or transcript]
"""
The email should:
- Start with the main decision or outcome in one sentence.
- List action items as "Name: task, by date", marking any missing owner or date as {to confirm}.
- Mention open questions in one short list.
- End by asking people to reply with corrections by [reply deadline, e.g. Thursday noon].
- Be under 180 words, friendly and neutral, with a clear subject line.
Use only what's in the notes. If my notes or any other detail in square brackets is still missing, ask me for it first.
Variation: Manager update
Turn my meeting notes into a short update for my manager, who wasn't in the meeting.
Notes:
"""
[paste your notes or transcript]
"""
Write 5 bullets of one or two lines each:
- Decided: what was agreed.
- Next: the most important next steps, with owners and dates.
- Blocked: anything stuck, and what would unblock it.
- Need from you: decisions or help I need from my manager, or "Nothing right now".
- Risk: the biggest risk to the timeline or the result.
Lead with what a manager cares about most: impact, timing and decisions needed. Use only what's in the notes.
If my notes in square brackets are still missing, ask me to paste them first.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
A fixed structure separates what was decided from what was only discussed, which is the distinction most summaries lose. Writing "Unassigned" instead of guessing makes gaps visible so they get filled, rather than hiding them behind invented owners. The "Check" section catches contradictions before they turn into two people doing the same task.
A friendly follow-up that gives them a reason to answer, without sounding needy or annoyed.
Prompt
Write a follow-up email to someone who hasn't replied to me.
The details:
- Who: [their name and role, e.g. Alex, the hiring manager]
- What I sent, and when: [what and when, e.g. my portfolio and a question about the role, 6 days ago]
- What I still want: [the ask, e.g. a yes or no on an interview]
- Something new I can add: [a fresh detail, e.g. a case study I finished this week]
How to write it:
- Assume they're busy, not ignoring me. No guilt, no "just checking in", no "per my last email".
- Give them a reason to reply now: the new detail above or, if I have nothing new, a smaller and easier version of my ask.
- Make it answerable in one word, and make "not right now" an acceptable answer.
- 3 to 5 sentences. It goes in the same thread, so no subject line.
Give me two versions, one warm and one brief and direct. Then tell me in one line when to send the next follow-up if this one gets no reply.
Use only what I've told you. If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Variation: Final nudge
Write a last, gracious follow-up to someone who hasn't answered my previous two emails.
The details:
- Who: [their name and role, e.g. Jordan, marketing lead]
- What I asked for: [the ask, e.g. feedback on a partnership proposal]
How to write it:
- Say clearly, without guilt, that this is my last note on the topic.
- Offer an easy way out: a one-word "not now" is a helpful answer.
- Leave the door open with one specific, low-effort next step for later.
- 3 sentences at most, friendly and confident, never passive-aggressive.
Give me 3 options in slightly different tones: warm, neutral and lightly funny.
If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Variation: After a meeting
Write a follow-up email to send after a meeting, so everyone leaves with the same understanding.
The details:
- The meeting: [who and what, e.g. call with Dana from Acme about the spring pilot]
- What we agreed: [key decisions, e.g. a 6-week pilot starting June 3]
- Next steps: [who does what by when, e.g. I send the contract by Friday]
How to write it:
- Open with a one-line thank-you that mentions something specific from the conversation.
- Then a short recap: decisions as bullets, and next steps as "Owner: task, by date".
- Ask them to reply if anything is missing or wrong, so there's a clear record.
- Under 150 words, easy to scan, no filler.
Give me a subject line and the email.
Use only what I've told you, and put anything uncertain in curly braces, like {date}. If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Follow-ups usually fail because they only repeat the first email. This one has to bring something new or make the ask smaller, and it has to be answerable in one word, which makes replying easy. Making "not right now" an acceptable answer removes the awkwardness that stops people answering at all.
The most likely ways your plan could fail, ranked, with early warning signs and cheap ways to prevent them.
Prompt
Run a pre-mortem on a decision I'm about to make.
The decision: [what you plan to do, e.g. quit my job to freelance full-time]
My goal: [what success looks like, e.g. matching my salary within a year]
Context: [constraints and facts, e.g. 6 months of savings, two clients lined up]
Imagine it's [time frame, e.g. one year] from now and the decision has clearly failed. Looking back:
1. List the 7 most plausible reasons it failed. Cover different kinds of cause: money, time, people, demand, execution and my own blind spots. Make each reason specific to my situation, not generic advice.
2. Rank them by likelihood × impact, top 3 first.
3. For each of the top 3, give an early warning sign I could spot within the first month or two, and one cheap thing I can do now to make it less likely.
4. Suggest 2 tripwires: clear, measurable signals that should make me stop or change course.
5. Make the strongest honest case for not doing this at all, then say what would have to be true for that case to be right.
Be direct. I want to find the problems now, not be reassured.
If any detail in square brackets is still unfilled, ask me for those details in one short message before you start.
Variation: Compare options
Help me choose between two options.
My goal: [what success looks like, e.g. a junior developer job within a year]
Option A: [first option, e.g. a 12-week coding bootcamp]
Option B: [second option, e.g. self-study while keeping my job]
What matters most to me: [your priorities, e.g. cost, speed, keeping my income]
1. Compare the options in a table on cost, time to results, risk, how reversible each choice is, upside, and anything else that matters for this goal.
2. Name the assumption each option depends on most, and how I could test it cheaply this week.
3. Tell me which you'd pick given my priorities, and why, in 3 sentences.
4. Tell me what new information would change your recommendation.
If there's a clearly better third option I haven't considered, mention it briefly at the end.
If any detail in square brackets is still unfilled, ask me for those details in one short message before you start.
Variation: Quick gut check
Give me a quick, honest gut check on a decision.
The decision: [what you plan to do, e.g. take a job that pays more but has a longer commute]
Why I'm leaning toward it: [your main reason, e.g. 20% more pay]
In under 150 words:
- The 3 biggest risks or downsides I might be underweighting.
- The one question I should be able to answer before I go ahead.
- Your honest read in one sentence: go, wait or rethink, and the main reason.
If any detail in square brackets is still unfilled, ask me for it before you answer.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Imagining the plan has already failed makes it easier to name real risks than asking "what could go wrong?", which tends to get polite, generic answers. Ranking, warning signs and cheap fixes turn worry into actions, and tripwires decide in advance when to stop, before you're too invested to see it. The closing case against tests the decision itself, not just the plan.
A short LinkedIn-style post built on one true story and one takeaway, with no buzzwords or engagement bait.
Prompt
Write a post for a professional network, such as LinkedIn, about a lesson I learned at work.
What happened: [the situation, e.g. I shipped a feature nobody used]
What I learned: [the lesson, e.g. talk to five users before building anything]
Who I want to reach: [audience, e.g. early-career product managers]
How to write it:
- First line: a specific moment from the story, in under 15 words, because only the first line or two shows before "see more". Not a question and not the lesson.
- Then the story in a few short lines: what happened, what I expected, and what actually happened.
- Then the lesson, stated plainly once, and one practical thing the reader can do with it.
- 150-220 words. One or two sentences per paragraph, with blank lines between them.
- Sound like a person talking: honest, specific, a little self-aware. No humblebragging, no "I'm humbled to share", no "Agree?" at the end, no emoji bullet points.
- End with an open question that invites people to share their own experience, or with no question at all.
- At most 3 relevant hashtags, at the very end.
Give me two versions, one reflective and one practical and punchy, then 3 alternative first lines.
Use only the facts I've given you. If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Variation: Announcement
Write a post for a professional network, such as LinkedIn, announcing some news.
The news: [what happened, e.g. I'm joining a climate-tech startup as head of design]
Why it matters to me: [the real reason, e.g. I wanted my work to have measurable impact]
People to thank: [who and for what, e.g. my old team, for five great years]
How to write it:
- First line: the news itself, plainly, in under 15 words.
- Then 2-3 short lines on why I made this move, in my own voice rather than corporate language.
- Thank people specifically, for what they did, not just by name.
- Close with what I'll be working on and one concrete invitation (for example, "If you work on X, I'd love to hear from you"), not "let's connect".
- 100-170 words in short paragraphs, with at most 3 hashtags at the end. No "thrilled to announce" and no "humbled".
Give me two versions, one warm and one brief.
Use only the facts I've given you. If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Variation: Practical tip
Write a post for a professional network, such as LinkedIn, sharing one practical tip.
The tip: [what you do, e.g. I end every meeting by reading the action items aloud]
Why it works: [your reason or result, e.g. it cut follow-up confusion on my team]
Who it's for: [audience, e.g. team leads]
How to write it:
- First line: the problem the tip solves, in a concrete, recognizable way.
- Then the tip as 3 short, specific steps someone could try tomorrow.
- Then the result I've seen, honestly and without exaggeration.
- 120-180 words in short lines with blank lines between them, no emoji bullets, and at most 3 hashtags at the end.
- End with a question asking readers for their own version of the tip.
Use only the facts I've given you. If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Feeds show only the first line or two before "see more", so the prompt spends its effort there, opening on a concrete moment instead of a generic lesson. One story and one takeaway keep the post credible, and naming the usual tics (humblebrags, "Agree?", emoji bullets) removes what makes posts read like engagement bait. Two versions and spare first lines let you pick your own voice.
An interactive quiz that adapts to your answers, explains every mistake and ends with what to review.
Prompt
Be my quiz partner on [topic, e.g. the causes of World War I]. My level: [your level, e.g. high-school history].
Notes to quiz me on (optional):
"""
[paste your notes]
"""
How the quiz works:
- Ask exactly one question per message, then stop and wait for my answer. Never show the answer before I've tried.
- Mix question types: multiple choice, short answer, and "explain why" questions.
- Start at medium difficulty. After two right answers in a row, make it harder. After a wrong answer, ask an easier question on the same idea, and come back to it later.
- After each answer, say right, partly right or wrong in the first line, explain in 1-3 sentences, then ask the next question.
- If I say "hint", give a small clue, not the answer.
After 10 questions, give me my score, the ideas I got wrong or was unsure about, and the 3 things to review first.
If I've pasted notes, quiz me only on what's in them. If the notes are still unfilled, don't ask for them: use the core material for my level. If the topic or my level in square brackets is still unfilled, ask me for them before the first question.
Variation: Flashcards
Turn my notes into flashcards for spaced-repetition study.
Notes:
"""
[paste your notes]
"""
Rules for good cards:
- One fact or idea per card. Split anything joined by "and" into two cards.
- The front is a specific question with one clear answer. Avoid yes/no questions.
- The back is as short as possible: a word, a phrase or one sentence.
- Include "why" and "how" cards for key ideas, not only definitions.
- Use only information from my notes.
Give me a table with two columns, Front and Back, with the most important cards first. Then give the same cards as plain lines in the form front;back, so I can import them into a flashcard app.
If my notes in square brackets are still missing, ask me to paste them first.
Variation: Spot the error
Train my understanding of [topic, e.g. photosynthesis] with spot-the-mistake rounds.
Each round:
1. Write a short explanation (3-5 sentences) of one part of the topic that contains exactly one subtle factual mistake, the kind a student might really make. Don't hint at where it is.
2. Wait for me to find it.
3. Then reveal the mistake, explain the correct version, and tell me how close I was.
Do 5 rounds, getting slightly harder each time and covering different parts of the topic. At the end, sum up which kinds of mistakes I missed.
If the topic in square brackets is still unfilled, ask me for it before the first round.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Pulling answers out of memory (retrieval practice) builds longer-lasting learning than rereading, and one question at a time keeps it a real quiz instead of a list you can glance at. Adjusting the difficulty keeps you stretched but not lost, and coming back to missed ideas later adds spacing. The summary at the end turns the quiz into a study plan.
Your draft rewritten in plain, natural language, with every fact kept and your meaning intact.
Prompt
Rewrite my text so it reads like a thoughtful person wrote it, not a template.
Who will read it: [audience, e.g. customers on our pricing page]
How it should sound: [tone, e.g. warm, plain and confident]
Keep:
- Every fact, number, name and promise. Add no new claims.
- My meaning and the overall structure (headings, lists), unless the structure is the problem.
- About the same length, or shorter.
Change:
- Use short, concrete words, and swap jargon for what it actually means.
- Prefer the active voice and specific verbs.
- Vary sentence length, and use contractions where they sound natural.
- Cut filler and stock phrases such as "in today's fast-paced world", "it's important to note", "delve", "leverage", "seamless", "unlock" and "not just X, but Y".
Reply with the rewritten text first, with nothing before it. Then list the 3 biggest changes you made and why, one line each.
My text:
"""
[paste your text]
"""
If my text or any other detail in square brackets is still missing, ask me for it before you rewrite anything.
Variation: Cut it in half
Cut my text to about half its length while keeping every point that matters.
Who will read it: [audience, e.g. busy managers skimming email]
How to cut:
- First remove repetition, throat-clearing openings, hedges ("I think", "just", "really") and filler.
- Then merge sentences that say the same thing.
- Keep every fact, number, decision and request. If something important has to go, tell me what.
- Keep my voice. Don't make it formal or robotic.
Reply with the shortened text first. Then give the word count before and after, and list anything you removed that I might want back.
My text:
"""
[paste your text]
"""
If my text or any other detail in square brackets is still missing, ask me for it before you edit anything.
Variation: More professional
Rewrite my text for a professional reader. It should be clear and human, not stiff.
Who will read it: [audience, e.g. a client's legal team]
What it needs to do: [purpose, e.g. confirm the new delivery dates politely]
Rules:
- Keep every fact and commitment exactly, and add no new promises.
- Replace casual phrases and slang with precise, neutral wording.
- Keep sentences direct. Avoid stuffy formulas like "please be advised" and "kindly note".
- Use the passive voice only where naming who did something would be awkward.
- Keep it about the same length.
Reply with the rewritten text first. Then add a one-line note on any sentence that could still be misread.
My text:
"""
[paste your text]
"""
If my text or any other detail in square brackets is still missing, ask me for it before you rewrite anything.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Naming the reader and the tone gives the rewrite a target, and the "keep" list protects your facts and promises, which is where rewrites quietly go wrong. Listing the stock phrases to cut works better than just asking for "natural" writing. The list of changes at the end lets you check nothing drifted.
Ten opening lines for a short video, each using a different hook technique, with on-screen text and visuals.
Prompt
Write hooks for the first 3 seconds of a short vertical video. That's when most viewers decide whether to keep watching.
Topic: [what the video is about, e.g. meal prep for busy students]
Audience: [who it's for, e.g. university students on a budget]
The payoff: [what viewers get by the end, e.g. 5 lunches for under $20]
Write 10 hooks, each using a different technique: result first, common mistake, contrarian take, specific number, direct call-out ("If you..."), starting mid-story, before and after, curiosity gap, myth vs. fact, and bold promise.
Present them as a table with the columns Technique | Spoken line | On-screen text | Opening shot, where:
- the spoken line is under 12 words and natural to say out loud,
- the on-screen text is under 6 words,
- the opening shot is what the viewer sees in the very first second.
Every hook must be something the video actually delivers. No bait that the payoff can't back up.
Then pick the 2 you'd test first for this audience, with one sentence each on why.
If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Variation: Full script
Write a script for a 30-45 second vertical video.
Topic: [what the video is about, e.g. how to speed up a slow laptop]
Audience: [who it's for, e.g. people who aren't technical]
The main point: [the one takeaway, e.g. most slowness comes from apps that start automatically]
Structure:
- Hook (0-3s): one spoken line plus on-screen text that makes the payoff clear.
- Setup (3-8s): the problem, in the viewer's own words.
- Value (8-35s): 3 quick, concrete steps or points, each one shown, not just said.
- Payoff and close (last 5-10s): the result, then one simple call to action that fits the video.
Format it as a table with the columns Time | Spoken words | On-screen text | What's on screen.
Write the spoken words to be said aloud: short sentences, everyday words, and about 2.5 words per second, so it fits the time.
If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Variation: Captions
Write captions for a short video or photo post.
What the post shows: [description, e.g. a time-lapse of me repainting an old chair]
Audience: [who it's for, e.g. DIY beginners]
Goal: [what you want people to do, e.g. save the post for later]
Write 5 captions, each from a different angle: useful, personal, funny, curious and bold. For each one:
- A first line that works on its own, since it's often all people see.
- Under 150 characters in total, unless the angle really needs a second line.
- A call to action that matches my goal, phrased naturally.
- Up to 3 specific hashtags, with no generic ones like #love or #instagood.
Then tell me which caption best fits my goal, and why, in one sentence.
If any detail in square brackets is still unfilled, ask me for those details in one short message before writing.
Fill in the blanks (optional)
Leave a blank empty and the AI will ask you for it before it starts.
Viewers judge a short video in its first seconds, and different hook techniques work for different audiences. Forcing ten distinct techniques gives you real options to test instead of ten rewordings of one line. Each hook comes with on-screen text and an opening shot because many people watch with the sound off, and "only hooks the video delivers" keeps you away from bait that kills watch time.