openclaw-email-orientation

Explain OpenClaw agent Gmail and Google Calendar access and permission troubleshooting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about openclaw-email-orientation

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

FAQPage Schema
How do I authenticate a Gmail account for an OpenClaw agent using gog CLI?

OpenClaw agents authenticate to Gmail by using gog CLI commands to add accounts and generate OAuth credentials at specific token paths. This establishes the agent profile needed to access the owner account.

What is the difference between owner and agent accounts in OpenClaw Google Calendar integration?

In OpenClaw Google Calendar integration, owner and agent accounts are separate identities requiring explicit calendar sharing and individual authentication. Agents must be granted write permissions by the owner to create or modify events.

Why does my OpenClaw agent fail to create Google Calendar events despite being authenticated?

Google Calendar event creation fails for an OpenClaw agent when the owner account has not explicitly shared the calendar with write permissions. You must verify write access by testing event creation after confirming the sharing settings.

How do I refresh OAuth tokens for gog CLI on a headless server?

To refresh OAuth tokens for gog CLI on a headless server, apply an API-based token refresh workaround that bypasses the standard interactive browser flow. This updates the stored token files without requiring manual GUI authentication.

What are the common troubleshooting steps for OpenClaw Gmail and Google Calendar access issues?

Common troubleshooting steps for OpenClaw Gmail and Google Calendar access include checking for missing gog installations, diagnosing expired OAuth tokens, and verifying correct calendar sharing permissions using an ordered diagnostic checklist.