Professor Cold Email Drafter
A good professor cold email is short, specific, and easy to answer. It should prove the sender has done enough homework to be credible, while avoiding a long autobiography or generic praise.
Use this when
- The user wants to draft, review, shorten, or personalize an email to a professor or PI.
- The user is asking about PhD supervision, lab openings, research internships, RA roles, rotations, or meetings.
- The user has professor-fit notes and wants an outreach message.
- The user needs a follow-up after no response.
- The user wants subject lines or alternative tones for academic outreach.
Do not use this when
- The user has not yet figured out what the professor currently works on. Use
apply-research-direction-mapper first.
- The user wants a full SOP or application essay. Use
apply-sop-writer.
- The user is comparing many faculty or programs. Use
apply-program-fit-mapper.
- The user needs recommender strategy. Use
apply-recommendation-letter-strategist.
Workflow
1. Gather the minimum context
Identify:
- sender status: prospective PhD applicant, master's student, undergraduate, industry researcher, RA applicant, etc.
- target professor, department, institution, and program cycle if relevant
- purpose: ask about openings, request meeting, seek feedback, express fit before applying, or ask about RA/internship
- professor-specific evidence: recent paper, project, talk, grant, or lab theme
- sender-specific evidence: 1-2 strongest research experiences, technical skills, publications, or projects
- constraints: desired tone, word limit, attachments, CV link, deadline, country/program norms
If professor-specific evidence is missing, ask for it or draft a clearly marked placeholder version. Do not fabricate paper titles or claims.
1b. Set the address and register for the target system
Before drafting the opening, establish how this recipient should be addressed. references/address-and-formality.md carries the conventions — German-speaking systems expect a written-out title and no first names unless invited; Italian address is formal and often governed by a published bando; Anglophone systems use Dear Professor [Surname]; Nordic and Dutch academia are markedly informal.
Two rules override any convention:
- Take the recipient's title from their own institutional page, never from their name and never by inference. Where the page is ambiguous, choose the more formal option.
- Their stated preference and their reply signature win. Mirror the register they answer in.
Getting this right costs nothing and is read before the pitch. It does not substitute for the pitch — a perfectly addressed generic email is still generic.
2. Choose the email strategy
Select one primary ask:
- PhD fit / openings: ask whether they are considering students in the cycle and whether your direction fits.
- Research meeting: ask for a short conversation around a specific shared topic.
- RA / internship: ask whether there are opportunities and state availability or relevant skills.
- Follow-up: briefly restate context and make it easy to ignore if busy.
Avoid combining too many asks. Professors should be able to decide what to do after one quick read.
3. Build the message
Use this structure:
- Subject: specific, searchable, and not gimmicky.
- Opening: who the sender is and why they are writing.
- Professor-specific hook: one recent work/theme and what genuinely interests the sender.
- Sender fit: one compact evidence-backed bridge from the sender's background.
- Ask: one clear, low-friction request.
- Close: mention CV/materials if attached, thank them, and sign off.
Keep the main email around 120-220 words unless the user requests otherwise. Prefer concrete details over flattery.
4. Calibrate tone and risk
Check for:
- generic praise such as "your esteemed research" without evidence
- excessive biography or paragraph-long project summaries
- overclaiming fit or implying guaranteed supervision
- asking the professor to do work the applicant should do
- mentioning outdated research if recent directions differ
- unclear program cycle or opportunity type
- attachments or links referenced but not included
When useful, provide both a polished version and a shorter version.
5. Add follow-up guidance
For follow-ups:
- wait a reasonable interval unless there is a deadline
- keep it under 100 words
- forward or reply in the same thread
- add one new useful detail only if it materially changes the request
- avoid guilt, urgency pressure, or repeated chasing
Output formats
For drafting:
## Subject options
1. [Specific subject]
2. [Alternative]
## Draft email
Dear Professor [Last Name],
[Email body]
Best regards,
[Name]
## Why this works
- Professor-specific hook: ...
- Applicant fit bridge: ...
- Ask: ...
## Optional edits
- Shorter version: ...
- If attaching CV: ...
- If no reply: ...
For review:
# Cold Email Review
## Overall assessment
## Main risks
## Revised email
## Line-level fixes
Quality bar
A strong email should sound like a serious junior researcher, not a mass-mail template. It should be specific enough to show fit, short enough to respect the professor's time, and clear enough that the professor can reply with a simple yes, no, or suggestion.
1---2name: apply-cold-email-drafter3description: Draft, critique, and revise concise cold emails to professors for PhD applications, research internships, RA opportunities, lab rotations, or prospective-supervisor outreach. Use this skill whenever the user wants to contact a professor, ask about PhD openings, request a meeting, introduce their research background, mention a paper, follow up politely, or convert professor-fit notes into an email. This skill should trigger even if the user says "email a PI", "message a potential advisor", "reach out to faculty", or "cold mail" rather than "cold email".4---56# Professor Cold Email Drafter78A good professor cold email is short, specific, and easy to answer. It should prove the sender has done enough homework to be credible, while avoiding a long autobiography or generic praise.910## Use this when1112- The user wants to draft, review, shorten, or personalize an email to a professor or PI.13- The user is asking about PhD supervision, lab openings, research internships, RA roles, rotations, or meetings.14- The user has professor-fit notes and wants an outreach message.15- The user needs a follow-up after no response.16- The user wants subject lines or alternative tones for academic outreach.1718## Do not use this when1920- The user has not yet figured out what the professor currently works on. Use `apply-research-direction-mapper` first.21- The user wants a full SOP or application essay. Use `apply-sop-writer`.22- The user is comparing many faculty or programs. Use `apply-program-fit-mapper`.23- The user needs recommender strategy. Use `apply-recommendation-letter-strategist`.2425## Workflow2627### 1. Gather the minimum context2829Identify:3031- sender status: prospective PhD applicant, master's student, undergraduate, industry researcher, RA applicant, etc.32- target professor, department, institution, and program cycle if relevant33- purpose: ask about openings, request meeting, seek feedback, express fit before applying, or ask about RA/internship34- professor-specific evidence: recent paper, project, talk, grant, or lab theme35- sender-specific evidence: 1-2 strongest research experiences, technical skills, publications, or projects36- constraints: desired tone, word limit, attachments, CV link, deadline, country/program norms3738If professor-specific evidence is missing, ask for it or draft a clearly marked placeholder version. Do not fabricate paper titles or claims.3940### 1b. Set the address and register for the target system4142Before drafting the opening, establish how this recipient should be addressed. `references/address-and-formality.md` carries the conventions — German-speaking systems expect a written-out title and no first names unless invited; Italian address is formal and often governed by a published *bando*; Anglophone systems use `Dear Professor [Surname]`; Nordic and Dutch academia are markedly informal.4344Two rules override any convention:4546- **Take the recipient's title from their own institutional page**, never from their name and never by inference. Where the page is ambiguous, choose the more formal option.47- **Their stated preference and their reply signature win.** Mirror the register they answer in.4849Getting this right costs nothing and is read before the pitch. It does not substitute for the pitch — a perfectly addressed generic email is still generic.5051### 2. Choose the email strategy5253Select one primary ask:5455- **PhD fit / openings**: ask whether they are considering students in the cycle and whether your direction fits.56- **Research meeting**: ask for a short conversation around a specific shared topic.57- **RA / internship**: ask whether there are opportunities and state availability or relevant skills.58- **Follow-up**: briefly restate context and make it easy to ignore if busy.5960Avoid combining too many asks. Professors should be able to decide what to do after one quick read.6162### 3. Build the message6364Use this structure:65661. **Subject**: specific, searchable, and not gimmicky.672. **Opening**: who the sender is and why they are writing.683. **Professor-specific hook**: one recent work/theme and what genuinely interests the sender.694. **Sender fit**: one compact evidence-backed bridge from the sender's background.705. **Ask**: one clear, low-friction request.716. **Close**: mention CV/materials if attached, thank them, and sign off.7273Keep the main email around 120-220 words unless the user requests otherwise. Prefer concrete details over flattery.7475### 4. Calibrate tone and risk7677Check for:7879- generic praise such as "your esteemed research" without evidence80- excessive biography or paragraph-long project summaries81- overclaiming fit or implying guaranteed supervision82- asking the professor to do work the applicant should do83- mentioning outdated research if recent directions differ84- unclear program cycle or opportunity type85- attachments or links referenced but not included8687When useful, provide both a polished version and a shorter version.8889### 5. Add follow-up guidance9091For follow-ups:9293- wait a reasonable interval unless there is a deadline94- keep it under 100 words95- forward or reply in the same thread96- add one new useful detail only if it materially changes the request97- avoid guilt, urgency pressure, or repeated chasing9899## Output formats100101For drafting:102103```markdown104## Subject options1051. [Specific subject]1062. [Alternative]107108## Draft email109Dear Professor [Last Name],110111[Email body]112113Best regards,114[Name]115116## Why this works117- Professor-specific hook: ...118- Applicant fit bridge: ...119- Ask: ...120121## Optional edits122- Shorter version: ...123- If attaching CV: ...124- If no reply: ...125```126127For review:128129```markdown130# Cold Email Review131132## Overall assessment133134## Main risks135136## Revised email137138## Line-level fixes139```140141## Quality bar142143A strong email should sound like a serious junior researcher, not a mass-mail template. It should be specific enough to show fit, short enough to respect the professor's time, and clear enough that the professor can reply with a simple yes, no, or suggestion.