omni-proxies

Configure HTTP/HTTPS/SOCKS proxies with per-provider or global rules.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/DevMHOne/nextroute --skill omni-proxies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omni-proxies
Source: https://github.com/DevMHOne/nextroute/tree/main/skills/omni-proxies
Command: npx skills add https://github.com/DevMHOne/nextroute --skill omni-proxies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proxy management for upstream provider requests: configure HTTP/HTTPS/SOCKS proxies with per-provider or global rules, enabling reliable routing and minimal latency.

Core Features & Use Cases

  • Per-provider and global proxy rules to control which requests use which proxies.
  • Proxy rotation and connectivity testing to ensure availability and performance.
  • Lightweight authentication integration and easy openAPI-guided usage for upstream providers.

Quick Start

Configure a global proxy policy and test a sample provider connection to validate routing.

Frequently Asked Questions about omni-proxies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure HTTP and SOCKS proxies for upstream provider requests?

Configure HTTP, HTTPS, and SOCKS proxies for upstream provider requests using per-provider or global rules to control routing, ensure reliable connectivity, and minimize latency.

What is the best way to route specific upstream providers through dedicated proxies?

Routing specific upstream providers through dedicated proxies is achieved by setting per-provider rules, allowing granular control over which requests use specific proxy configurations across multiple scenarios.

Can I test proxy connectivity and rotate proxies across multiple providers?

Yes, proxy connectivity testing and proxy rotation are supported natively, allowing you to verify availability and maintain performance across multiple upstream providers and scenarios.

Do I need a Bearer token or session cookie to manage proxy configurations?

A valid Bearer token or session cookie is required to authenticate and manage proxy configurations, with detailed request and response schemas available in the API specification.

Why use global proxy rules instead of per-provider configurations for upstream routing?

Global proxy rules apply a single routing policy across all upstream providers for simplified management, while per-provider configurations offer granular control for specific routing and latency requirements.

When should I not use a centralized proxy configuration for upstream providers?

Avoid centralized proxy configuration when upstream providers require isolated, locally managed network routing without global policy enforcement, or when custom proxy rotation testing is unsupported by your API spec.