Write an out-of-office message
Writes out-of-office auto-replies for leave, travel or parental leave with the return date, who to contact for what, and what happens to messages meanwhile. Use before going away.
An out-of-office reply is read by someone who wanted something from you and now has to decide what to do. It works when it answers three questions in the first lines: when you are back, who can help with what in the meantime, and whether their message will be read or should be resent. It fails when it says "back Monday" with no date, routes everything to one overloaded colleague, or overshares. Auto-replies go to strangers, mailing lists and scammers too, so the external version should not reveal where you are, that a home is empty, private reasons such as health, or internal phone numbers and org details that help social engineering. The internal version can carry more detail: project links, channels and named owners.
Write out-of-office auto-replies for a audience in a tone.
Reason for absence (private context, not to be disclosed): First day back: Only if [BACKUP_CONTACTS] is given:
- Decide how much of the reason to say. Default to a neutral "I am out of the office". Mention a reason only when it helps the reader and is not private: a conference or business trip may be named without the location for external readers; parental leave may be mentioned if the reason says so; medical, family, bereavement or other personal reasons are never named.
- State the return date as a full date with weekday. If the return date is vague ("next week", "Monday"), use it but add
[confirm: full date]. If it is uncertain, say "until [month]" or "for an extended period" and lean harder on the contacts. - Route by topic, not just by name: "For invoices, contact…; for urgent issues with live orders, contact…". Use only the contacts given. If none are given, say messages will be answered after the return date and suggest the reader resend anything urgent then; do not invent a colleague or a shared inbox.
- Say what happens to messages: read on return, or (for absences of three weeks or more) not read and to be resent after the return date. Pick the one that fits the length of absence and say which you chose under Notes.
- Write the external version (if needed) first, then the internal one (if needed). The internal version may add links, channels and the people covering specific projects, if given.
- Write a one-line chat status (for Slack, Teams or similar) with the return date.
- Write a short settings checklist for the absence: schedule start and end, separate internal and external replies, reply once per sender, avoid replying to mailing lists where the client allows it, decline or hand over meetings in the calendar, and tell the backup contacts before switching it on.
- Body under about 80 words per version; the first two lines must carry the return date and where to go instead.
- Never reveal private reasons, the travel destination, personal phone numbers or a home address in the external version. If the backup contacts include a personal mobile, keep it out of the external version and say why under Notes.
- Never promise a reply time you cannot keep ("I will reply within 24 hours of my return") unless the input says so.
- No jokes or emojis in the formal tone; in the friendly tone, warmth is fine but no puns about the beach.
- Use only the names, addresses and numbers given; never invent them.
Auto-replies
For each audience: a subject line (for clients that allow one, such as "Out of office until Mon 17 Nov"), then the body.
Chat status
One line.
Settings checklist
Four to six bullets.
Notes
Placeholders to fill, what you left out on purpose and why. "None" if nothing.
Weak: "I'm currently out of the office with limited access to email. I'll respond as soon as possible upon my return." Strong: "Thanks for your email. I'm away until Monday 17 November and won't be reading messages. For invoices, please contact Priya at [email protected]; for anything else, I'll reply when I'm back."
2 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
- level
- Beginner
- made for
- Anyone, personal use, People manager, Consultant / freelancer, Founder / business owner
- 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
use in
npx @hermes-hq/hodios install write-out-of-office-message --target claude-codeThis 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 EmailWrite a handover document
Writes a handover for leave or a role change covering responsibilities, open work status, contacts, access, recurring tasks, known risks and first-week priorities, with gaps listed as questions.
write-handover-documentTriage 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-inboxWrite 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-emailDecline 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-gracefullyReply 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-emailAsk for feedback by email
Writes a request for feedback on a piece of work, a talk or your own performance, with two or three specific questions and an easy format, so people actually answer.
ask-for-feedback-by-email