Opening line that states the purpose.
\n\nSupporting details in a second paragraph.
\n\nClosing with a clear next step or ask.
\n\nBest,
IDENTITY_NAME
tags\nUse
tags instead\nGet the identity name with: ravi identity list --json | jq -r '.[0].name'" }, { "title": "Recommended Template", "body": "Copy-paste starting point for most emails:\n\nNAME=$(ravi identity list --json | jq -r '.[0].name')\n\nravi email compose \\\n --to \"recipient@example.com\" \\\n --subject \"Specific subject under 60 chars\" \\\n --body \"
Hi Alex,
\n\nI'm reaching out about [specific topic]. [One sentence of context.]
\n\n[Core message — what you need, what you're sharing, or what you're asking.]
\n\n[Clear next step — what should the recipient do?]
\n\nBest,
$NAME
tag\nGet to the point — state your purpose in the first sentence\nEnd with an action item — \"Can you review by Friday?\" not \"Let me know your thoughts\"\nNo filler phrases — cut \"I hope this email finds you well\", \"Just wanted to touch base\", \"Per our previous conversation\"\nNo robotic language — cut \"I am writing to inform you\", \"Please be advised\", \"Kindly note\"\nMatch the thread tone — if they're casual, be casual. If they're formal, be formal."
},
{
"title": "Anti-Spam Essentials",
"body": "These rules help your emails land in the inbox, not spam:\n\nHigh text-to-HTML ratio — more words, fewer tags. Don't over-format.\nNo link shorteners — use full URLs. Spam filters distrust bit.ly, t.co, etc.\nMax 2-3 links per email — more links = higher spam score\nNo ALL CAPS — not even for emphasis. Use instead.\nNo image-only emails — always include text content\nOne topic per email — don't cram multiple requests into one message\nDon't repeat yourself — saying the same thing in different words triggers spam heuristics"
},
{
"title": "Common Mistakes",
"body": "MistakeWhy it's badDo this insteadPlain text in --bodyRenders as one blob, no formattingWrap everything in tags 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 accessibilitydescriptive textEmpty 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"
},
{
"title": "Related Skills",
"body": "ravi-email-send — CLI commands for compose, reply, reply-all, and forward\nravi-inbox — Read incoming email to understand what you're replying to\nravi-identity — Get your identity name for email signatures\nravi-feedback — Tell the Ravi team if email deliverability could be better"
}
],
"body": "Email Writing Guide\n\nWrite emails that look like they came from a real person — not an AI. Good email hygiene improves deliverability, avoids spam filters, and gets responses.\n\nSubject Lines\n40-60 characters — long subjects get truncated on mobile\nBe specific — \"Q3 metrics review for Acme project\" beats \"Update\"\nNo ALL CAPS — spam filters penalize this heavily\nAvoid spam triggers — \"free\", \"act now\", \"limited time\", \"click here\", \"urgent\", \"guaranteed\", \"no obligation\"\nMatch the tone — casual for teammates, professional for external contacts\nHTML Body Structure\n\nThe --body flag in ravi email compose/reply/forward accepts HTML. Always use semantic tags — never pass plain text.\n\nNote: --subject is only used with ravi email compose. Reply and forward commands auto-derive the subject from the original message (prepending Re: or Fwd:).\n\nDo this:\n\n Opening line that states the purpose. Supporting details in a second paragraph. Closing with a clear next step or ask. Best, tags\nUse tags instead\nGet the identity name with: ravi identity list --json | jq -r '.[0].name'\nRecommended Template\n\nCopy-paste starting point for most emails:\n\nNAME=$(ravi identity list --json | jq -r '.[0].name')\n\nravi email compose \\\n --to \"recipient@example.com\" \\\n --subject \"Specific subject under 60 chars\" \\\n --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.] [Clear next step — what should the recipient do?] Best, tag\nGet to the point — state your purpose in the first sentence\nEnd with an action item — \"Can you review by Friday?\" not \"Let me know your thoughts\"\nNo filler phrases — cut \"I hope this email finds you well\", \"Just wanted to touch base\", \"Per our previous conversation\"\nNo robotic language — cut \"I am writing to inform you\", \"Please be advised\", \"Kindly note\"\nMatch the thread tone — if they're casual, be casual. If they're formal, be formal.\nAnti-Spam Essentials\n\nThese rules help your emails land in the inbox, not spam:\n\nHigh text-to-HTML ratio — more words, fewer tags. Don't over-format.\nNo link shorteners — use full URLs. Spam filters distrust bit.ly, t.co, etc.\nMax 2-3 links per email — more links = higher spam score\nNo ALL CAPS — not even for emphasis. Use instead.\nNo image-only emails — always include text content\nOne topic per email — don't cram multiple requests into one message\nDon't repeat yourself — saying the same thing in different words triggers spam heuristics\nCommon Mistakes\nMistake\tWhy it's bad\tDo this instead\nPlain text in --body\tRenders as one blob, no formatting\tWrap everything in tags\n tags\n\"Dear Sir/Madam\"\tOutdated, signals mass email\tUse the recipient's name or \"Hi there\"\nWall of text\tNobody reads long emails\tBreak into 2-3 short paragraphs\n\"Click here\" links\tSpam trigger, bad accessibility\tdescriptive text\nEmpty or vague subject\tLow open rates, looks like spam\tBe specific: \"Invoice #1234 for January\"\nExcessive HTML styling\tHigh tag-to-text ratio triggers filters\tKeep formatting minimal\nNo signature\tLooks impersonal, unprofessional\tSign with identity name\n\"Sent by AI\" disclaimers\tUndermines trust, unnecessary\tJust write naturally\nRelated Skills\nravi-email-send — CLI commands for compose, reply, reply-all, and forward\nravi-inbox — Read incoming email to understand what you're replying to\nravi-identity — Get your identity name for email signatures\nravi-feedback — Tell the Ravi team if email deliverability could be better"
},
"trust": {
"sourceLabel": "tencent",
"provenanceUrl": "https://clawhub.ai/raunaksingwi/ravi-email-writing",
"publisherUrl": "https://clawhub.ai/raunaksingwi/ravi-email-writing",
"owner": "raunaksingwi",
"version": "1.7.1",
"license": null,
"verificationStatus": "Indexed source record"
},
"links": {
"detailUrl": "https://openagent3.xyz/skills/ravi-email-writing",
"downloadUrl": "https://openagent3.xyz/downloads/ravi-email-writing",
"agentUrl": "https://openagent3.xyz/skills/ravi-email-writing/agent",
"manifestUrl": "https://openagent3.xyz/skills/ravi-email-writing/agent.json",
"briefUrl": "https://openagent3.xyz/skills/ravi-email-writing/agent.md"
}
}
chainsLooks spammy, inconsistent spacingUse separate \n
\n\n
IDENTITY_NAME
Using br chains
instead of paragraphs\n\n\nRules:\n\nAlways wrap text in for section headers (not
)\nUse
/
chains — use separate \n
\n\n
$NAME
chains\tLooks spammy, inconsistent spacing\tUse separate