Reply to Email — threaded reply with quoting and signature

Use this skill when the user wants to reply to an existing incoming message. For a brand-new email, use compose-email.

Steps

1. Locate the original

Parse the user's request for one of:

• Sender name or email — "reply to Ivanov", "reply to user@example.com"
• Subject keyword — "reply to the message about Q3 quote"
• UID — if explicitly given

Search strategy (use the first that matches):

1. UID given → skip to step 2.
2. Email given → mcp__yandex-mail__search_emails(from_addr="<email>", limit=5).
3. Name only → search_emails(from_addr="<name>", limit=5) (IMAP FROM matches the display-name part of From: too).
4. Subject keyword → search_emails(subject="<keyword>", limit=5).
5. Name + subject → combine both parameters in one call.

search_emails returns newest first. If exactly one result, use it. If multiple plausible matches, show a short list with UID, sender, subject and date, and ask which one. If zero results, say so plainly — do not fall back to send_email without an original.

2. Load the full original

Call mcp__yandex-mail__get_email with the UID to get the full body, sender, headers, and attachment list. Read it carefully and identify:

• What the sender is asking for
• Any specific questions to answer
• Any deadlines

3. Load the signature

Same as compose-email:

• echo $CLAUDE_PLUGIN_ROOT to get the plugin root
• Read $CLAUDE_PLUGIN_ROOT/assets/signature.html and signature.txt
• Check for $CLAUDE_PLUGIN_ROOT/assets/logo.jpg or logo.png
• If signature files do not exist, tell the user to run ./scripts/setup.sh and stop.

4. Draft the reply

• Address by name (use full first name + patronymic in Russian when known)
• Answer the sender's specific questions in order — bullet them if there are several
• If you commit to action, give a concrete timeframe
• If you need clarifications, ask specific questions
• Do not paraphrase the original — the server will quote it after your text

Match the language and formality level of the original message.

5. Show the draft and wait for confirmation

Show:

• To (the original sender's address)
• Subject (Re: <original subject>)
• Reply body (without the quote — that's appended automatically)

Ask: "Отправить ответ? / Send this reply?"

Send only after explicit yes.

6. Send

mcp__yandex-mail__reply_to_email(
  uid="<UID of the original>",
  body="<plain reply text + signature.txt> — DO NOT include the original; the server quotes it",
  html_body="<full HTML reply with signature, same template as compose-email>",
  inline_images=[{"path": "<abs path to assets/logo.{jpg,png}>", "cid": "plugin-logo"}],  # only if logo file exists
  reply_all=False,  # set True only if the user explicitly says "reply all" / "ответь всем"
)

Important behaviour: the server appends the quoted original to body (plain) but NOT to html_body. Most modern clients render the HTML version, so the user typically sees only the new reply text plus the signature. If the user wants the original quoted in the HTML version too, embed it manually as <blockquote style="border-left: 3px solid #ccc; padding-left: 12px; color: #666;">...</blockquote>.

7. Confirm

Reply briefly: "Ответ отправлен на <email>" / "Reply sent to <email>".

What not to do

• Do not reply to system addresses (noreply@, no-reply@, mailer-daemon@) — confirm first that the user actually wants this.
• Do not use reply_all=True without an explicit request — the Cc list may include people the user doesn't want to ping.
• Do not start with "Спасибо за ваше письмо!" / "Thanks for your email!" — get to the point.
• Do not duplicate the quoted text in your own body — the recipient will see the quote below.
• Do not send if you couldn't actually find the original — the threading would be broken. Report "not found" instead.