Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Manages Google AI Pro/Ultra access for OpenClaw agents by detecting restrictions and applying proxy or session rotation strategies. Handles rate limiting, IP blocks, auth failures, and geo-restrictions automatically. Provides a CLI for manual inspection and configuration.
Centralizes restriction detection and mitigation in one place instead of requiring manual intervention each time Google AI access fails in an automated workflow.
When to use it
- Rotating sessions when Google AI returns 429 rate limit errors
- Switching proxies after an IP-based block is detected
- Refreshing expired authentication tokens mid-workflow
- Testing proxy pool health before running a long agent job
- Diagnosing why a specific OpenClaw workflow lost Google AI access
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Google AI is returning 403 errors in my OpenClaw agent, how do I fix it?
- 1Run `node scripts/main.js detect` to analyze HTTP response patterns and identify the restriction type
- 2Check output: HTTP 403 maps to IP-based Block with critical severity and recommended action `switch_proxy`
- 3Run `node scripts/main.js proxy-health` to find a healthy proxy in the pool
- 4Run `node scripts/main.js proxy-add --host <new-proxy> --port 8080` if no healthy proxy is available
- 5Run `node scripts/main.js session-rotate` to create a fresh session through the new proxy
Agent resumes Google AI access using a rotated session routed through a healthy proxy, with the restriction event logged for diagnostics.
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.