Sauna Skills

                    ---
name: "Gmail Detective"
description: "User wants deep forensic analysis of their Gmail inbox. More thorough than basic Gmail setup.
Triggers: \"analyze my inbox deeply\", \"forensic email analysis\", \"who do I really email\",
\"understand my email patterns\", \"gmail detective\", \"deep inbox analysis\", \"email forensics\"
"
requiredApps: [gmail]
---

Forensically interrogate your inbox to build the most comprehensive understanding possible.

Gmail Detective goes far beyond basic inbox setup. It runs 100+ targeted searches across
personal facts, professional signals, financial patterns, lifestyle indicators, and life events.
It fetches full email bodies—not just snippets—so it can actually read and understand content.

The analysis uses longevity-first scoring: your most important contacts aren't necessarily
the most recent—they're the ones you've been consistent with over time. It identifies
dormant-important relationships (people who mattered but went quiet), maps your social
clusters, and finds bridge contacts who connect different parts of your life.

It reconstructs your life timeline from email evidence—moves, jobs, relationships, major
purchases. It analyzes your communication patterns—morning person or night owl, initiator
or responder, deep conversations or quick exchanges.

Takes 5-10 minutes. The result is a comprehensive profile that powers personalization
across everything you do.


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


## Skills

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

**Gmail Core API**
When: Shared Gmail API operations (list, fetch, parse)
Follow the instructions in: `skills/sauna/gmail.detective.forensic/references/skills/gmail.core.api/SKILL.md`

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

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


## Tasks

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

**Gmail Detective Forensic Analysis**
When: User wants deep forensic analysis of their inbox
Follow the instructions in: `skills/sauna/gmail.detective.forensic/references/recipes/gmail.detective.setup.md`



## State

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

**Service Profiles**
When: Check Gmail analysis including timeline, relationships, and patterns
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 existing profile before extracting facts (files: personal.md, interests.md, goals.md)
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).

**Work Overview**
When: Check existing work context before extracting work domain
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 Detective Forensic Presentation**
When: Presenting forensic findings to user
Read the documentation in: `skills/sauna/gmail.detective.forensic/references/gmail.detective.wow.md`

**Gmail Detective Extraction Guidelines**
When: Extracting facts from discovery categories
Read the documentation in: `skills/sauna/gmail.detective.forensic/references/gmail.detective.extraction.md`

**Gmail Detective Timeline Reconstruction**
When: Reconstructing life events
Read the documentation in: `skills/sauna/gmail.detective.forensic/references/gmail.detective.timeline.md`

**Gmail Detective Relationship Analysis**
When: Interpreting social graph
Read the documentation in: `skills/sauna/gmail.detective.forensic/references/gmail.detective.relationships.md`

**Gmail Detective Behavioral Patterns**
When: Analyzing communication patterns
Read the documentation in: `skills/sauna/gmail.detective.forensic/references/gmail.detective.behavior.md`

                  

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

2. Ensure Gmail is connected. Tell the user you'll do a deep forensic analysis of their inbox—contacts, patterns, timeline, and more. This takes 5-10 minutes. Run skills/sauna/gmail.detective.forensic/references/recipes/gmail.detective.setup.md.