Calendar Hold Sync for Openclaw

A professional-grade synchronization skill that mirrors source Google calendars into target calendars as private busy holds to eliminate scheduling conflicts.

tdewitt
v1.0.1
Feb 17, 2026
2
2k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install calendar-hold-sync

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install calendar-hold-sync using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Calendar Hold Sync?

Calendar Hold Sync is a robust automation utility designed for developers and power users who need to maintain availability parity across multiple Google Calendar accounts. By leveraging the gog CLI, this skill creates idempotent hold events in target calendars, ensuring your time is protected without exposing sensitive event details. This tool is a vital addition to the library of Openclaw Skills for anyone managing complex, multi-account schedules.

The skill operates on a mapping-based configuration, allowing for precise control over source and target relationships. It excels at maintaining privacy by setting synchronized events to private visibility and busy transparency, effectively blocking off time while keeping the original event descriptions and attendees hidden from the target calendar's view.

Calendar Hold Sync Use Cases

  • Preventing double-booking across multiple independent Google Calendar accounts.
  • Creating private Busy blocks in a professional calendar based on personal life events.
  • Reconciling scheduling drift and backfilling legacy hold events with metadata for better management.
  • Automating calendar availability management via self-hosted cron jobs or real-time watch processes.

How Calendar Hold Sync Works

  1. The skill identifies source events within a user-defined lookahead window (defaulting to 30 days).
  2. It constructs a desired state of hold events, applying private visibility and busy transparency settings.
  3. Existing managed holds are detected by scanning for a specific SYNCV1 metadata prefix in event descriptions.
  4. A reconciliation engine performs idempotent operations: creating missing holds, updating drifted data, and deleting stale entries.
  5. Overlap policies are enforced to ensure that existing manual events in the target calendar are respected or handled according to configuration.
  6. The process concludes by logging changes and respecting safety limits like maxChangesPerRun.

Calendar Hold Sync Setup

First, ensure the gog CLI is installed and available in your PATH. Configure your OAuth credentials and accounts as follows:

gog auth credentials /path/to/client_secret.json
gog auth add [email protected] --services calendar
gog auth list

Once gog is configured, define your mapping JSON and validate the configuration using the Openclaw Skills CLI interface:

hold-sync validate-config
hold-sync reconcile --all --dry-run

Calendar Hold Sync Data Schema & Taxonomy

The skill manages source linkage using a SYNCV1 prefix and Base64url-encoded JSON metadata within the target event's description. The schema includes:

Field Description
srcAccount The email address of the source Google account
srcCalendar The unique identifier for the source calendar
eventId The original event ID from the source calendar
start / end The RFC3339 timestamps for the event duration
title The original title used for drift detection purposes

Calendar Hold Sync Advanced Features

  • Idempotent reconciliation that prevents duplicate entries and handles event drift automatically.
  • Polling-based watch mode with configurable intervals (e.g., 900 seconds) for near real-time synchronization.
  • Advanced backfill mode to upgrade legacy hold events by attaching SYNCV1 metadata to existing matches.
  • Safety controls including dry-run modes, max changes per run, and summary-based exclusion filters.
  • Support for custom gog command templates, allowing power users to override default CLI behavior safely.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*