Agent skill

OmniRoute Provider Management

by diegosouzapw in diegosouzapw/OmniRoute

Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.

MITAuto-check passedBackend & APIs

Install OmniRoute Provider Management

skills CLI
$ npx skills add diegosouzapw/OmniRoute --skill omni-providers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install diegosouzapw/OmniRoute omni-providers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omni-providers .claude/skills/omni-providers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
omni-providers
GitHub stars
74k
Token cost
~2.4k tokens
SKILL.md length
291 words
Files
2 (incl. references)
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.

  • Adding a new AI provider connection to OmniRoute
  • SKILL.md covers Overview, Authentication, Endpoints and Payloads, plus 1 more section
  • Calls curl; needs OMNIROUTE_TOKEN and REQUIRE_API_KEY
  • Testing whether a configured provider's API key still works

What it does

The skill documents a REST API for listing, adding, updating, removing and testing AI provider integrations in OmniRoute, an AI gateway that fronts many providers behind one endpoint. Every request needs a Bearer token or session cookie, obtained through a login endpoint, or the REQUIRE_API_KEY setting can be turned off for local development.

Endpoints cover standard CRUD on /api/providers and /api/provider-nodes, testing a single provider or a batch of providers, validating a provider or a provider-node configuration, listing a provider's available models, checking Cursor agent availability, and a set of agy-auth endpoints for importing credentials individually, in bulk, from a zip file, or applying them locally. A separate reference file documents each endpoint's request and response shape in detail.

When your agent uses it

  • Adding a new AI provider connection to OmniRoute
  • Testing whether a configured provider's API key still works
  • Listing the models available from a connected provider
  • Bulk-importing provider credentials into OmniRoute

Example prompts

  • “Add a new provider connection for this API key and test it.”
  • “List all the models available from our Anthropic provider connection.”
  • “Bulk-import these provider credentials from the zip file.”

Requirements

  • A running OmniRoute instance
  • A Bearer token or session cookie, or REQUIRE_API_KEY disabled for local use

What it can do on your machine

Read from SKILL.md and the folder at commit 4ea24a2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OMNIROUTE_TOKEN
    • REQUIRE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OmniRoute Provider Management loads about 2.4k tokens when it runs, and up to ~8.8k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 291 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from diegosouzapw/OmniRoute at commit 4ea24a2, republished under its MIT licence (© diegosouzapw). 291 words, ~2,416 tokens.

Download SKILL.mdSave it as .claude/skills/omni-providers/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
omni-providers
description
Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations across OmniRoute's 327-provider catalog.
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

Overview

Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations across OmniRoute's 327-provider catalog.

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

Payloads

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

<!-- skill:custom-start -->

Additional endpoints

POST /api/providers/{id}/refresh

Rotate / refresh OAuth tokens or re-validate credentials for a provider connection. Useful after token expiration or when credentials need to be renewed without deleting the connection.

bash
curl -X POST https://localhost:20128/api/providers/{id}/refresh \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
GET /api/provider-metrics

Retrieve aggregated usage and performance metrics for all provider connections (request counts, error rates, latency percentiles, token usage). Used by dashboards and Auto-Combo scoring.

bash
curl https://localhost:20128/api/provider-metrics \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

Response example:

json
{
  "providers": [
    {
      "id": "my-openai",
      "requestCount": 1240,
      "errorRate": 0.02,
      "p50LatencyMs": 340,
      "p99LatencyMs": 1200,
      "tokensIn": 500000,
      "tokensOut": 250000
    }
  ]
}
GET /api/providers/health-matrix

Returns a health-matrix view of all providers with per-connection status, circuit-breaker state, and cooldown expiry. Useful for debugging routing decisions.

bash
curl https://localhost:20128/api/providers/health-matrix \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
<!-- skill:custom-end -->

© diegosouzapw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/omni-providers of diegosouzapw/OmniRoute.

  • SKILL.md
  • references/endpoints.md

Open the folder on GitHubat commit 4ea24a2

Compare with similar skills

OmniRoute Provider Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

OmniRoute Provider Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
OmniRoute Provider Management this skilldiegosouzapw/OmniRoute74k—~2.4kAutomated safety check: PassMIT
Soundcloud API Integrationsoundcloud/api259—~787Automated safety check: PassNone
Frappe Core APIImpertio-Studio/Frappe_Claude_Skill_Package188—~3.2kAutomated safety check: PassMIT
Fwrest Client Generatortotvs/engpro-advpl-tlpp-skills143—~2.9kAutomated safety check: PassMIT
Twitterapi IokaitoInfra/twitterapi-io450—~3.1kAutomated safety check: PassMIT
Creating Integration DocsNangoHQ/nango13k—~2.7kAutomated safety check: PassCustom licence

