Sauna Skills

                    ---
name: "Calendar Reader"
description: "User wants to check their calendar, see what's scheduled, or find specific events.
Triggers: \"what's on my calendar\", \"today's meetings\", \"my schedule\",
\"this week\", \"when do I meet with [person]\", \"calendar for tomorrow\"
"
requiredApps: [google_calendar]
---

Check your schedule without opening Google Calendar. Ask about today, tomorrow, this week, or any specific date—and get a clear, organized view of what's on your calendar.

Events are presented intelligently: grouped by day, filtered to show real meetings (not your "Focus Time" blocks or birthday reminders), and annotated with who's attending. For long schedules, you'll get a summary first with the option to dive deeper.


**Limitations:** Read-only—cannot create, modify, or delete events. Cannot check availability or schedule meetings.


## Skills

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

**Calendar Discovery**
When: Need user's calendar profile for timezone and collaborator context
Follow the instructions in: `./skills/sauna/calendar.google.reader/references/skills/calendar.google.discovery/SKILL.md`

**Time Mastery**
When: Interpreting relative time expressions like 'this week' or 'next Tuesday'
Follow the instructions in: `./skills/sauna/calendar.google.reader/references/skills/world.time.mastery/SKILL.md`


## Tasks

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

**Read Calendar Events**
When: User asks what's on their calendar for a specific time
Follow the instructions in: `./skills/sauna/calendar.google.reader/references/recipes/calendar.google.read.md`



## UI

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

**Connection Profiles**
When: Check timezone and collaborator names
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.



## Knowledge

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

**Calendar Agent Rules**
When: Read before any calendar operation
Read the documentation in: `./skills/sauna/calendar.google.reader/references/calendar.google.rule.md`

**Google Calendar Guide**
When: Need Calendar API details (events, recurrence, attendees)
Read the documentation in: `./skills/sauna/calendar.google.reader/references/calendar.google.guide.md`

                  

                    1. Install Calendar Reader with: ```bash
rm -rf ./skills/sauna/calendar.google.reader && curl -fsSL "https://sk.ills.app/api/skill/calendar.google.reader/download" | tar -xzf - -C ./skills/sauna/ && cat ./skills/sauna/calendar.google.reader/SKILL.md
```. Do so silently without commentary.

2. Ensure Google Calendar is connected. Tell the user you can check their schedule. Ask what timeframe they want to see—today, this week, or a specific date.