Skip to main content
Agent skill

Omni Proxies

Configure HTTP/HTTPS/SOCKS proxies for upstream provider requests. Set per-provider or global proxy rules, test connectivity, and manage proxy rotation.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Omni Proxies when an AI agent needs a reusable SKILL.md workflow for this job: Configure HTTP/HTTPS/SOCKS proxies for upstream provider requests. Set per-provider or global proxy rules, test connectivity, and manage proxy rotation.

When not to use it

Skip Omni Proxies when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/omni-proxies
# Save SKILL.md to ~/.claude/skills/omni-proxies/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/omni-proxies/SKILL.md. For a shared project, commit the folder at .claude/skills/omni-proxies/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Omni Proxies skill for this task: Use Omni Proxies when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
76/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

## Overview

Configure HTTP/HTTPS/SOCKS proxies for upstream provider requests. Set per-provider or global proxy rules, test connectivity, and manage proxy rotation.

## Authentication

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.

## Endpoints

### GET /api/settings/proxy

Get proxy settings

```bash curl http://localhost:20128/api/settings/proxy \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### PUT /api/settings/proxy

Update proxy settings

```bash curl -X PUT http://localhost:20128/api/settings/proxy \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### POST /api/settings/proxy/test

Test proxy connection

```bash curl -X POST http://localhost:20128/api/settings/proxy/test \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### GET /api/settings/proxies

GET settings › proxies

```bash curl http://localhost:20128/api/settings/proxies \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### POST /api/settings/proxies

POST settings › proxies

```bash curl -X POST http://localhost:20128/api/settings/proxies \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### PATCH /api/settings/proxies

PATCH settings › proxies

```bash curl -X PATCH http://localhost:20128/api/settings/proxies \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### DELETE /api/settings/proxies

DELETE settings › proxies

```bash curl -X DELETE http://localhost:20128/api/settings/proxies \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### POST /api/settings/proxies/{id}/repair-relay

POST settings › proxies › <id> › repair relay

```bash curl -X POST http://localhost:20128/api/settings/proxies/{id}/repair-relay \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### GET /api/settings/proxies/assignments

GET settings › proxies › assignments

```bash curl http://localhost:20128/api/settings/proxies/assignments \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### PUT /api/settings/proxies/assignments

PUT settings › proxies › assignments

```bash curl -X PUT http://localhost:20128/api/settings/proxies/assignments \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### POST /api/settings/proxies/auto-test

POST settings › proxies › auto test

```bash curl -X POST http://localhost:20128/api/settings/proxies/auto-test \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### POST /api/settings/proxies/batch-activate

POST settings › proxies › batch activate

```bash curl -X POST http://localhost:20128/api/settings/proxies/batch-activate \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### POST /api/settings/proxies/batch-delete

POST settings › proxies › batch delete

```bash curl -X POST http://localhost:20128/api/settings/proxies/batch-delete \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### PUT /api/settings/proxies/bulk-assign

PUT settings › proxies › bulk assign

```bash curl -X PUT http://localhost:20128/api/settings/proxies/bulk-assign \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### POST /api/settings/proxies/bulk-import

POST settings › proxies › bulk import

```bash curl -X POST http://localhost:20128/api/settings/proxies/bulk-import \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### GET /api/settings/proxies/egress

GET settings › proxies › egress

```bash curl http://localhost:20128/api/settings/proxies/egress \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### POST /api/settings/proxies/egress

POST settings › proxies › egress

```bash curl -X POST http://localhost:20128/api/settings/proxies/egress \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### GET /api/settings/proxies/health

GET settings › proxies › health

```bash curl http://localhost:20128/api/settings/proxies/health \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### POST /api/settings/proxies/migrate

POST settings › proxies › migrate

```bash curl -X POST http://localhost:20128/api/settings/proxies/migrate \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### GET /api/settings/proxies/pool

GET settings › proxies › pool

```bash curl http://localhost:20128/api/settings/proxies/pool \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### PUT /api/settings/proxies/pool

PUT settings › proxies › pool

```bash curl -X PUT http://localhost:20128/api/settings/proxies/pool \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### PATCH /api/settings/proxies/pool

PATCH settings › proxies › pool

```bash curl -X PATCH http://localhost:20128/api/settings/proxies/pool \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### DELETE /api/settings/proxies/pool

DELETE settings › proxies › pool

```bash curl -X DELETE http://localhost:20128/api/settings/proxies/pool \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### GET /api/settings/proxies/pool/egress-observation

GET settings › proxies › pool › egress observation

Read-only observation of how many distinct egress IPs actually served the members of a proxy pool over the last 24 h, read from the proxy log (numbers only, never used for routing). Opt-in through the PROXY_POOL_EGRESS_OBSERVATION feature flag: while it is off, or when the read fails, the body is JSON null. Results are cached for 30 seconds per normalized scope (key is read as account, global as the stored global pool).

```bash curl http://localhost:20128/api/settings/proxies/pool/egress-observation \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### POST /api/settings/proxy/cloudflare-deploy

POST settings › proxy › cloudflare deploy

```bash curl -X POST http://localhost:20128/api/settings/proxy/cloudflare-deploy \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### POST /api/settings/proxy/deno-deploy

POST settings › proxy › deno deploy

```bash curl -X POST http://localhost:20128/api/settings/proxy/deno-deploy \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### POST /api/settings/proxy/vercel-deploy

POST settings › proxy › vercel deploy

```bash curl -X POST http://localhost:20128/api/settings/proxy/vercel-deploy \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

## Payloads

See the full OpenAPI specification at `GET /api/openapi/spec` or `docs/openapi.yaml` for detailed request/response schemas.

Intended uses

  • Use Omni Proxies when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.