calendar-scheduling

What This Skill Does

The calendar-scheduling skill, also recognized as Temporal Cortex, serves as a sophisticated routing engine for all calendar-related AI operations. It acts as the central intelligence layer between your requests and a suite of specialized sub-skills that handle datetime resolution and complex calendar orchestration. By leveraging an open-source Rust-based MCP server, this skill allows your OpenClaw agent to bridge the gap between disparate calendar providers including Google Calendar, Microsoft Outlook, and standard CalDAV implementations. It abstracts away the complexity of cross-provider availability merging, ensuring that your agent maintains a unified view of your schedule while preventing conflicting bookings through an atomic Two-Phase Commit process.

Installation

To integrate this capability into your OpenClaw environment, execute the following command in your terminal or command-line interface: clawhub install openclaw/skills/skills/billylui/calendar-scheduling. Once installed, the skill will initialize the necessary MCP environment. For advanced users or developers building their own scheduling tools, you can also utilize the npm package @temporal-cortex/cortex-mcp to interface directly with the Rust-backed server. Ensure you have your OAuth credentials ready for your specific calendar providers, as the sub-skills will require these tokens to perform read/write operations against your calendars.

Use Cases

This skill is designed for high-frequency scheduling and resource management. Individual users benefit from hands-free meeting orchestration, where the agent automatically identifies mutual availability among multiple stakeholders and drafts invitations. Developers can utilize the infrastructure as a scheduling backend for custom applications, taking advantage of 18 distinct tools that handle everything from simple time-zone math to complex recurring meeting (RRULE) expansions. Whether you are managing personal appointments or coordinating enterprise-wide availability, the routing architecture ensures that intent is translated into the correct technical execution layer.

Example Prompts

1. "Check my availability for next Tuesday and find a 30-minute window between 2 PM and 5 PM for a sync with Sarah."
2. "List my events for tomorrow and move the 10 AM meeting to Thursday at the same time if my calendar is clear."
3. "Schedule a recurring weekly meeting for this team on Wednesday mornings at 9 AM, and draft an email invitation with the Zoom link."

Tips & Limitations

To get the best results, ensure your timezone settings are correctly configured within your agent profile, as the temporal-cortex-datetime layer relies heavily on accurate localization for math operations. Note that while the datetime-resolution sub-skill works immediately without authentication, the scheduling sub-skill requires active OAuth grants for your calendars. Avoid scheduling highly sensitive or private events if you are using public or shared instances of the MCP server. Always verify the output before the agent executes an atomic booking to ensure the intent correctly maps to your specific time zone preferences.