agentleFS
Sign inStart free
YangsonHungYangsonHung/awesome-agent-skills/skills/en/routerbase-api-integration/SKILL.md

routerbase-api-integration

Skill18 starsChanged 5 days agoMITView on GitHub

Use when integrating applications with an OpenAI-compatible model gateway, migrating SDK calls, or documenting safe API key handling for RouterBase.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks for:

    line 14
  2. Distinctive:

    Do not use this skill for:

    line 23
  3. Distinctive:

    Keep the existing OpenAI-compatible SDK when possible.

    line 31
  4. Very specific:

    Use placeholders such as <ROUTERBASE_API_KEY> in examples.

    line 32
  5. Distinctive:

    Keep credentials server-side and out of git.

    line 33
  6. Distinctive:

    Prefer a small test request before suggesting broad application changes.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

RouterBase API Integration

Overview

Integrate applications with routerbase as an OpenAI-compatible model gateway. This skill covers SDK migration, base URL configuration, streaming, tool calling, JSON mode, vision inputs, request validation, error handling, and safe credential handling.

When to Use

Use this skill when the user asks for:

  • Migrating OpenAI-compatible SDK calls to RouterBase
  • Setting base_url or baseURL to https://routerbase.com/v1
  • Configuring RouterBase API keys without exposing secrets
  • Implementing chat completions, streaming, tool calling, JSON mode, or vision inputs
  • Writing concise RouterBase integration examples for Python, JavaScript, curl, LangChain, LlamaIndex, Vercel AI SDK, Cursor, Continue, or similar clients

Do not use

Do not use this skill for:

  • Publishing, logging, or storing real API keys
  • Guessing provider-specific behavior that is not documented by the user or upstream docs
  • Rewriting a working provider integration when the user only needs model selection guidance

Instructions

  1. Identify the user's current client, language, model ID, and deployment environment.
  2. Keep the existing OpenAI-compatible SDK when possible; change only the base URL, model, and local secret configuration.
  3. Use placeholders such as <ROUTERBASE_API_KEY> in examples.
  4. Keep credentials server-side and out of git.
  5. Prefer a small test request before suggesting broad application changes.
  6. Include a verification checklist with expected status code, response shape, timeout handling, and redaction requirements.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free