Google calendar sync engine
My personal collection of custom AI Agent Skills for Claude Code. Contains production-grade architectural patterns and workflows for React, Firebase, Tailwind CSS, and Zustand.
npx -y skills add Chagai33/my-agent-skills --skill google-calendar-sync-engineAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generic full-featured Google Calendar synchronization engine structure
SKILL.md
1.8 KB, as published. Nobody here has run it
google-calendar-sync-engine
Overview
This skill implements a full-featured Google Calendar synchronization engine. It provides a React Context wrapper for OAuth and state management, an API service client for backend interactions (e.g., syncing single/bulk events, cleaning orphans), and UI components to manage calendar configuration.
It handles advanced use cases such as:
- Connecting to Google OAuth2.
- Managing "Primary" vs "Secondary" calendars to prevent polluting the user's main calendar.
- Bulk synchronization, rate limiting awareness, and background jobs.
- Error handling and accessibility (Focus Management, Screen Reader announcements).
Golden Templates
The templates/ folder contains extracted, abstracted files showing how the system fits together:
GoogleCalendarContext.tsx: The primary state machine Context wrapper.googleCalendar.service.ts: API client class bridging the frontend to cloud functions.GoogleCalendarModal.tsx: UI modal with connection warnings and accessibility.googleCalendar.ts: Utilities for transforming domain entities into Google Calendar events.
What NOT to do (Negative Constraints)
- DO NOT hardcode Google Client IDs or API keys. Always use environment variables (e.g.,
import.meta.env). - DO NOT block the main thread during bulk syncing. Offload bulk processing to background jobs/cloud functions and use optimistic UI updates.
- DO NOT store tokens insecurely in LocalStorage. Let the backend manage Refresh Tokens, or manage sessions safely via HTTP-only cookies.
- DO NOT bypass user consent or blindly sync to the user's primary calendar. Always encourage the creation of a dedicated secondary calendar for the app.