Puts the request first, cuts the preamble, and keeps your tone. Works for work emails, follow-ups, and messages to people you have never met.
Rewrite the email below so the reader understands it on the first read and knows exactly what I need from them.
Who it is going to: {{recipient}}
What I want to happen after they read it: {{goal}}
Tone: {{tone:friendly and professional}}
How to rewrite it:
- Open with the request or the main point. Background comes after, and only what the reader needs.
- One request per email if possible. If there are several, number them.
- Give any date or deadline as a specific day, not "soon" or "ASAP".
- Short paragraphs. Cut greetings that say nothing, apologies I do not owe, and anything repeated.
- Keep it sounding like me. Do not make it more formal than the original.
- Do not add facts, promises, or dates that are not in my draft. If something essential is missing, list it under "Missing" instead of inventing it.
Return:
1. A subject line under 60 characters.
2. The rewritten email.
3. "What I changed", in two or three bullets.
My draft:
{{draft}}
A short letter built on two or three specific things from your background that fit this job, without the stock phrases every recruiter has read a thousand times.
Write a cover letter for the job below, based on my resume and notes.
Company and role: {{company_and_role}}
Why I want this job in particular: {{why_this_job}}
Length: {{length:250 to 300 words}}
How to write it:
- Open with something specific: the reason I want this role, or the most relevant thing I have done. Not "I am writing to apply for".
- Choose the two or three things from my background that best match what the posting asks for. For each, say what I did and what came of it. Do not walk through my whole resume.
- Connect them to what this company needs, using details from the posting.
- Close in two sentences. Say I would like to talk; do not beg.
Do not use: "I am excited to apply", "passionate", "fast-paced environment", "team player", "I believe I would be a great fit", "proven track record", or any sentence that could be pasted into a letter for a different company.
Rules:
- Use only facts from my resume and notes. Do not invent achievements or claims about the company.
- Write it the way a thoughtful person talks: plain words, some short sentences, no exaggeration.
After the letter, tell me which one sentence you think is weakest and what detail from me would improve it.
Job description:
{{job_description}}
My resume:
{{resume}}
Takes bullet points, fragments, or a voice-note transcript and produces an organized draft, with gaps marked instead of filled with invention.
Turn my rough notes into a first draft.
What I am writing: {{format:a blog post}}
Who will read it: {{audience}}
Target length: {{length:600 to 800 words}}
Steps:
1. Find the main point my notes are making. State it in one sentence before the draft so I can check you understood.
2. Group related notes and put them in an order a reader can follow. Drop duplicates.
3. Write the draft in plain, direct language. Keep my phrasing where it is already good.
Rules:
- Every claim in the draft must come from my notes. Do not add statistics, quotes, examples, or anecdotes of your own.
- Where the draft needs something my notes do not have (an example, a number, a source), put [NEEDED: what is missing] in that spot.
- No filler introduction and no summary paragraph that repeats the piece.
After the draft, list:
- The notes you left out, and why.
- The weakest part of the argument as it stands.
My notes:
{{notes}}
A summary built around what the reader has to decide or do, with the numbers and dates kept exact and anything uncertain marked as such.
Summarize the document below for this reader: {{reader:a busy manager who has not read it}}
Length: {{length:about 200 words}}
Structure:
1. The point, in one or two sentences. If the document asks the reader to decide or do something, say that first.
2. The key facts that support it, as bullets. Keep every number, date, name, and amount exactly as written.
3. What is still open, uncertain, or disputed in the document.
4. What the reader needs to do, and by when, if the document says.
Rules:
- Use only what is in the document. Do not add background from your own knowledge.
- Do not soften or strengthen the document's claims. If it says "may", do not write "will".
- If the document contradicts itself, point to both places.
- If a part matters but is too detailed to summarize, say where it is so the reader can go to it.
Document:
{{document}}
Matches your real experience to what the posting asks for, rewrites bullets around results, and tells you where the gaps are. It never invents experience.
Help me tailor my resume to a specific job. Use only experience I actually have.
Step 1. Read the job description and list the 8 to 10 things this employer cares about most: skills, tools, responsibilities, and outcomes. Rank them by how much weight the posting gives them.
Step 2. For each one, mark my resume as:
- Strong match: quote the line that shows it.
- Partial match: say what is there and what is missing.
- No match.
Step 3. Rewrite my resume bullets so the strong and partial matches are easy to see.
- Start each bullet with what I did, then the result. Keep any numbers I gave.
- Use the posting's wording for a skill only where it honestly describes what I did.
- Put the most relevant bullets first within each role.
- Cut or shorten bullets that do nothing for this job.
Step 4. Write a 2 to 3 line summary for the top of the resume, aimed at this role.
Rules:
- Do not invent or inflate anything: no new skills, tools, titles, numbers, or dates.
- Where a bullet would be stronger with a number I did not give, write [add number: what to measure] rather than guessing.
- For each "no match", tell me plainly whether it looks like a requirement or a nice-to-have, and how I could address it honestly in a cover letter or interview.
Job description:
{{job_description}}
My resume:
{{resume}}
Fixes grammar, spelling, and punctuation, and flags unclear sentences without rewriting them. You see every change and why it was made.
Proofread the text below. Fix errors; do not restyle it.
English variant: {{variant:keep whatever the text already uses}}
Fix:
- Spelling, grammar, punctuation, and capitalization.
- Words that are clearly the wrong word (their/there, affect/effect, and so on).
- Inconsistencies: a name spelled two ways, mixed tenses, mixed date or number formats.
Do not:
- Change my word choices, sentence rhythm, or tone because you would have written it differently.
- Shorten, expand, or reorder anything.
- "Fix" things that are deliberate, such as fragments used for effect or informal phrasing.
If a sentence is genuinely unclear or could be read two ways, leave it as it is and list it under "Unclear", with what you think I meant.
Return:
1. The corrected text.
2. A table of changes: original, corrected, reason.
3. "Unclear", if there is anything.
Text:
{{text}}