Sauna Skills

                    ---
name: "Gmail Draft Composer"
description: "User wants to draft, compose, or write an email in Gmail.
Triggers: \"draft an email\", \"write an email to\", \"compose email\",
\"help me reply\", \"email draft\", \"write to [person]\"
"
requiredApps: [gmail]
---

Draft emails that actually sound like you wrote them. This skill captures your Gmail writing style—your greetings, sign-offs, tone, and phrasing—then uses it to compose drafts that match your voice.

Tell it what you want to say in rough notes or bullet points, and get back a polished draft ready to review. Works for new emails or replies to existing threads. Drafts save directly to Gmail—review and send when you're ready.


**Limitations:** Cannot send emails directly—drafts must be sent manually from Gmail.


## Skills

This skill depends on the following skills. Use these if needed.

**Gmail Discovery**
When: Need user's writing style and contact context
Follow the instructions in: `./skills/sauna/gmail.draft.composer/references/skills/gmail.inbox.discovery/SKILL.md`


## Tasks

These are tasks you can execute. Read the task file to get your instructions:

**Create Email Draft**
When: User wants to draft or compose an email
Follow the instructions in: `./skills/sauna/gmail.draft.composer/references/recipes/gmail.draft.create.md`



## UI

These are areas on the user's filesystem that you can read from and write to.

**Writing Style**
When: Reference when drafting emails to match user's voice
Use this file: `./documents/user/writing_style.md`
Usage Guide: Captured writing style patterns organized by service (Gmail, Notion, Slack) - tone, formality, structure, phrases, greetings, signatures. Each service has its own section to preserve context-specific styles. Used to draft content matching the user's voice.

**Connection Profiles**
When: Check contact context for recipients
Use this directory: `./documents/connections/[service-name].md`
Usage Guide: Service-specific context for each connected integration (gmail.md, slack.md, notion.md). Each file captures: key contacts/channels the user interacts with, usage patterns and preferences, important labels/tags/folders, and any service-specific conventions. Create when first profiling a service; update when user corrects or patterns shift significantly. Don't duplicate raw API data—summarize what matters for task execution. Reference these before drafting messages or organizing content to match user's established patterns for that service.

**Stated Preferences**
When: Check explicit email preferences
Use this file: `./documents/preferences/stated.yaml`
Usage Guide: Explicit preferences the user has stated. Structured YAML with categories: communication (response length, formality defaults), scheduling (preferred meeting times, buffer preferences), content (formatting preferences, tone for different contexts), and tool-specific preferences.
WRITE when user explicitly states a preference ("I prefer...", "Always...", "Never..."). UPDATE when user changes a stated preference. Each entry includes: preference, context, and when it was stated.
Higher confidence than learned preferences—user explicitly said this.

**Learned Preferences**
When: Check past draft corrections
Use this file: `./documents/preferences/learned.yaml`
Usage Guide: Preferences inferred from user corrections and behavior patterns. Structured YAML with categories matching stated preferences.
WRITE when user corrects agent behavior (e.g., edits a draft, rejects a suggestion). Each entry includes: observation, inferred preference, confidence (low/medium/high), and supporting evidence count.
Lower confidence than stated—these are inferences. If user corrects the same thing 3+ times, consider it high confidence. PROMOTE to stated preferences if user confirms. DELETE if contradicted.



## Knowledge

This is knowledge you have access to. Read these files if you need additional context:

**Email Drafting Guidelines**
When: Drafting or composing an email
Read the documentation in: `./skills/sauna/gmail.draft.composer/references/gmail.draft.rules.md`

**Gmail Guide**
When: Need Gmail API details (search operators, attachments, replies)
Read the documentation in: `./skills/sauna/gmail.draft.composer/references/email.gmail.guide.md`

                  

                    1. Install Gmail Draft Composer with: ```bash
rm -rf ./skills/sauna/gmail.draft.composer && curl -fsSL "https://sk.ills.app/api/skill/gmail.draft.composer/download" | tar -xzf - -C ./skills/sauna/ && cat ./skills/sauna/gmail.draft.composer/SKILL.md
```. Do so silently without commentary.

2. Ensure Gmail is connected. Tell the user you can draft emails in their voice. Ask who they want to email and what they want to say.