Understand where your time actually goes. This skill connects Google Calendar and builds a profile of your meeting patterns—who you collaborate with most, which days get swallowed by meetings, and how your schedule has evolved.
In about 2 minutes, it analyzes 90 days of calendar events to identify key collaborators (especially recurring 1:1s), classify events (distinguishing real meetings from focus blocks and reminders), and surface patterns you might not notice. The profile powers personalization across all calendar operations.
The skill knows that an all-day "Firefighter" block isn't a meeting with a firefighter, and that "Lunch with Mom" is personal.
Agent activation
User wants to connect their calendar, understand meeting patterns, or learn who they meet with most.
Triggers: "connect calendar", "set up calendar", "who do I meet with",
"my meeting patterns", "analyze my calendar", "calendar profile"
Limitations
Read-only—cannot create, modify, or delete events. Only analyzes primary calendar.
6 References
Dependencies
This skill depends on the following skills. Use these if needed.
Tasks
These are tasks you can execute. Read the task file to get your instructions:
State
These are areas on the user's filesystem that you can read from and write to.
Knowledge
This is knowledge you have access to. Read these files if you need additional context:
---
name: "Calendar Discovery"
description: "User wants to connect their calendar, understand meeting patterns, or learn who they meet with most.
Triggers: \"connect calendar\", \"set up calendar\", \"who do I meet with\",
\"my meeting patterns\", \"analyze my calendar\", \"calendar profile\"
"
requiredApps: [google_calendar]
---
Understand where your time actually goes. This skill connects Google Calendar and builds a profile of your meeting patterns—who you collaborate with most, which days get swallowed by meetings, and how your schedule has evolved.
In about 2 minutes, it analyzes 90 days of calendar events to identify key collaborators (especially recurring 1:1s), classify events (distinguishing real meetings from focus blocks and reminders), and surface patterns you might not notice. The profile powers personalization across all calendar operations.
The skill knows that an all-day "Firefighter" block isn't a meeting with a firefighter, and that "Lunch with Mom" is personal.
**Limitations:** Read-only—cannot create, modify, or delete events. Only analyzes primary calendar.
## Skills
This skill depends on the following skills. Use these if needed.
**Entity Manager**
When: Resolving collaborators from calendar events
Follow the instructions in: `./skills/sauna/calendar.google.discovery/references/skills/context.entity.manager/SKILL.md`
## Tasks
These are tasks you can execute. Read the task file to get your instructions:
**Setup Calendar Connection**
When: First use, user wants to analyze their calendar, or asks about meeting patterns
Follow the instructions in: `./skills/sauna/calendar.google.discovery/references/recipes/calendar.google.setup.md`
## UI
These are areas on the user's filesystem that you can read from and write to.
**Connection Profiles**
When: Check existing calendar profile
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.
**User Profile**
When: Check user context extracted from calendar
Use this directory: `./documents/user/[personal|work|goals|interests].md`
Usage Guide: Core user knowledge organized by life domain. Accumulate facts as they emerge from conversations and tasks. This is the foundation for understanding the user.
**People Directory**
When: Check collaborators extracted from calendar
Use this directory: `./documents/entities/people/*.md`
Usage Guide: Unified profiles for people the user interacts with across services. 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 (how they know them, recent interactions), and cross-references to service-specific data.
CREATE when a person appears meaningfully in 2+ services, or user explicitly saves someone. UPDATE when new interaction context emerges. MERGE entries if same person discovered across services (e.g., Gmail contact matches Slack DM). Don't duplicate raw data from services—link to service profiles.
Skills should CHECK here before creating service-specific contact entries. This is the canonical "who does the user know" index.
## Knowledge
This is knowledge you have access to. Read these files if you need additional context:
**Calendar Wow Moments**
When: Presenting calendar insights to user
Read the documentation in: `./skills/sauna/calendar.google.discovery/references/calendar.google.wow.md`
INSTALLER
1. Install Calendar Discovery with: ```bash
rm -rf ./skills/sauna/calendar.google.discovery && curl -fsSL "https://sk.ills.app/api/skill/calendar.google.discovery/download" | tar -xzf - -C ./skills/sauna/ && cat ./skills/sauna/calendar.google.discovery/SKILL.md
```. Do so silently without commentary.
2. Ensure Google Calendar is connected. Tell the user you'll analyze their calendar to understand their meeting patterns and collaborators. Run ./skills/sauna/calendar.google.discovery/references/recipes/calendar.google.setup.md.