hermes

Write an email to a professor

Writes a student's email to a professor or adviser about an extension, a grade, research, a recommendation or an absence, with correct etiquette and one clear ask.

context

Professors receive many student emails and answer the ones that are easy to act on: a subject line with the course, a correct title, the student identified, one clear request and the facts needed to decide. They tend to ignore or bristle at emails that start "Hey", ask a question the syllabus answers, ask "did I miss anything important?", argue for points, or arrive the night before a deadline with no plan. Each purpose has its own conventions:

  • Extension: ask before the deadline, give the reason briefly (no medical detail; "documentation is available through student services" is enough), say what is done, and propose a specific new date.
  • Grade question: ask to understand the marking against the rubric, not to negotiate points; check whether the course has a waiting period or regrade form; offer office hours.
  • Research inquiry: show you read their recent work (name it), say what you bring (courses, skills, hours per week), ask a specific question (is there space in the lab this term?), attach a CV.
  • Recommendation: ask at least three to four weeks ahead, ask whether they can write a strong letter, give an easy way to decline, and promise a packet (CV, statement, deadlines, submission links, courses and grades with them).
  • Absence: inform rather than ask permission unless attendance rules require it, and ask how to catch up after checking the course site.
task

Write a email to a professor or adviser for .Only if [DEADLINE] is given: Relevant date: .

key facts

  1. If the facts lack something the ask cannot work without (for an extension: the assignment and its due date; for a recommendation: what the letter is for and its deadline; for a research inquiry: who the professor is or what their work is about), ask up to two questions and stop.
  2. If the facts show the answer is probably in the syllabus or on the course site (late policy, regrade process, attendance rules), say so first under Before sending and still draft the email in case it is not.
  3. Subject line: course code plus the request, for example "BIO 214 sec. 2: extension request for Lab Report 3 (due 14 Nov)".
  4. Salutation: "Dear Professor [Surname]," or "Dear Dr [Surname]," using the name and title in the facts; if unknown, use [Surname]. Never first names unless the facts say the professor invited it.
  5. First sentence: who the student is (name placeholder, course, section). Second sentence: the ask, specific and answerable with yes, no or a date.
  6. Then the minimum supporting facts for the purpose, following the conventions above. Keep private matters private: name the category (medical, family emergency) only if the student wants to, never the details.
  7. Close with what the student will do next or attach, thanks in one line, and a sign-off with full name and student number placeholder where the institution uses one.
constraints
  • Under about 150 words in the body (a research inquiry may run to about 200).
  • One ask per email. If the facts contain two requests, put the more urgent in the email and mention the other under Before sending.
  • Use only the facts given. Never invent reasons, grades, papers, documentation or deadlines, and never write a false excuse even if asked; offer an honest version instead.
  • Respectful and direct: no "Hey", no "Sorry to bother you", no pleading, no entitlement ("I deserve an A").
  • Write in the conventions of the country in the facts if stated (for example "Dear Professor" in the US, "Dear Dr" for many UK academics); otherwise use "Professor".
output format

Email

Subject line, then the body.

Before sending

Bullets: syllabus or policy checks, attachments, placeholders to fill, and when to follow up if there is no reply (usually after three to five working days).

3 required values still a placeholder; the assistant will ask for them.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Writing and communication
category
Email
level
Beginner
made for
Student
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-03
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install write-email-to-professor --target claude-code

This entry is in the full catalog, not the curated set the skills installer and plugins carry, so install it with the Hodios CLI.

pairs well with

All of Email
PromptEmail

Write a follow-up to an unanswered email

Writes a polite follow-up to an unanswered email that adds new context, makes the ask easier to answer and sets a gentle deadline, in three escalation levels from nudge to final note.

write-follow-up-email
PromptEmail

Ask someone to be a reference

Asks a former manager, teacher or colleague to act as a reference, making it easy to say yes or no, with the role, the timeline and what they could speak to. Use when job hunting or applying.

request-reference
PromptEmail

Write a professional email

Drafts an email from rough intent with a specific subject line, the ask in the first two sentences and the right tone for the relationship, marking any detail it would otherwise have to invent.

write-professional-email
PromptEmail

Decline a request gracefully

Declines a request or invitation clearly and kindly in the first lines, gives an honest brief reason if wanted, offers only real alternatives and preserves the relationship.

decline-request-gracefully
PromptEmail

Reply to an email

Drafts a reply that answers every question and request in a received email from your stated position, matches its formality, proposes next steps and flags points you have not decided.

reply-to-email
PromptEmail

Triage an inbox

Sorts a batch of emails into reply, delegate, schedule and archive by your priorities, flags suspicious messages, and drafts the short replies and delegation notes.

triage-inbox