🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
πŸ¦€ ClawHub

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...

Versionv2.1.1
Downloads857
TERMINAL
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

  • 40-60 characters β€” long subjects get truncated on mobile
  • Be specific β€” "Q3 metrics review for Acme project" beats "Update"
  • No ALL CAPS β€” spam filters penalize this heavily
  • Avoid spam triggers β€” "free", "act now", "limited time", "click here", "urgent", "guaranteed", "no obligation"
  • Match the tone β€” casual for teammates, professional for external contacts
  • 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 all

    Or this:

    Using br chains

    instead of paragraphs

    Rules:

  • Always wrap text in

    tags

  • Use

    for section headers (not

    )

  • Use
      /
    • for lists, not dashes or asterisks
    • Use descriptive text for links β€” never bare URLs
    • No , , or wrapper tags β€” the email system adds these
    • No
      chains β€” use separate

      tags instead

    • Get the identity name with: ravi auth status
    • Recommended 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

    • First person, active voice β€” "I'll send the report Monday" not "The report will be sent"
    • Short paragraphs β€” 2-3 sentences max per

      tag

    • Get to the point β€” state your purpose in the first sentence
    • End with an action item β€” "Can you review by Friday?" not "Let me know your thoughts"
    • No filler phrases β€” cut "I hope this email finds you well", "Just wanted to touch base", "Per our previous conversation"
    • No robotic language β€” cut "I am writing to inform you", "Please be advised", "Kindly note"
    • Match the thread tone β€” if they're casual, be casual. If they're formal, be formal.
    • Anti-Spam Essentials

      These rules help your emails land in the inbox, not spam:

    • High text-to-HTML ratio β€” more words, fewer tags. Don't over-format.
    • No link shorteners β€” use full URLs. Spam filters distrust bit.ly, t.co, etc.
    • Max 2-3 links per email β€” more links = higher spam score
    • No ALL CAPS β€” not even for emphasis. Use instead.
    • No image-only emails β€” always include text content
    • One topic per email β€” don't cram multiple requests into one message
    • Don't repeat yourself β€” saying the same thing in different words triggers spam heuristics
    • 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 |

      Related Skills

    • ravi-email-send β€” CLI commands for compose, reply, reply-all, and forward
    • ravi-inbox β€” Read incoming email to understand what you're replying to
    • ravi-identity β€” Get your identity name for email signatures
    • ravi-feedback β€” Tell the Ravi team if email deliverability could be better