Skill Detail

Expose CLI agent accounts through an API-compatible local proxy with CLIProxyAPI

Run CLIProxyAPI when an operator needs a local OpenAI, Gemini, Claude, Codex, or Grok-compatible API facade over authenticated CLI agent access for repeatable agent and tool integrations.

Integrations & ConnectorsMulti-Framework
Integrations & Connectors Multi-Framework Published
⭐ 38.3k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill expose-cli-agent-accounts-through-api-compatible-local-proxy-with-cliproxyapi Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
CLIProxyAPI binary or source build; supported local CLI/OAuth credentials for the providers being proxied; compatible OpenAI/Gemini/Claude/Codex client
Install & setup
Follow the upstream getting-started guide at https://help.router-for.me/ or install from the latest GitHub release at https://github.com/router-for-me/CLIProxyAPI/releases, then configure only the provider accounts and local endpoints needed for the operator workflow.
Author
router-for-me
Publisher
Open Source
Last updated
Jun 24, 2026
Quick brief

CLIProxyAPI provides a local proxy server that presents OpenAI-, Gemini-, Claude-, Codex-, and Grok-compatible API endpoints backed by CLI model access. Use it for internal automation where existing CLI-agent authentication needs to be consumed by tools, SDKs, or services that expect an API-compatible endpoint.

How it works

What this skill actually does

The repeatable workflow is: install or run CLIProxyAPI, complete the supported local CLI authentication flows, configure provider accounts and routing, point compatible clients at the local endpoint, then monitor account health, model routing, streaming behavior, tool calls, and usage with the documented management APIs or companion dashboards.

Invoke this instead of using the CLI product normally when the workflow needs a programmatic local API bridge, multi-account routing, or one compatibility layer for several agent clients. The scope boundary is the local proxy and account-routing operation. It is not a model marketplace, hosted relay recommendation, generic SDK listing, or permission to bypass provider policies; operators remain responsible for compliant account and credential handling.