Tencent SkillHub · Content Creation

Ravi email-writing

Best practices for writing high-quality emails that look professional and avoid spam filters. Reference this before composing, replying, or forwarding emails...

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Best practices for writing high-quality emails that look professional and avoid spam filters. Reference this before composing, replying, or forwarding emails...

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.7.1

Provenance

Publisher: raunaksingwi
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 8 sections Open source page

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 flag in ravi email compose/reply/forward accepts HTML. Always use semantic tags — never pass plain text. Note: --subject is only used with ravi email compose. 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. <ul> <li>Key point one</li> <li>Key point two</li> </ul> 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 <h2> for section headers (not <h1>) Use <ul>/<li> for lists, not dashes or asterisks Use <a href="...">descriptive text</a> for links — never bare URLs No <html>, <head>, or <body> wrapper tags — the email system adds these No chains — use separate tags instead Get the identity name with: ravi identity list --json | jq -r '.[0].name'

Recommended Template

Copy-paste starting point for most emails: NAME=$(ravi identity list --json | jq -r '.[0].name') 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.] <ul> <li>[Key point or action item]</li> <li>[Key point or action item]</li> </ul> [Clear next step — what should the recipient do?] Best, $NAME" --json

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

MistakeWhy it's badDo this insteadPlain text in --bodyRenders as one blob, no formattingWrap everything in tags chainsLooks spammy, inconsistent spacingUse separate tags"Dear Sir/Madam"Outdated, signals mass emailUse the recipient's name or "Hi there"Wall of textNobody reads long emailsBreak into 2-3 short paragraphs"Click here" linksSpam trigger, bad accessibility<a href="...">descriptive text</a>Empty or vague subjectLow open rates, looks like spamBe specific: "Invoice #1234 for January"Excessive HTML stylingHigh tag-to-text ratio triggers filtersKeep formatting minimalNo signatureLooks impersonal, unprofessionalSign with identity name"Sent by AI" disclaimersUndermines trust, unnecessaryJust 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

Category context

Writing, remixing, publishing, visual generation, and marketing content production.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

1 Docs

SKILL.md Primary doc