Google Calendar Group Scheduler Skill for Codex

Google Calendar Group Scheduler

Use this skill when the scheduling problem is the task.

Relevant Actions

• Use get_availability for attendee and room/resource busy windows once you know the concrete calendar IDs.
• Use search_events when you need event context, candidate-room history, or a clearer read on what is creating conflicts.
• Use read_event or search_events_all_fields when the attendee emails, manager contact, room email, or full source-event details need to be recovered from existing calendar events.

Workflow

• Ground the scheduling problem first: date window, duration, timezone, required attendees, optional attendees, and any hard constraints such as "this week", "afternoons only", or "avoid lunch".
• Normalize the request into explicit candidate windows before ranking anything.
• If attendee or room identities are referenced indirectly, such as "my manager", "same attendees", or "the room we usually use", search a bounded relevant window and read the likely source event before asking the user for contact details.
• Rank slots, do not enumerate everything. Optimize for a short list of strong options.
• Prefer slots that minimize conflict cost, are reasonably fair across timezones, and avoid fragmenting the day for the most constrained attendees.
• If no perfect slot exists, return the best compromise and state exactly who is impacted.
• If the meeting also needs a room, first narrow to attendee-compatible slots, then check likely rooms or resources against those shortlisted times.

Ranking Heuristics

• Favor required-attendee fit over optional-attendee fit.
• Favor slots that avoid very early or very late local times for distributed attendees.
• Favor slots that preserve lunch and avoid consuming the only large free block in someone's day unless the meeting is clearly important.
• Favor a small number of high-confidence options over a long weak list.
• When two slots are similar, prefer the one that causes less calendar fragmentation.

Output Conventions

• Return 2-4 candidate slots by default.
• For each slot, say why it works and who, if anyone, would be inconvenienced.
• If there is no clean option, say what tradeoff the best slot is making.