Calendar Setup Skill

Minimum Model

Key Concept

Two accounts are involved:

• - Agent email — the PA's own Google account (e.g. agent@agentdomain.com)
• Owner email — the human's Google account (e.g. owner@company.com)

The agent needs access to the owner's calendar. These are separate Google accounts. The OpenClaw dashboard "calendar connected" status reflects the agent's own calendar — not the owner's. Verify write access explicitly.

Step 1 — Owner Shares Calendar

The owner does this in Google Calendar (not the agent):

1. 1. Open calendar.google.com as the owner
2. Find the primary calendar in the left sidebar (usually their name)
3. Click the three-dot menu → Settings and sharing
4. Under Share with specific people → click + Add people
5. Enter the agent email
6. Set permission to "Make changes to events" — not "See all event details" (that is read-only)
7. Click Send

✅ Done. The agent receives an email confirmation — no action needed from the agent side yet.

If owner can't find the calendar: Scroll down in the sidebar to "Other calendars".

If sharing is blocked: The owner's organization may restrict external sharing. They need to ask their IT admin to allow it.

Step 2 — Agent Authenticates

The agent runs:

CODEBLOCK0

Expected output of gog auth list:
CODEBLOCK1

If re-authenticating after a permission change or expired token:
CODEBLOCK2

If gog is not found: Check PATH or reinstall via your OpenClaw distribution.

If OAuth fails with "access blocked": Owner must allow access in Google Account → Security → Third-party apps.

Step 3 — Test Write Access

CODEBLOCK3

Check the owner's Google Calendar. The test event should appear within 30 seconds.

Delete it after verifying:

# Use EVENT_ID from the output of the create command above
GOG_ACCOUNT=owner@company.com gog calendar delete primary EVENT_ID

Common Issues and Fixes

Dashboard shows "connected" but agent can't write

Cause: Dashboard reflects the agent's own calendar, not the owner's.

Fix:

1. 1. Confirm owner shared their calendar with the agent email (Step 1)
2. Confirm agent ran gog auth add for the owner's account (Step 2)
3. Always use GOG_ACCOUNT=owner@company.com in all commands

"Insufficient permissions" error

Cause: Calendar was shared with read-only permission.

Fix: Owner goes back to Step 1 and changes the permission to "Make changes to events".

"Token expired" or authentication failure

CODEBLOCK5

Multiple calendars (work + personal)

CODEBLOCK6

macOS date command

CODEBLOCK7

Useful Commands

CODEBLOCK8

Heleni-specific: Direct API Workaround (when gog CLI auth fails)

INLINECODE6 requires a browser — doesn't work on a server. Use the pre-existing credentials in /opt/ocana/openclaw/.gog/credentials.json instead.

CODEBLOCK9

Note: ~/.config/gws/credentials.json (gog default path) has a stale/broken token. Always use /opt/ocana/openclaw/.gog/credentials.json.

Verification Checklist

• - [ ] Owner shared calendar with agent email
• [ ] Permission is "Make changes to events" (not read-only)
• [ ] Agent ran gog auth add for owner's account
• [ ] gog auth list shows owner's account with calendar service
• [ ] Test event created successfully in owner's calendar
• [ ] Test event deleted after verification
• [ ] All calendar commands use INLINECODE12

Cost Tips

• - Cheap: This is a one-time setup — very low ongoing cost
• Small model OK: All steps are procedural — any model can follow them
• Avoid: Don't re-authenticate repeatedly — tokens last a long time if not revoked
• Batch: Add all needed services in one gog auth add call (gmail,calendar,drive,contacts) instead of separate calls

Email & Workspace Orientation (Merged from openclaw-email-orientation skill)

The Core Concept: Two Separate Accounts

These are separate. Having an agent email does NOT automatically give access to the owner's email or calendar. Owner must explicitly share, and agent must explicitly authenticate.

Key Files

Security: Never print the contents of these files in chat. Path is fine; content is not.

Using gog

CODEBLOCK10

Troubleshooting Email/Calendar Access

Work through in order:

1. 1. Two accounts? — Is the question about agent email or owner email?
2. gog installed? — which gog — if missing, check PATH
3. Account added? — gog auth list — does owner's account appear?
4. Write scope? — OAuth must include calendar write scope, not read-only
5. GOG_ACCOUNT set? — All commands must include INLINECODE21
6. Permission level? — Must be "Make changes to events", not "See all event details"

"Insufficient permissions" error → Owner re-shares calendar with write permission (Step 1 above).

"Token expired" error:
CODEBLOCK11