cliproxy-openclaw
Deploy and configure CLIProxyAPI, expose its dashboard safely, connect OAuth providers like Claude Code, Gemini, Codex, Qwen, and iFlow, generate a reusable API endpoint and API key, and integrate it with OpenClaw or other OpenAI-compatible tools. Use when the user wants one API layer from subscription-based CLI or OAuth accounts, multi-account routing, or CLIProxy setup on a VPS or local machine.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/ayder21/cliproxy-openclawWhat This Skill Does
The cliproxy-openclaw skill serves as a robust bridge between local infrastructure and cloud-based AI ecosystems. It automates the installation, configuration, and secure exposure of CLIProxyAPI, a powerful middleware tool designed to aggregate various CLI-based AI subscriptions into a unified, OpenAI-compatible API layer. By deploying this, you gain the ability to route traffic from multiple accounts—such as Claude Code, Gemini, Codex, Qwen, or iFlow—through a single, consistent endpoint. This eliminates the need for managing individual API keys across different client applications, as the skill handles the heavy lifting of service management, reverse proxy setup, and OAuth credential integration. Once deployed, the skill bridges the gap between your managed proxy and the OpenClaw environment, ensuring seamless model inference and standardized communication across all your authenticated AI providers.
Installation
To install this skill, run the following command in your terminal:
clawhub install openclaw/skills/skills/ayder21/cliproxy-openclaw
Ensure that you have Docker or a systemd-compatible environment ready, as the skill will attempt to provision a persistent service to ensure your API endpoint remains active. During the setup process, the skill will conduct an environment inspection to identify existing web servers like Nginx or Caddy to minimize conflicts while optimizing for local or remote connectivity.
Use Cases
- Multi-Account Routing: Consolidate different subscription-based CLI AI accounts into one unified interface for OpenClaw.
- Remote Access: Securely expose your local CLIProxy dashboard to a private VPS or LAN for development consistency across devices.
- Workflow Automation: Programmatically access high-tier models via CLI tools that don't natively support OpenAI-compatible API schemas.
- Cost & Token Management: Simplify the lifecycle of OAuth-based tokens by centralizing them within a single, local, and auditable management surface.
Example Prompts
- "Setup CLIProxyAPI on my local machine and integrate my active Claude Code and Gemini subscriptions so I can use them in OpenClaw."
- "Deploy CLIProxy to my remote VPS, secure it with a reverse proxy, and provide me with the endpoint URL to use in my IDE."
- "I'm having trouble with my API key; can you check the CLIProxy logs and verify the connection status for my iFlow provider?"
Tips & Limitations
- Security First: Always ensure that when exposing your dashboard to a public network, you use a strong authentication mechanism or a restrictive firewall/VPN. This skill defaults to secure practices but requires user oversight.
- Performance: The responsiveness of your API endpoint depends on the latency of the underlying CLI-based provider; expect slight overhead compared to direct API calls.
- Troubleshooting: If you encounter 401 or 403 errors, verify your OAuth tokens via the dashboard before requesting a system re-configuration. Always run the included smoke test to validate connectivity after adding new providers.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-ayder21-cliproxy-openclaw": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, file-write, file-read, code-execution