菜单
Best practices for writing high-quality emails that look professional and avoid spam filters. Reference this before composing, replying, or forwarding emails with ravi-email-send.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Reply to the email you were just dispatched to handle. Use this skill whenever you are running under the ravix daemon (you'll see email headers `From:`, `To:`, `Subject:`, `Message-ID:` in your initial input) and the user has asked you to respond to that email. Do NOT use for composing new outbound emails — this is reply-only.
Manage contacts associated with your identity — list, search, create, update, and delete. Use ravi-contacts to resolve a person's name to their email or phone before sending (e.g. "email Alice" or "text Bob" → search contacts first). Do NOT use for website credentials (use ravi-passwords) or API keys (use ravi-secrets).
Send, compose, reply, reply-all, or forward emails with HTML formatting and attachments. Do NOT use for reading incoming email (use ravi-inbox) or for credentials (use ravi-passwords or ravi-secrets).
Get your agent identity (email, phone, owner name) and manage identities. Do NOT use for reading messages (use ravi-inbox), sending email (use ravi-email-send), or credentials (use ravi-passwords or ravi-secrets).
Read incoming SMS or email messages — verification codes, verification links, incoming mail. Do NOT use for sending email (use ravi-email-send) or managing credentials (use ravi-passwords or ravi-secrets).
Sign up for and log into services using your Ravi identity — handles onboarding, forms, verification codes read from SMS/email, and credential storage. Do NOT use for standalone inbox reading (use ravi-inbox) or email sending (use ravi-email-send).
| name | ravi-email-writing |
| description | Best practices for writing high-quality emails that look professional and avoid spam filters. Reference this before composing, replying, or forwarding emails with ravi-email-send. |
Write emails that look like they came from a real person — not an AI.
Good email hygiene improves deliverability, avoids spam filters, and gets responses.
The --body argument in ravi email compose accepts HTML. Always use semantic tags — never pass plain text.
Note: --subject is only used with the compose command. Reply and forward commands auto-derive the subject from the original message (prepending Re: or Fwd:).
Do this:
<p>Opening line that states the purpose.</p>
<p>Supporting details in a second paragraph.</p>
<ul>
<li>Key point one</li>
<li>Key point two</li>
</ul>
<p>Closing with a clear next step or ask.</p>
<p>Best,<br>IDENTITY_NAME</p>
Don't do this:
Plain text with no tags at all
Or this:<br><br>Using br chains<br><br>instead of paragraphs
Rules:
<p> tags<h2> for section headers (not <h1>)<ul>/<li> for lists, not dashes or asterisks<a href="...">descriptive text</a> for links — never bare URLs<html>, <head>, or <body> wrapper tags — the email system adds these<br> chains — use separate <p> tags insteadravi auth statusCopy-paste starting point for most emails:
ravi email compose \
--to "recipient@example.com" \
--subject "Specific subject under 60 chars" \
--body "<p>Hi Alex,</p><p>I'm reaching out about [specific topic]. [One sentence of context.]</p><p>[Core message — what you need, what you're sharing, or what you're asking.]</p><ul><li>[Key point or action item]</li><li>[Key point or action item]</li></ul><p>[Clear next step — what should the recipient do?]</p><p>Best,<br>YOUR_NAME</p>"
<p> tagThese rules help your emails land in the inbox, not spam:
<strong> instead.| Mistake | Why it's bad | Do this instead |
|---|---|---|
Plain text in --body | Renders as one blob, no formatting | Wrap everything in <p> tags |
<br><br> chains | Looks spammy, inconsistent spacing | Use separate <p> tags |
| "Dear Sir/Madam" | Outdated, signals mass email | Use the recipient's name or "Hi there" |
| Wall of text | Nobody reads long emails | Break into 2-3 short paragraphs |
| "Click here" links | Spam trigger, bad accessibility | <a href="...">descriptive text</a> |
| Empty or vague subject | Low open rates, looks like spam | Be specific: "Invoice #1234 for January" |
| Excessive HTML styling | High tag-to-text ratio triggers filters | Keep formatting minimal |
| No signature | Looks impersonal, unprofessional | Sign with identity name |
| "Sent by AI" disclaimers | Undermines trust, unnecessary | Just write naturally |