ms-graph-calendar

What This Skill Does

The ms-graph-calendar skill empowers your OpenClaw AI agent to interface directly with Microsoft 365 environments. It acts as an automated scheduling assistant, capable of resolving employee identities, querying real-time free/busy availability, and identifying optimal meeting slots across teams. By integrating with the Microsoft Graph API, it ensures that your scheduling workflows are synchronized with actual calendar data rather than static schedules.

Installation

To install this skill, run clawhub install openclaw/skills/skills/artisong/ms-graph-calendar.

After installation, the initial setup requires Azure AD integration. Ensure your Azure App Registration has the Calendars.Read and User.Read.All application permissions granted by an administrator. Execute node skills/ms-graph-calendar/scripts/setup.js with your specific --tenant-id, --client-id, and --client-secret. These credentials will be stored securely with file permissions set to 600. Verify the connection by running the get-token.js script to ensure you receive a success status.

Use Cases

• Automated Team Syncing: Instantly find a one-hour window where the entire project team is free.
• Calendar Auditing: Quickly check if a specific colleague has a conflict before scheduling a high-priority meeting.
• Dynamic Scheduling: Use the nickname mapping feature to translate casual names like 'The Dev Team' into actual calendar email addresses, simplifying team communication.
• Meeting Optimization: Suggest meeting times across multiple time zones by leveraging the built-in Bangkok timezone default and date-range filtering.

Example Prompts

1. "Find a one-hour meeting slot for me, Alice, and Bob next Tuesday between 9 AM and 5 PM."
2. "Check if Sarah is free for a 30-minute sync tomorrow morning."
3. "List all my busy blocks for this Friday so I can prepare my agenda."

Tips & Limitations

• Nicknames First: Always curate your nicknames.md file. It drastically reduces API latency compared to performing a full Graph search for every name.
• Ambiguity Handling: If the tool returns multiple users for a single name, always ask the user for clarification before proceeding to avoid scheduling with the wrong individual.
• Permission Scope: Note that this skill requires Application Permissions, meaning it operates at an administrative level. Ensure your organizational policies allow for such access before deploying in a production environment.
• Error Handling: Always verify the result of the get-token.js script; if expired, the agent must trigger a refresh cycle to prevent failed API calls.