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`



## State

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

**User Analysis Results**
When: Reference when drafting emails to match user's voice (file: writing-style.md)
Use this directory: `documents/user/analysis/*.md`
Usage Guide: Personality and style analysis results. Each analysis type gets its own file: enneagram.md (type, wing, scores), compass.md (political position, ideology), writing-style.md (tone, formality, patterns by service), mbti.md, etc.
CREATE when user completes an assessment or analysis task. OVERWRITE on retake for assessments (enneagram, compass). UPDATE incrementally for observed patterns (writing style). Include source attribution for automatically discovered patterns.
File naming: lowercase analysis type with hyphens (e.g., writing-style.md).

**Service Profiles**
When: Check contact context for recipients
Use this directory: `documents/user/services/*.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, aggregate statistics, 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.

**Domain Preferences**
When: Check email preferences and past corrections (domain: email)
Use this directory: `documents/preferences/[domain].md`
Usage Guide: User preferences organized by domain. Each file stores preferences for a specific context (image_generation.md, newsletter.md, email.md, etc.). Include source (stated/inferred) and confidence inline when relevant. Read only the domains you need. Create new domain files as needed.

                  

                    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.