Most OpenClaw users connect their agent to Telegram or WhatsApp first — it is the obvious move, making the agent reachable from anywhere. The second connection that changes daily workflows is usually Google. Email, calendar, files, contacts, spreadsheets: the majority of working knowledge for most people lives in Google’s ecosystem. GOG — short for Google Workspace CLI — is the ClawHub skill that connects all of it, through a single OAuth setup, without requiring separate integrations for each service.
The unusual footnote: GOG was written by Peter Steinberger himself — steipete, the creator of OpenClaw. It is one of a small number of skills bearing his personal ClawHub account.
What GOG Covers
A single npx clawhub@latest install gog and one OAuth authorization gives your agent access to six Google services:
- Gmail — read, search, compose, reply, label, and archive messages
- Google Calendar — query events, create appointments, set reminders, check availability
- Google Drive — list, search, read, upload, and organize files
- Google Contacts — look up contact details, add entries, update records
- Google Sheets — read and write spreadsheet data, run queries across ranges
- Google Docs — read document content, append text, create new documents
The download count sits in the 14,000–146,000 range depending on counting methodology (ClawHub counts both direct installs and downstream dependencies). Either way, GOG is consistently among the top-performing skills in the productivity category — which makes sense given that Google Workspace is the default productivity stack for a significant portion of the knowledge workforce.
Why One OAuth Matters
Before GOG, connecting an OpenClaw agent to Google services required either stringing together separate skills for each product or managing multiple API credentials. The friction was enough that most users skipped it, relying instead on manually copying information into conversations when they needed their agent to act on something in their inbox or calendar.
GOG resolves this with a unified OAuth flow. You authenticate once via Google’s standard OAuth2 consent screen, the credential is stored locally (in line with OpenClaw’s local-first architecture), and from that point forward your agent can reference anything across all six services in a single conversation turn. Ask it to check your calendar before scheduling a follow-up email, pull a contract from Drive while drafting a reply in Gmail, or update a project tracker in Sheets based on something that just arrived in your inbox — all without re-authenticating or switching contexts.
Practical Workflows
The workflows that emerge from this kind of cross-service access tend to be the ones that feel tedious to do manually. A few examples that come up frequently in the OpenClaw community:
Morning digest. Ask the agent for a briefing: unread emails that need responses, calendar commitments for the day, any Drive files shared with you overnight. GOG pulls from all three in a single query and formats it however you prefer.
Meeting prep. Before a calendar event, the agent searches Gmail for relevant correspondence with the attendees, pulls any shared Drive documents linked in the invite, and surfaces a summary. This takes about thirty seconds of agent time and would take five to ten minutes manually.
Inbox triage. A natural language query like “show me emails from last week that need a response and haven’t been replied to” produces a filtered list. The agent can draft replies directly, using Contacts to fill in salutations correctly and Calendar to suggest times if scheduling is involved.
Spreadsheet updates from conversation. For anyone who maintains a log or tracker in Sheets — expense records, client lists, project status — the agent can append or update rows from a conversation without opening a browser. Combined with the ezBookkeeping skill, this enables a reasonably complete personal finance workflow that never requires touching a spreadsheet manually.
Setup
Installation is standard ClawHub:
npx clawhub@latest install gogAfter install, the skill walks you through a one-time OAuth authorization for your Google account. The credential is stored locally in your OpenClaw workspace — nothing is sent to ClawHub servers or any intermediary. If you run multiple Google accounts, GOG supports multiple credential profiles with a flag at install time.
The skill is available on ClawHub under steipete’s account. Given that it comes from the same person who architected OpenClaw’s core local-first principles, the implementation choices are consistent with that philosophy: credentials stay on your machine, queries run directly against Google’s APIs, and nothing persists in a third-party cloud.
The Bigger Picture
GOG is not the most technically complex skill in the registry. What it represents is the point at which an OpenClaw agent stops being a standalone assistant and becomes genuinely embedded in how you actually work. Most productivity tools live in Google Workspace; an agent that cannot reach them is fundamentally limited in what it can do without manual intervention. GOG removes that limitation in a single install.
For anyone who has set up OpenClaw and found themselves repeatedly copying email content or calendar details into the conversation manually, GOG is the obvious next install.
Leave a Reply