Gmail Search
skill icon Skill
Gmail Search
Search with plain English or power-user Gmail operators. Find emails by sender, subject, date, or content—"emails from Sarah last month about the project" just works. Beyond search: analyze your inbox patterns (who's flooding you, what's junk), generate daily or weekly digests of what matters, and deep-dive specific threads to understand the full conversation. All read-only—perfect for staying informed without inbox zero pressure.
Agent activation
User wants to search Gmail, analyze inbox patterns, or get email summaries. Triggers: "find email from", "search my inbox", "email digest", "who emails me most", "check my gmail", "what happened in email"
Limitations
Read-only—cannot send, archive, delete, or modify emails.
10 References
                    ---
name: "Gmail Search"
description: "User wants to search Gmail, analyze inbox patterns, or get email summaries.
Triggers: \"find email from\", \"search my inbox\", \"email digest\",
\"who emails me most\", \"check my gmail\", \"what happened in email\"
"
requiredApps: [gmail]
---

Search with plain English or power-user Gmail operators. Find emails by sender, subject, date, or content—"emails from Sarah last month about the project" just works.

Beyond search: analyze your inbox patterns (who's flooding you, what's junk), generate daily or weekly digests of what matters, and deep-dive specific threads to understand the full conversation. All read-only—perfect for staying informed without inbox zero pressure.


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


## Skills

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

**Gmail Discovery**
When: Need user's Gmail profile for context (contacts, patterns)
Follow the instructions in: `./skills/sauna/gmail.inbox.search/references/skills/gmail.inbox.discovery/SKILL.md`


## Tasks

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

**Search Gmail**
When: User wants to find specific emails or search their inbox
Follow the instructions in: `./skills/sauna/gmail.inbox.search/references/recipes/gmail.inbox.search.md`

**Analyze Inbox**
When: User asks about patterns, stats, or who emails them most
Follow the instructions in: `./skills/sauna/gmail.inbox.search/references/recipes/gmail.inbox.analyze.md`

**Inbox Digest**
When: User wants a summary of recent activity
Follow the instructions in: `./skills/sauna/gmail.inbox.search/references/recipes/gmail.inbox.digest.md`

**Thread Deep-Dive**
When: User wants to see a specific conversation thread
Follow the instructions in: `./skills/sauna/gmail.inbox.search/references/recipes/gmail.inbox.thread.md`



## UI

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

**Connection Profiles**
When: Check who user emails most and their Gmail patterns
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.

**Inbox Analysis**
When: Reference past inbox analytics
Use this file: `./documents/inbox/analysis.yaml`
Usage Guide: Aggregate inbox statistics updated after each digest run. Tracks: top senders by volume and response rate, peak email hours/days, average response times, label/folder distribution, and trend data (week-over-week changes). Structure as YAML with dated snapshots for historical comparison. Update incrementally—merge new data with existing stats rather than replacing. Used to prioritize inbox processing and identify communication patterns. Don't store individual email content—only aggregate metrics.

**Inbox Digests**
When: Reference previously generated digest summaries
Use this directory: `./documents/inbox/digests/*`
Usage Guide: Historical inbox summaries named by date (YYYY-MM-DD-daily.md, YYYY-WW-weekly.md). Each digest contains: priority threads requiring action, important updates grouped by sender/topic, and a quick-scan summary. Create new file per digest period—never overwrite past digests as they serve as searchable history. Keep last 30 daily and 12 weekly digests; archive older ones. Reference past digests to identify patterns or find "that email from last month." Don't duplicate full email content—summarize and link to thread IDs.



## Knowledge

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

**Gmail Inbox Overview**
When: Read before any Gmail search operation
Read the documentation in: `./skills/sauna/gmail.inbox.search/references/gmail.inbox.overview.md`

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

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

2. Ensure Gmail is connected. Tell the user you can search their inbox, analyze patterns, and generate digests. Ask what they're looking for.