calendar-setup

Connect a Google Calendar to an OpenClaw PA with write access.

5|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/netanel-abergel/pa-skills --skill calendar-setup-netanel-abergel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: calendar-setup
Source: https://github.com/netanel-abergel/pa-skills/tree/main/skills/calendar-setup
Command: npx skills add https://github.com/netanel-abergel/pa-skills --skill calendar-setup-netanel-abergel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides an OpenClaw PA operator through connecting an owner's Google Calendar to the agent and ensuring the agent has explicit write permissions, eliminating confusion caused by dashboard-connected agent calendars and read-only access.

Core Features & Use Cases

  • Owner sharing walkthrough: Step-by-step instructions for the owner to share their calendar with the agent and set "Make changes to events".
  • Agent authentication & verification: Commands and procedures to add owner accounts to the gog CLI, re-authenticate, and verify write access with a test event.
  • Fallbacks and troubleshooting: Guidance for token refresh flows, direct API calls using stored credentials, multi-account handling, and common error resolutions (insufficient permissions, token expiry, blocked OAuth).
  • Use Case: Onboard a new PA to manage meetings across a user's work and personal calendars and verify the agent can create and delete events.

Quick Start

Connect the owner's Google Calendar to the PA using the setup steps, add the owner account with gog auth add, and verify by creating and deleting a test event.

Frequently Asked Questions about calendar-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect my Google Calendar to an OpenClaw agent with write access?

To connect Google Calendar to an OpenClaw agent with write access, share your calendar with the agent and set permissions to 'Make changes to events'. You then authenticate the agent using the gog CLI and verify write access by creating a test event.

Why does my OpenClaw agent fail to create or modify Google Calendar events?

Your OpenClaw agent fails to modify Google Calendar events due to insufficient permissions or token expiry. You must ensure the calendar is explicitly shared with the agent for write access and re-authenticate using the gog CLI or direct OAuth refresh token flow.

How do I set up multi-account Google Calendar configurations for an OpenClaw PA?

Multi-account Google Calendar configurations for an OpenClaw PA require adding each owner account via the gog auth add command. You must ensure the GOG_ACCOUNT variable is properly set and that calendar write scope is granted for each authenticated account.

What's the best way to troubleshoot OAuth token expiry and blocked authentication for Google Calendar integration?

Troubleshooting OAuth token expiry and blocked authentication for Google Calendar involves using the direct API calls with stored credentials or executing a direct OAuth refresh token flow. You can also resolve common errors by re-authenticating the owner accounts through the gog CLI.

Do I need the gog CLI to grant calendar write scope to my OpenClaw agent?

The gog CLI is the primary method used to add owner accounts and grant calendar write scope to your OpenClaw agent. Alternatively, you can bypass the CLI and use a direct OAuth refresh token flow to authenticate the agent and verify write access.

Can I use a dashboard-connected agent calendar to manage meetings instead of setting up owner sharing?

Dashboard-connected agent calendars only provide read-only access and cause confusion. You must explicitly share the owner's Google Calendar with the agent, set 'Make changes to events' permissions, and verify write access to properly create and modify events.