Ravi email-writing
by @raunaksingwi
Best practices for writing high-quality emails that look professional and avoid spam filters. Reference this before composing, replying, or forwarding emails...
clawhub install ravi-email-writingπ About This Skill
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.
Email Writing Guide
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.
Subject Lines
HTML Body Structure
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:
Opening line that states the purpose.
Supporting details in a second paragraph.
- Key point one
- Key point two
Closing with a clear next step or ask.
Best,
IDENTITY_NAME
Don't do this:
Plain text with no tags at allOr this:
Using br chains
instead of paragraphs
Rules:
tags for section headers (not )
/ for lists, not dashes or asterisksdescriptive text for links β never bare URLs, , or wrapper tags β the email system adds these
chains β use separate tags insteadravi auth statusRecommended Template
Copy-paste starting point for most emails:
ravi email compose \
--to "recipient@example.com" \
--subject "Specific subject under 60 chars" \
--body "Hi Alex,
I'm reaching out about [specific topic]. [One sentence of context.]
[Core message β what you need, what you're sharing, or what you're asking.]
- [Key point or action item]
- [Key point or action item]
[Clear next step β what should the recipient do?]
Best,
YOUR_NAME
"
Tone and Style
tagAnti-Spam Essentials
These rules help your emails land in the inbox, not spam:
instead.Common Mistakes
| Mistake | Why it's bad | Do this instead |
|---------|-------------|-----------------|
| Plain text in --body | Renders as one blob, no formatting | Wrap everything in tags |
| chains | Looks spammy, inconsistent spacing | Use separate 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 | descriptive text |
| 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 |