When should you use it?
- You're contacting hiring managers or recruiters about specific roles
- You have a list of contacts and the job descriptions
- You want each email tailored but don't have hours to write them
Not for: Mass emailing people with no relevant opening; keep it to roles that fit
What do you need, and what do you get?
You need
- A spreadsheet with name, company, role, contact email and job description link
- Your resume
- A short note on what you're looking for
You get
- One Gmail draft per contact, tailored to the role and your experience
- A summary sheet showing which draft matched which role
- A list of rows skipped for missing information
How does it work, step by step?
- Build the sheetCollect contacts you found yourself, the role, and the job description link.
- Give it your resumeAdd a few lines on the kind of role you want and achievements to highlight.
- Generate draftsUse our prompt so it writes one short email per row and saves drafts only.
- Edit and sendRead each draft, fix anything off, and send from your own account.
The prompt
Our own prompt, inspired by Pratyush Pandey (@Pratyush2241) and written to work in Claude Cowork, ChatGPT agent and Grok Bot. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Use my resume ({resume}) and the spreadsheet {sheet}, which lists contact name, company, role, email and job description link. For each row: read the job description, pick the two or three parts of my experience that match it best, and write a short email (under {word_limit} words) to the contact about that role, with a clear ask for a conversation. Save each as a Gmail draft addressed to the contact. Don't send anything. Don't mention personal details about the recipient. If a row has no job description or email, skip it. At the end, give me a table: row, role, draft subject, and any rows skipped.
Inspired by Pratyush Pandey (@Pratyush2241): Job outreach emails drafted by Claude Cowork. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Personalization can overreach, mentioning details about the person that feel invasive. Keep it to the role and the company.
- Check facts about the company before sending; models sometimes invent recent news.
Our take
Job outreach works best when each note is specific to the role, and that's exactly what takes the time. Pratyush's setup handles the tailoring by matching the job description against his resume and stops at the right place, leaving drafts in Gmail to review and send. That's the boundary we'd insist on, because a stream of generic or slightly wrong emails from your address hurts your search. Our prompt keeps emails short, ties each one to the role and your real experience, avoids personal details about the recipient, and flags rows where the job description is missing rather than guessing. It also produces a summary sheet so you can track which drafts you've sent. In our dry run with a made-up sheet of 8 contacts and a sample resume, it created 7 drafts of around 110 words, each naming the role and two matching achievements, skipped 1 row with no job description, and sent nothing.
Where the time goes back: Tailoring each email by hand takes a long time per contact; reviewing a ready draft takes a minute or two.
FAQ
Should it send automatically?
How long should each email be?
Source and credit
Inspired by Pratyush Pandey (@Pratyush2241). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Job outreach emails drafted by Claude Cowork
- Creator
- Pratyush Pandey (@Pratyush2241)
- Published on
- X
- Original date
- Oct 3, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Cowork
- AI dry run
- Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Drafts only; no personal details used.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 25, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.