Bidirectional calendar synchronization using Google Calendar API v3 with OAuth 2.0. Detects scheduling conflicts across multiple calendars, suggests optimal meeting times using FreeBusy API queries.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add aibot88/sec_skill_store --skill google-calendar-sync-conflict-resolver --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Google Calendar Sync Conflict Resolver?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aibot88-google-calendar-sync-conflict-resolver)More formats (shields.io, HTML) on the badges page.
---
title: "Google Calendar Sync & Conflict Resolver"
description: "Bidirectional calendar synchronization using Google Calendar API v3 with OAuth 2.0. Detects scheduling conflicts across multiple calendars, suggests optimal meeting times using FreeBusy API queries."
verification: "security_reviewed"
source: "https://developers.google.com/calendar/api"
author: "Google"
category:
- "Calendar, Email & Productivity"
framework:
- "OpenClaw"
---
# Google Calendar Sync & Conflict Resolver
Bidirectional calendar synchronization using Google Calendar API v3 with OAuth 2.0. Detects scheduling conflicts across multiple calendars, suggests optimal meeting times using FreeBusy API queries.
## Installation
Choose whichever fits your setup:
1. Copy this skill folder into your local skills directory.
2. Clone the repo and symlink or copy the skill into your agent workspace.
3. Add the repo as a git submodule if you manage shared skills centrally.
4. Install it through your internal provisioning or packaging workflow.
5. Download the folder directly from GitHub and place it in your skills collection.
## Documentation
- https://developers.google.com/calendar/api
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/google-calendar-sync-conflict-resolver/)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!