Skills / Email a professor
Email a professor
Get an email to a professor written and sent. Short, specific, in the person's own words. Use when they say "how do I email my professor", "can you check this email", or they keep putting the ask off.
Use this skill. Nothing to install.
Don't have an agent? · Raw file: skills/email-a-professor.md
Watch the first two minutes
This is how a session goes, four days of staring included. Click through it.
Scripted example of a real session.
What if I sound stupid
You won't, because the form is small and completely learnable, and professors read short direct emails all day without grading them. The skill workshops your draft against that form piece by piece, then has you read it aloud: it should sound like you on a good day. The apologies for existing get cut, the ask gets specific, and the thing actually gets sent before the session ends, which is the part four days of staring never delivers.
What you end up with
One sent email, and a form you now know cold. Here is a sent one, with the workshop's reasoning in the margin.
BIO 210, Tuesdays 10am
- The subject says the actual topic and names the course, so it gets opened and filed correctly. "Quick question" subjects get neither.
- Title and name, spelled right. Checked against the department page before sending. "Hey" is out; so is "Mrs." for someone with a doctorate.
- The ask lands in the second sentence with the deadline stated and the tight timeline acknowledged rather than hidden. Professors say yes faster to requests they can size at a glance.
- The professor's effort is minimized up front. Materials are offered before they have to be asked for, which saves a whole round trip of email.
Anatomy of a professor email
The skill edits every draft toward this shape:
- A Who you are and which class connects you. One line, no life story.
- B The ask itself, early and in plain words. Burying it reads as dodging it.
- C The specifics that let them decide fast: what for, due when.
- D Their effort minimized: documents offered, times proposed, nothing left for them to chase.
Questions people actually ask
Will it write the email for me, or my essays?
No. You type the draft, however rough, and the skill edits and explains; it will not compose the email even as a "template to personalize", because the fix-it conversation is where you learn the form, and the reply will go to someone who needs to sound like the sender. Same rule for essays and anything graded.
What if the professor never replies?
Replies take days and that is normal. A polite follow-up is fine after three or four business days, and the skill puts that date on your calendar before the session ends. When the reply comes, it helps you read the terseness straight: professors write short and it is rarely personal.
How long should the email be?
Under 150 words for almost every purpose. Long emails bury the ask and cost you replies. The skill also cuts apologies for existing and keeps exactly one plain thanks.
Is it too late to ask for a recommendation letter?
The comfortable window is three to four weeks before the deadline. Inside that, the ask is still possible; the email just has to acknowledge the timeline honestly and make declining easy. The skill will not let you pretend the deadline is farther than it is.
Is this free?
The skill is free, no account, no catch. The agent you paste it into may or may not be: Gemini has the widest free tier, Copilot's free tier is enough to try it, ChatGPT and Claude free plans can also run it in a chat.
Where to go from here
The asks this email usually leads to:
The same form, pointed at the working world:
Curious? Read the full skill — the exact instructions your agent gets
---
name: email-a-professor
category: school
description: Get an email to a professor written and sent. Short, specific, in the person's own words. Use when they say "how do I email my professor", "can you check this email", or they keep putting the ask off.
---
# email-a-professor
Help someone send one real email to a professor or
teacher, today. Most people in this situation have been staring at
a blank draft for days because the stakes feel high and the norms
are invisible. Your job is to make the norms visible, workshop
their draft, and get it sent before the session ends. The words are
theirs — a professor can smell a ghostwritten email, and the reply
will go to the person who did not write it.
## Rule zero: their words, really sent
They type the draft; you edit and explain. Do not compose the email
for them, even as a "template to personalize" — start from their
rough version, however bad, because the fix-it conversation is
where they learn the form. And the session ends with the email
actually sent, not saved as a draft. Ask to see the sent
confirmation.
## What is this email actually asking?
Get the real situation first:
- Who is the recipient, what course or context connects them, and
what exactly is being asked: a question about material, a grade
or extension conversation, office-hours access, joining a
research project, a recommendation letter.
- What is the honest deadline, if any? Recommendation letters need
three to four weeks of lead time; asking for less requires
acknowledging it in the email.
- Has anything relevant already happened — a missed class, a prior
email, a conversation? The email must not pretend otherwise.
- Checkable homework: if it is a research-interest email, have them
read one thing the professor actually wrote and name what caught
them. If it is a course question, confirm the syllabus does not
already answer it — syllabus questions burn goodwill.
## Workshop the draft
Have them write the rough draft, then edit together against the
form:
- Subject line that says the actual topic: "Question about Friday's
problem set (MATH 201)" beats "Question".
- Greeting with the recipient's preferred title and name as shown in the
syllabus, directory, or their own signature. If the title is unclear, ask
or use the form the institution publishes rather than guessing.
- First sentence: who they are and which class connects them. One
line.
- The ask, early and specific, with the professor's effort
minimized: propose times, attach the relevant document, state
the deadline. For letter requests: what it is for, when it is
due, and an offer to send their resume and talking points.
- Length: under 150 words for almost every purpose. Cut apologies
for existing ("sorry to bother you") and keep one plain thanks.
- Tone check: read it aloud. It should sound like them on a good
day — respectful, direct, no corporate varnish and no slang.
## Send and handle what comes back
1. Final pass: recipient address correct, attachment actually
attached, name spelled right, their school signature or full
name at the bottom.
2. They hit send, now, while you are there. Confirm it went.
3. Set expectations: replies take days; a polite follow-up is fine
after 3–4 business days ("following up in case this got
buried"). Put the follow-up date on their calendar.
4. When the reply arrives, help them read it straight — professors
write tersely and it is rarely personal — and workshop the
response the same way if one is needed.
## Done
- One email, in their words, actually sent
- Follow-up date on the calendar
- They can name the form's parts well enough to do the next one
alone — which is the point, because there will be many more





