Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Coding
maverick-gog
Try itInternal setup hook that provisions gogcli with Google OAuth credentials supplied by an external orchestrator over the OpenClaw `skills.setup` RPC. Not user-facing — for Google Workspace command usage, see the upstream `gog` skill which loads alongside this one.
What it does
Internal setup hook for the CLI (). Provisions gogcli's OAuth state from env vars supplied by an external orchestrator over the OpenClaw RPC. After setup completes, agents use Google Workspace via the upstream skill — this skill provides no agent-facing commands.
The skill document
maverick-gog
Internal setup hook for the gog CLI (openclaw/gogcli). Provisions gogcli's OAuth state from env vars supplied by an external orchestrator over the OpenClaw skills.setup RPC. After setup completes, agents use Google Workspace via the upstream gog skill — this skill provides no agent-facing commands.
Provides
- A
setup.shhook the deployment harness invokes on credential install / rotation. Reads OAuth credentials from env (delivered ephemerally per call) and hands them togog auth credentials set+gog auth import— gogcli owns where the values are persisted. - Multi-account support — each
(client, account)pair is provisioned independently; multiple Google accounts can coexist on one instance.
Does not provide
- Agent-callable commands or tool surface. For Workspace usage (
gog gmail ...,gog calendar ..., etc.) see the upstreamgogskill, which loads alongside this one. - Interactive auth (
gog auth add --manual). Setup is fully non-interactive — credentials come from the orchestrator.
Authentication
Credentials are setup-time only. Once seeded, gogcli handles refresh-token rotation autonomously; agent calls never need to refresh credentials directly. The only unrecoverable failure is user-side grant revocation (e.g. user removes the integration in Google's account settings), which surfaces as auth errors on the next API call.
Multi-account
The setup hook does not mark any provisioned account as the default. When more than one account is connected for the same client, gog ... calls must disambiguate — either via the GOG_ACCOUNT= env var (upstream's documented convention; see the Notes section of the upstream gog skill) or the --account= flag. With a single account connected, gogcli resolves it implicitly and the upstream skill's no---account command examples work unchanged.
Related skills
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.
Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.
More from maverick
Browse all skillsSearch and update HubSpot CRM records and activities
Work with Confluence workspace content through Atlassian Rovo's hosted MCP server. Thin pass-through to Atlassian's official MCP; the live tool catalog is whatever that server advertises. Use when the user asks about Confluence pages, spaces, docs, comments, or knowledge-base updates.
Read and update Linear issues, projects, and cycles
Work with WordPress posts, pages, media, and comments
Work with Jira issue tracking and project workflow state through Atlassian Rovo's hosted MCP server. Thin pass-through to Atlassian's official MCP; the live tool catalog is whatever that server advertises. Use when the user asks about Jira work tracking or workflow updates.
Read and manage Canva designs, assets, exports, and templates