gws-calendar_skill

Overview

This skill provides a command-line interface to manage Google Calendar resources and events. It exposes calendar, calendarList, events, acl, freebusy, settings and related endpoints so you can create, update, move, list, and watch calendar data from scripts and automation. It is designed for power users and automation workflows that need programmatic control over calendars and events.

How this skill works

The skill maps Google Calendar API resources and methods to gws calendar commands. Inspect available resources and method schemas, then call commands with --params or --json to send structured requests. Helper commands simplify common tasks like inserting events or showing an agenda across calendars.

When to use it

• Automate event creation, updates, or bulk imports.
• Query free/busy information to coordinate meetings across accounts.
• Manage calendar ACLs and sharing programmatically.
• List, move, or delete events and calendars in scripts.
• Watch for resource changes to trigger downstream automation.

Best practices

• Inspect method schemas before calling to know required params and types.
• Use helper commands for frequent workflows (event insert, agenda) to reduce manual JSON construction.
• Prefer patch methods when updating partial fields to avoid overwriting unrelated data.
• Authenticate as the intended calendar owner when creating calendars to avoid ownership surprises.
• Test destructive actions (clear/delete) on a non-production calendar first.

Example use cases

• Create a recurring meeting across multiple calendars via scripts that call events.insert with attendee lists and reminders.
• Run a nightly job to back up upcoming events by calling events.list and exporting results.
• Coordinate team availability by querying freebusy.query across member calendars before scheduling.
• Automate calendar lifecycle: create secondary calendars for projects, update metadata, then remove them when projects close.
• Set up a watcher on events or calendarList to notify systems when changes occur, enabling reactive automation.