Similar skills

  • Integrates applications with the SoundCloud HTTP API using OAuth 2.1, OpenAPI, and developer docs.

    259 GitHub stars~787 tokensUpdated 9 days ago
    Backend & APIsAuto-check passed
  • Frappe Core API

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when building ERPNext/Frappe API integrations (v14/v15/v16) including REST API, RPC API, authentication, webhooks, and rate limiting.

    188 GitHub stars~3.2k tokensUpdated 22 days ago
    Backend & APIsAuto-check passed
  • Fwrest Client Generator

    totvs/engpro-advpl-tlpp-skills

    Generate AdvPL/TLPP code that CONSUMES external REST APIs using the FWRest client class.

    143 GitHub stars~2.9k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Twitterapi Io

    kaitoInfra/twitterapi-io

    Official skill for twitterapi.io — query Twitter/X data (tweets, profiles, followers, advanced search, trends, spaces, communities, lists) and perform authenticated actions (post, reply, like…

    450 GitHub stars~3.1k tokensUpdated 4 mo ago
    Backend & APIsAuto-check passed
  • A skill your agent uses when adding or editing Nango integration documentation - creates and maintains integration pages, setup guides, connect guides, navigation, and provider metadata following…

    13k GitHub stars~2.7k tokensUpdated today
    Backend & APIsAuto-check passed
  • Discord Php Bot Security

    discord-php/DiscordPHP

    Audit checklist for DiscordPHP bots and API libraries — stop the bot token leaking to third-party APIs or logs, keep secrets out of customids and exception messages, use constant-time comparison and…

    1.1k GitHub stars~1.2k tokensUpdated 3 days ago
    Backend & APIsAuto-check: notes

More from diegosouzapw/OmniRoute

All 50 skills in this repo
  • OmniRoute Backup and Sync CLI

    diegosouzapw/OmniRoute

    Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.

    74k GitHub stars~948 tokensUpdated today
    Auto-check passed
  • Quality Scan

    diegosouzapw/OmniRoute

    Runs a scoped, read-only quality scan on a repository candidate and reports exact evidence, failures and frozen debt, without treating a static scan as release acceptance.

    74k GitHub stars~748 tokensUpdated today
    Auto-check passed
  • OmniRoute Settings API

    diegosouzapw/OmniRoute

    Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

    74k GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • OmniRoute Database Backups

    diegosouzapw/OmniRoute

    Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.

    74k GitHub stars~395 tokensUpdated today
    Auto-check passed
  • OmniRoute Batch CLI

    diegosouzapw/OmniRoute

    Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD…

    74k GitHub stars~565 tokensUpdated today
    Auto-check passed
  • OmniRoute Prompt Compression CLI

    diegosouzapw/OmniRoute

    Configure and test prompt compression from the CLI. Manage RTK filters, Caveman rules, stacked compression modes, and preview compression output with real…

    74k GitHub stars~521 tokensUpdated today
    Auto-check passed

Categories

Questions about OmniRoute Provider Management

What does OmniRoute Provider Management do?

Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog. The skill documents a REST API for listing, adding, updating, removing and testing AI provider integrations in OmniRoute, an AI gateway that fronts many providers behind one endpoint. Every request needs a Bearer token or session cookie, obtained through a login endpoint, or the REQUIRE_API_KEY setting can be turned off for local development.

When should I use OmniRoute Provider Management?

OmniRoute Provider Management fits situations like: adding a new AI provider connection to OmniRoute; testing whether a configured provider's API key still works; listing the models available from a connected provider; bulk-importing provider credentials into OmniRoute.

How do I install OmniRoute Provider Management in Claude Code?

Run `npx skills add diegosouzapw/OmniRoute --skill omni-providers -a claude-code`. Or copy the skill folder (skills/omni-providers in diegosouzapw/OmniRoute) into .claude/skills/omni-providers in your project. Claude Code loads it when a task matches its description.

How do I install OmniRoute Provider Management in Codex?

Run `npx skills add diegosouzapw/OmniRoute --skill omni-providers -a codex`. Or copy the skill folder (skills/omni-providers in diegosouzapw/OmniRoute) into .agents/skills/omni-providers in your project. Codex loads it when a task matches its description.

Can I use OmniRoute Provider Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add diegosouzapw/OmniRoute --skill omni-providers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omni-providers, .gemini/skills/omni-providers, .github/skills/omni-providers and .opencode/skills/omni-providers in your project.

What does OmniRoute Provider Management need to run?

Going by SKILL.md and its folder, OmniRoute Provider Management needs the command-line tools its instructions call (curl) and credentials named OMNIROUTE_TOKEN and REQUIRE_API_KEY. Our summary lists: A running OmniRoute instance; A Bearer token or session cookie, or REQUIRE_API_KEY disabled for local use.

Does OmniRoute Provider Management access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is OmniRoute Provider Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does OmniRoute Provider Management use?

OmniRoute Provider Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does OmniRoute Provider Management use?

About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.3k tokens, read only when the agent opens those files.

What are the alternatives to OmniRoute Provider Management?

Skills that share tags, products or a category with OmniRoute Provider Management: Soundcloud API Integration (soundcloud/api, 259 stars), Frappe Core API (Impertio-Studio/Frappe_Claude_Skill_Package, 188 stars), Fwrest Client Generator (totvs/engpro-advpl-tlpp-skills, 143 stars) and Twitterapi Io (kaitoInfra/twitterapi-io, 450 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OmniRoute Provider Management?

diegosouzapw (a GitHub user) maintains it in diegosouzapw/OmniRoute, which has 74,424 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 8, 2026.

Source: diegosouzapw/OmniRoute on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.