Compose Email — new business email from configured Yandex account

Use this skill when the user wants to send a NEW email. If they want to reply to an existing incoming message, use the reply-to-email skill instead.

Steps

1. Gather parameters

From the user's request extract:

• Recipient — name and/or email. If only a name is given and you don't have an email for them, ask. Don't guess.
• Goal — what the email should accomplish (send a quote, schedule a meeting, ask a question, deliver documents, etc.)
• Key points — what must be in the body
• Subject — if not given, propose one and ask for confirmation
• Attachments — if files are mentioned, ask for absolute paths

2. Load the user's signature

Run echo $CLAUDE_PLUGIN_ROOT to get the plugin root, then:

• Read $CLAUDE_PLUGIN_ROOT/assets/signature.html (HTML version of signature) — if the file does not exist, the user has not run setup yet; tell them to run ./scripts/setup.sh and stop.
• Read $CLAUDE_PLUGIN_ROOT/assets/signature.txt (plain version) — same fallback rule.
• Check whether $CLAUDE_PLUGIN_ROOT/assets/logo.jpg or assets/logo.png exists. If yes, the HTML signature already references cid:plugin-logo and you must pass the logo via inline_images. If neither exists, the HTML signature has no logo cell and you must NOT pass inline_images.

3. Draft the body

Match the user's stated language preference. If unclear, default to the language of the recipient's name. Use a business-formal tone:

• Open with a proper salutation (use the recipient's name; in Russian use full first name + patronymic when known)
• 2–4 short paragraphs: context first, then the point, then a clear call to action or question
• Close with "С уважением," / "Best regards," on its own line — the signature follows

Avoid: filler small talk, unnecessary exclamation marks, emoji, vague pleasantries.

4. ALWAYS show the draft and wait for confirmation

Show the user:

• To
• Subject
• Full body (without the signature — it will be appended automatically)
• Attachment list

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

Send only after an explicit yes (да, отправляй, send, go). On any other response, edit and re-show.

5. Send

Build the final email by combining the body and signature.

HTML version — the body in <p>...</p> paragraphs, then the loaded signature.html content:

<!DOCTYPE html>
<html><body style="font-family: -apple-system, 'Segoe UI', Arial, sans-serif; color: #1a1a1a; font-size: 14px; line-height: 1.5;">
<p>...body paragraph 1...</p>
<p>...body paragraph 2...</p>
<p style="margin-top: 24px;">С уважением,</p>
{{INSERT signature.html CONTENT HERE}}
</body></html>

Plain version — the body, a blank line, then "С уважением," / "Best regards,", then signature.txt content.

Tool call:

mcp__yandex-mail__send_email(
  to_email="<email>",
  subject="<subject>",
  body="<plain body + signature.txt>",
  html_body="<full HTML above>",
  inline_images=[{"path": "<absolute path to assets/logo.jpg or .png>", "cid": "plugin-logo"}]  # ONLY if logo file exists
                # otherwise omit this parameter entirely
  attachments=["<paths>"]  # only if user provided files
)

6. Confirm completion

Reply briefly: "Отправлено на <email> (тема: <subject>)" / "Sent to <email> (subject: <subject>)". List attachments if any.

What not to do

• Do not send without explicit confirmation, even if the user's request looks like an unambiguous command.
• Do not pass inline_images if the logo file doesn't exist on disk — the email will fail to build.
• Do not invent a recipient email address from memory or guess at a domain — ask.
• Do not skip the plain-text body — old clients and spam filters need it.
• Do not edit assets/signature.html from this skill — that's the setup script's responsibility. If the user wants a different signature, tell them to re-run ./scripts/setup.sh (after deleting the old signature.html and signature.txt).