hermes

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.

context

A good "no" is clear early, brief and warm. People damage relationships less by declining than by declining badly: a vague reply that sounds like "maybe" and has to be chased, a long justification that invites negotiation, excessive apology that makes the other person comfort the decliner, or a counter-offer the decliner does not actually want to honour. A reason is optional; a clear answer is not.

task

Write a message declining this request:

request

Only if [REASON] is given: Reason I can share: Only if [ALTERNATIVE] is given: Alternative I'm willing to offer:

  1. If it is unclear what is being requested, ask and stop.
  2. Infer the channel (email, chat, letter) and the relationship (boss, client, friend, stranger, organiser) from the request, and match its formality.
  3. Open with brief, specific thanks or acknowledgement that shows you read the request, then decline clearly within the first two sentences. Use unambiguous words ("I won't be able to", "I'm going to say no to this"), not "I'm not sure I can" or "probably not".
  4. Give the reason only if one was provided, in one sentence, without over-explaining. If none was provided, decline without a reason or with a neutral line such as "I can't take this on right now"; never invent one.
  5. Offer the alternative only if one was provided, stated specifically. If none was provided, do not offer to help in some other way, and do not suggest asking again later unless the user said so.
  6. End warmly and in a way that fits the relationship (wishing the event well, expressing interest in future work only if the user's input supports it).
constraints
  • At most one apology, and only if the relationship calls for it.
  • No invented reasons, commitments, referrals or future availability.
  • Keep the main message under 120 words. The short version is under 40 words, suitable for chat.
  • If the request is from a manager or client where saying no has consequences, keep the message respectful and note in Notes any part the user may want to discuss live instead of in writing.
output format

Message

Subject line if email, then the message.

Short version

A shorter version for chat or text.

Notes

One to three bullets: what to adjust (warmth, reason, door left open) and any risk in how it may land. "None" if none.

examples

Request: "Hi! Loved your talk last autumn. Would you speak at our 12 March meetup? 20 minutes on anything testing-related. Jordan" Reason: none given. Alternative: none. Message: "Hi Jordan, thanks for thinking of me for the March meetup, and for the kind words about my last talk. I won't be able to speak this time. I hope the evening goes really well." Why it works: the thanks uses only what Jordan wrote, the no is in the second sentence, and nothing is promised for later.

1 required value still a placeholder; the assistant will ask for it.

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
Anyone, personal use, People manager, Consultant / freelancer, Writer / author
risk
read-only
version
v1.0.1 · experimental
reviewed
2026-10-02
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 decline-request-gracefully --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill decline-request-gracefully -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

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

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
PromptEditing

Rewrite a text for tone

Rewrites a text in a target tone or register, such as warmer, firmer or more formal, without changing its facts, asks or commitments, and shows which tone dials moved.

rewrite-for-tone
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
PromptEmail

Build a personal email template library

Builds a personal library of reusable email templates for the user's recurring situations, in their own voice from sent examples, with placeholders, subject lines and when-to-use notes.

build-email-templates
PromptEmail

Request approval by email

Writes a bottom-line-first email asking a busy decision-maker to approve a budget, purchase, hire or exception, with options, cost, the risk of waiting and a one-line reply path.

request-approval-by-email