Draft Gmail in the user's own voice from the voice profile built by email-voice-profile. Drafts only; the user reviews and sends.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills-seed/email-draft-in-voice/SKILL.mdUse this when the user asks you to write or reply to email as them — "draft a reply to this", "write back to her for me", "answer my inbox in my voice".
The profile lives in the user's Files, never on a particular computer. Find it by the
memory fact "Email voice profile is Files ", or failing that
GET $AGENT_API_URL/v1/files?q=email-voice-profile (header
x-agent-capability: $AGENT_API_TOKEN; take the newest match), then download it with
GET $AGENT_API_URL/v1/files/<id>/content. A missing file on disk means nothing; only
when memory and Files both come back empty does the profile not exist, and then run
the email-voice-profile skill first (personal DM only). Do not improvise a voice from
memory or from this conversation's tone. The profile's Hard rules and
Anti-patterns sections are constraints, not suggestions.
Use the selected email access skill to create or update the Gmail draft, preserving reply threading and recipients. Sending is a separate action and requires explicit approval of the draft for sending.
Tell the user where the draft landed in Gmail Drafts and keep the draft id in memory (one fact naming the thread and draft id) so a later turn on any computer can update it. If they edit your text, notice what they changed — recurring corrections belong in the voice profile as hard rules; offer to add them and republish the profile.
yc-software/qm
c94f65b
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.