Agent skill · ma08
gws-calendar-safe
Safely read, create, edit, split, cancel, or delete Google Calendar events through the named work, personal, or columbia gws aliases. Use for any agent-driven Calendar write, recurring-event change, exact event preview, writable-calendar inventory, or Calendar OAuth scope planning.
What it needs
About 3k tokens when loaded.
What this skill does
Safe Google Calendar Use gws-calendar-safe as the only Calendar write path. Leave the native Codex Google Calendar connector and the jiffy alias untouched. Required workflow 1. Require one explicit alias and one explicit calendar ID. Never infer either. 2. Read the exact calendar or event before proposing a write. 3. Generate a preview and show the user: title; exact start and end; timezone or all-day dates; account and calendar; location; visibility; conferencing; resolved reminders; attendee state; organizer state; recurrence scope; exact diff; notification behavior and risk. 4. Wait for explicit approval of that exact preview. Do not treat a general request as approval of a generated hash. 5. Apply the unexpired preview with its approval hash. For deletion, also pass the exact destructive confirmation from the preview. 6. Return the structured audit receipt. Commands Inventory and exact reads: Create from a local JSON request: The request must contain a title plus exact start and end objects. A new event always includes only the selected account as attendee and uses sendUpdates=none. Primary calendars use default visibility. Secondary calendars default to private. Calendar-default reminders are inherited and resolved in the preview. Google Meet is opt-in with "conference": "googleMeet". Edit one occurrence, a whole series, or this-and-following: Use an exact recurring instance ID for following. The helper rejects unsafe recurrence forms instead of guessing. If the source series has conferencing, a following split requires an explicit "conference": "googleMeet" for a new unique Meet or "conference": "remove"; existing conference data cannot be safely reused on a new series. Existing attendee lists are immutable. A non-organizer event can be previewed but cannot be applied. Attendee-bearing events require an explicit none or all notification choice. Destructive preview: Apply only after approval: OAuth gate Never start reauthorization silently. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ma08/gws-calendar-safe