email-draft-in-voice
GitHub基于用户语音画像起草或回复 Gmail 邮件。先加载配置文件，读取完整邮件线程，按指定风格生成草稿并自检，经用户确认后调用工具创建草稿，确保语气符合个人设定且不擅自发送。
Trigger Scenarios
Install
npx skills add yc-software/qm --skill email-draft-in-voice -g -y
SKILL.md
Frontmatter
{
"name": "email-draft-in-voice",
"description": "Draft Gmail in the user's own voice from the voice profile built by email-voice-profile. Drafts only; the user reviews and sends.",
"requiredCapabilities": [
"egress:gmail.googleapis.com"
]
}
Draft email in the user's voice
Use 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".
Load the profile first — never freehand
Read voice/email-voice-profile.md from the workspace. If it doesn't exist, 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.
Draft
- Read the full thread you're replying to with
gmail.py thread THREAD_ID --full— never draft from a snippet or excerpt; a question below the fold would go silently unanswered. Match the register the profile prescribes for this audience. - Write the body to a file — plain text, one line per paragraph, blank line between.
- Self-check against the profile before showing anything: opener and sign-off drawn from their real ones, sentence rhythm right, no anti-pattern present. If a sentence could appear in anyone's email, rewrite it or cut it.
- Show the user the exact text and ask for approval before creating any draft.
Gmail
Use the google-workspace skill's helper (the user's OAuth token is already on your computer):
python3 skills/google-workspace/scripts/gmail.py draft --to a@b.com --subject '...' --body-file body.txt
python3 skills/google-workspace/scripts/gmail.py reply MESSAGE_ID --body-file body.txt [--all]
Sending (send-draft) only ever fires on a draft the user explicitly approved for
sending, per that skill's rules.
Afterward
Tell the user where the draft landed in Gmail Drafts and keep the draft id in the workspace so it can be updated. If they edit your text, notice what they changed — recurring corrections belong in the voice profile as hard rules; offer to add them.
Version History
- 7f2c916 Current 2026-08-02 21:46
