| license | Apache-2.0 |
| name | agentic-calendar-coordination |
| description | AI-powered calendar management and agent-based scheduling coordination. Covers calendar APIs (Google Calendar, CalDAV/iCal), AI scheduling assistants (Reclaim, Clockwise, Motion, Cal.com), building custom calendar agents with MCP, multi-calendar merging, timezone management, focus block protection, meeting fatigue detection, and agent-to-agent meeting negotiation protocols. Activate on: "calendar agent", "AI scheduling", "calendar coordination", "meeting scheduling", "calendar API", "focus time protection", "calendar optimization", "Google Calendar MCP", "Reclaim", "Clockwise", "Motion", "Cal.com", "smart scheduling", "calendar-aware agent", "timezone scheduling", "agent negotiation meetings". NOT for: manual calendar UI component design (use form-validation-architect), project management scheduling or Gantt charts (use project-management-guru-adhd), general time-tracking or pomodoro apps (use adhd-daily-planner for time-awareness), building the agent itself from scratch (use agent-creator).
|
| allowed-tools | Read,Write,Edit,Bash,Glob,Grep,WebSearch,WebFetch |
| metadata | {"category":"Productivity & Agents","tags":["calendar","scheduling","agent","productivity","google-calendar","timezone","meetings","mcp","coordination","focus-time"],"pairs-with":[{"skill":"always-on-agent-architecture","reason":"Calendar is a primary context source for persistent agents — event streams feed the memory hierarchy"},{"skill":"always-on-agent-inputs","reason":"Calendar events as contextual signals for agent behavior and energy-level inference"},{"skill":"adhd-daily-planner","reason":"ADHD-friendly scheduling patterns, time-blindness mitigation, and hyperfocus block protection"},{"skill":"daemon-development","reason":"Background daemon for continuous calendar monitoring, conflict detection, and proactive rescheduling"},{"skill":"multi-agent-coordination","reason":"Agent-to-agent meeting negotiation protocols and multi-party scheduling orchestration"}]} |
| category | Lifestyle & Personal |
| tags | ["calendar","scheduling","coordination","agentic","productivity"] |
Agentic Calendar Coordination
Build AI agents that negotiate meetings, protect focus time, and infer context from calendar data. Navigate timezone complexity, implement agent-to-agent scheduling, and architect custom calendar logic using Google Calendar API and MCP.
Decision Points
When Conflict Detected
Incoming meeting request conflicts with existing event
├─ Sender = manager/exec → Auto-accept, suggest moving existing
├─ Meeting = 1:1/urgent tagged → Propose alternative within 24h
├─ Focus block collision
│ ├─ Block priority = high (deep work) → Auto-decline
│ └─ Block priority = medium → Propose alternative time
└─ Double-booking with peer meeting → Counter with 3 alternative slots
Auto-Decline vs. Propose-Alternative Decision
Factors: sender_tier (exec/manager/peer/external) × meeting_type (1:1/team/all-hands) × focus_block_priority
If exec + any_type → Always propose alternative
If manager + (1:1 OR urgent) → Propose alternative
If peer + recurring + low_attendance → Auto-decline
If external + no_prior_relationship → Auto-decline with "use calendar link"
If during high_priority_focus_block → Auto-decline regardless of sender
Timezone-Aware Slot Selection
Multi-participant scheduling:
├─ All same timezone → Use local working hours (9-17)
├─ 2 timezones, <6h apart → Find overlap window
├─ 2 timezones, >6h apart → Early/late split (one takes 8am, other takes 6pm)
└─ 3+ timezones → Propose async alternative OR rotating schedule
Energy Model Slot Ranking
Time of day priority (descending):
1. 9-11 AM (peak cognitive) → Reserve for deep work, decline routine meetings
2. 11 AM-12 PM (sustained focus) → Allow important meetings only
3. 2-4 PM (collaboration sweet spot) → Prefer for team meetings
4. 4-5 PM (wrap-up) → Good for 1:1s, status updates
5. 1-2 PM (post-lunch dip) → Avoid complex meetings
Failure Modes
Timezone-Aware Recurring Conflicts
Symptoms: Weekly 9 AM meeting shows conflicts in winter but not summer; cross-timezone recurring fails after DST change
Detection: if recurring_event && timezone_conversion && conflict_pattern_seasonal
Fix: Always expand recurring with singleEvents: true, convert each instance to UTC for conflict checking, re-evaluate after DST transitions
Buffer Enforcement Thrashing
Symptoms: Agent repeatedly reschedules same meeting trying to create buffers; meetings bounce between slots
Detection: if same_meeting_rescheduled > 2 times in 24h for buffer_reasons
Fix: Lock in meeting after first reschedule, adjust buffer requirements dynamically based on meeting importance
