Configure HTTP, HTTPS, and SOCKS proxies for requests to external providers. Manage shared or provider-specific rules, test connections, and control proxy rotation to define which intermediary servers handle outgoing requests.
Configure HTTP/HTTPS/SOCKS proxies for upstream provider requests. Set per-provider or global proxy rules, test connectivity, and manage proxy rotation.
omni-proxies covers proxy settings for requests sent to external providers. A proxy relays those requests through an intermediary server. The skill supports HTTP, HTTPS, and SOCKS proxies. It covers both shared rules that apply across providers and separate rules for individual providers. Connection testing and rotation, which switches between proxies in sequence, are also within its scope.
Use it when you want to configure communication routes to external services together, or choose a different proxy for a particular provider. It can also serve as reference material when asking an agent to check whether a proxy connects and configure how proxies are switched. These tasks cover both connection checks and the rules used to select proxies.
API requests require a valid Bearer token or session cookie. No concrete API endpoints for this area are listed yet. Detailed request and response formats are referenced through GET /api/openapi/spec or docs/openapi.yaml.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 22, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Configure HTTP/HTTPS/SOCKS proxies for upstream provider requests. Set per-provider or global proxy rules, test connectivity, and manage proxy rotation.
All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false for local development.
No endpoints mapped for this area yet.
See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use the command line to send tasks to OmniRoute's A2A server, which supports communication between agents. Inspect execution history and logs, monitor or cancel tasks, and interactively test the JSON-RPC 2.0 communication protocol.
Back up and restore OmniRoute data from the command line. Covers incremental snapshots, encryption, cloud synchronization, scheduled backups, and archive import and export, with options for retention and previewing an import.
Submit groups of AI requests as batch jobs with the OmniRoute command line. Manage input files, monitor or cancel jobs, save results and errors, and incorporate batch processing into automated build and deployment workflows.
Send prompts to LLMs from a terminal, display answers as they arrive, or hold an ongoing conversation. Use files or standard input for prompts, choose models, and set system instructions through OmniRoute.
Configure prompt compression, which shortens text sent to AI models, through the OmniRoute command line. Adjust RTK filters, Caveman rules, and combined compression modes, then preview the results using real prompts.
Manage OmniRoute context settings from the command line, including token budgets and RTK filters for processing context. Switch saved server connections, import or export configurations, and inspect or expire conversation sessions.