Sauna Skills

                    ---
name: "Gmail Discovery"
description: "User wants to connect Gmail, set up their inbox profile, or learn their email patterns.
Triggers: \"connect gmail\", \"set up gmail\", \"learn my email patterns\",
\"who do I email\", \"my email contacts\", \"gmail profile\"
"
requiredApps: [gmail]
---

Know your inbox before you use it. This skill connects Gmail and builds a comprehensive profile of how you communicate—your key contacts, email patterns, and writing style.

In about 3 minutes, it analyzes your sent messages and inbox to identify who you email most (and who's mutual), extracts personal context from confirmations and receipts, and captures your writing voice for future drafts. The profile powers personalization across all Gmail operations.

Run once to set up, then periodically refresh as your patterns evolve.


**Limitations:** Read-only analysis—cannot send, modify, or delete emails.


## Skills

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

**Writing Voice Capture**
When: Analyzing writing style from sent emails
Follow the instructions in: `skills/sauna/gmail.inbox.discovery/references/skills/context.style.analyzer/SKILL.md`

**Entity Manager**
When: Resolving and merging contact entities
Follow the instructions in: `skills/sauna/gmail.inbox.discovery/references/skills/context.entity.manager/SKILL.md`


## Tasks

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

**Build Gmail Profile**
When: First use, user wants to connect Gmail, or refresh their profile
Follow the instructions in: `skills/sauna/gmail.inbox.discovery/references/recipes/gmail.inbox.setup.md`



## State

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

**Service Profiles**
When: Check existing Gmail profile
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.

**User Profile Facts**
When: Check user context extracted from Gmail (files: personal, interests, goals)
Use this directory: `documents/user/profile/[file=personal|goals|interests|ideology].md`
Usage Guide: Core user knowledge organized by life domain. Each domain gets its own file: personal.md (location, family, birthday, routines, relationships), goals.md (career goals, milestones, learning targets), interests.md (hobbies, media, communities), ideology.md (political compass results, values assessments).
Work context (role, company, team) lives in state:work.context.overview, not here.
UPDATE when facts emerge from conversations or service integrations. Include source attribution (e.g., "From Gmail:", "From Slack:") for automatically discovered facts. Track progress on goals when mentioned. This is the foundation for understanding the user - check here before asking questions they may have already answered.
File naming: lowercase domain name (personal.md, goals.md, interests.md, ideology.md).

**User Analysis Results**
When: Check captured writing style (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).

**People Directory**
When: Check extracted contacts
Use this directory: `documents/knowledge/people/*.md`
Usage Guide: Unified profiles for people the user interacts with or researches. Each person gets one file named by full-name slug (john-smith.md). Contains: name, relationship to user, contact methods (email, Slack handle, LinkedIn), interaction context, research findings (role, company, background, recent activity), and cross-references to service data.
CREATE when a person appears meaningfully in 2+ services, user explicitly saves someone, or user researches them. UPDATE when new context emerges. MERGE entries if same person discovered across services. Include research sections with findings, sources, and dates for meeting prep.
Skills should CHECK here before creating contact entries or doing research. This is the canonical "who does the user know" index including research data.

**Work Overview**
When: Check existing work context extracted from Gmail
Use this file: `documents/work/overview.md`
Usage Guide: Your company, role, and organizational context - the single source of truth for who you are at work. Sections:
## Company Name, industry, stage (startup/growth/enterprise), size, fiscal year, revenue.
## Role Your title, department, responsibilities, tenure.
## Team Direct reports (names, roles), team size, reporting structure, key collaborators.
## Key Metrics The numbers you track and are accountable for (OKRs, KPIs, quotas).
## Strategic Priorities Current quarter/year focus areas, major initiatives, company objectives.
## Tools HR systems, analytics platforms, CRM, communication tools you use.
## Culture Notes Company values, communication norms, decision-making style.
## ICP (if sales/CS role) Ideal customer profile: target titles, industries, company sizes, pain points.
UPDATE when: role changes, team reorgs, new quarter priorities, significant company changes. READ before: any task needing company/team context to personalize output.



## Knowledge

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

**Gmail Wow Moments**
When: Presenting profile insights to user
Read the documentation in: `skills/sauna/gmail.inbox.discovery/references/gmail.inbox.wow.md`

                  

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

2. Ensure Gmail is connected. Tell the user you'll analyze their inbox to understand their contacts, patterns, and writing style. Run skills/sauna/gmail.inbox.discovery/references/recipes/gmail.inbox.setup.md.