hermes

Invite a speaker

Writes an invitation to a speaker, guest expert or panelist with why them, the audience, the format, date options, what is offered and an easy reply path. Use for events, podcasts and classes.

context

Speakers and guest experts receive many invitations and decide in seconds based on four things: is this for me specifically, is the audience worth my time, what exactly would I be doing and when, and what do I get. Invitations get ignored when they open with a long description of the organisation, flatter generically ("we love your work"), hide whether it is paid, leave out the time commitment (preparation, travel, the slot itself), or make replying hard. Strong invitations name the specific piece of the speaker's work that fits, describe the audience concretely, state the format, length and dates, are upfront about money and logistics, say what the organiser will handle, and close with a simple yes, no or "tell me more" path. For well-known people, the invitation often goes through an agent or assistant and must contain everything they need to put it in front of the speaker.

task

Write a speaker invitation to .

event

Audience: Only if [OFFER] is given:

offer

Only if [DATES] is given: Dates:

  1. If the event's format or topic is unclear, or nothing is said about why this speaker, ask up to two questions and stop.
  2. If the input suggests the speaker is booked through an agent, bureau or assistant, address it to them, keep it factual and complete, and make it easy to forward.
  3. Subject: "[Invitation]: speak on [topic] at [event], [date or month]".
  4. Opening: the invitation in one sentence, and why them in one or two sentences tied to their specific work as given. If the input gives no specific work, use [need: their talk, article or project that fits] rather than generic praise.
  5. The audience: who, how many, and what they want to leave with.
  6. The ask: format, length, topic or angle (with room for them to shape it), in person or remote, and the total time commitment including any prep call or rehearsal.
  7. Dates: the options with time zone, and the date you need an answer by.
  8. The offer: fee or honorarium, travel and accommodation, recording and how it will be used, promotion. If unpaid, say so plainly and state what is offered instead, without calling it "exposure".
  9. What the organiser handles (AV, moderation, tech check, questions in advance) only as given or as placeholders.
  10. Reply path: a one-line yes, no, or "happy to talk", plus a short call offer. An easy decline ("if the timing doesn't work, a recommendation of someone else would be welcome") is optional and short.
  11. Write a short version (under about 70 words) for LinkedIn or a DM.
  12. Under "Have ready", list what to send once they accept: event brief, speaker form, bio and headshot request with deadline, run of show, recording consent.
constraints
  • Email body under about 200 words.
  • Use only facts given; never invent audience figures, fees, past speakers, sponsors or the speaker's work. Use [need: …].
  • Specific, warm and professional; no gushing, no "huge fan", no pressure tactics or false scarcity.
  • State money clearly in the first half of the email if it is unpaid or if the fee is a key detail.
  • If a recording will be published or reused, say so in the invitation, not after acceptance.
output format

Email

Subject line, then the body.

Short version

The short message.

Have ready

Bullets.

Notes

Placeholders and any facts to confirm. "None" if nothing.

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
Marketer, Content creator, Teacher / tutor, Operations
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 invite-speaker --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill invite-speaker -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the writing-communication plugin
claude plugin install hodios-writing-communication@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Email
PromptEmail

Write an event invitation

Writes an invitation email for a work social, workshop, offsite or community event with why to come, logistics, RSVP mechanics and accessibility notes, plus a reminder. Use when organising an event.

write-event-invitation
PromptPublic speaking

Prepare to moderate a panel

Prepares a panel moderator with a timed run of show, opening, speaker introductions, a question flow with follow-ups, tactics for dominant or quiet speakers, audience Q&A and a close.

moderate-panel
PromptPublic speaking

Write an emcee script

Writes an emcee script for an event with welcome, housekeeping, speaker introductions, transitions, ready-made filler for delays and a close, timed against the run of show.

write-emcee-script
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