openclaw-email-orientation

What problem does it solve?

This Skill removes confusion about how OpenClaw agents interact with Gmail and Google Calendar by explaining the difference between owner and agent accounts, where credentials and tokens live, and how to authenticate and verify access so operators can diagnose and fix permission or token issues quickly.

Core Features & Use Cases

• Account distinction: Clear guidance on owner vs agent accounts and why separate identities require explicit sharing and authentication.
• gog CLI workflows: Step-by-step commands and checks to add accounts, list auth profiles, run Gmail searches, and create or list calendar events.
• Troubleshooting & headless workarounds: Ordered checklist for common failures (missing gog, expired tokens, wrong calendar permissions) and an API-based token refresh approach for headless servers.
• Use case: Onboard an OpenClaw agent to read and create calendar events for an owner account and verify write access after sharing.

Quick Start

Ask the agent to explain owner versus agent accounts, show the gog commands to authenticate the owner account, and provide the exact steps to test and confirm calendar write access.