CtrlK
BlogDocsLog inGet started
Tessl Logo

email-drafting

Draft an email matching the user's voice, with structured intent and CTA

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./surfsense_backend/app/agents/chat/multi_agent_chat/main_agent/skills/builtin/email-drafting/SKILL.md
SKILL.md
Quality
Evals
Security

Email drafting

When to use this skill

"Draft an email to ...", "reply to this thread", "write a follow-up to X". Plain "summarize the email" is not in scope — that's a comprehension task.

Voice

Search the KB for prior emails from the user to similar audiences (same recipient, same topic class). Mirror tone, opening style, sign-off, and length distribution. If there is no precedent, default to: warm, direct, no filler, short paragraphs, one clear ask.

Required structure

Every draft includes, in this order:

  1. Subject line — concrete, ≤ 8 words, no clickbait, no Re: unless replying.
  2. Opening (1 sentence) — context the recipient already shares; never restate what they wrote unless the thread is long.
  3. Body — the actual point in one short paragraph. Bullets only if there are >3 discrete items.
  4. Single explicit CTA — what you want the recipient to do, with a soft deadline if relevant.
  5. Sign-off — match the user's prior closing style.

Always offer alternatives

End your message with: "Want me to make it shorter, more formal, or add a different angle?" — give the user one obvious next step.

Repository
MODSetter/SurfSense
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.