How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

nemo-rl-docs - Skill - OpenSmartRoute

Name: nemo-rl-docs
Author: nvidia

Imported from nvidia/skills (skills/nemo-rl-docs/SKILL.md) via skills.sh. Install upstream with npx skills add nvidia/skills --skill nemo-rl-docs. Copyright stays with the author (Apache-2.0).

Documentation Conventions

Keep docs/index.md Up to Date

When a new markdown doc is added under docs/**/*.md or a markdown file is renamed, ensure that @docs/index.md is updated and the document appears in the most appropriate section.

Docstring Format

Use Google style docstrings for classes and functions. These are parseable by Sphinx.

For interfaces that may be used outside a file, prefer docstrings over comments. Comments should be reserved for code within a function or interfaces local to a file.

Document New Features

When a new feature is added, update or create documentation in the docs/ directory that most closely matches the feature. Look at existing docs to find the best fit — if none exists, create a new doc and add it to @docs/index.md.

Documentation changes are not required for bug fixes or CI-related changes.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install nemo-rl-docs and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "nvidia-skills-nemo-rl-docs", "kind": "skill", "name": "nemo-rl-docs", "description": "Documentation conventions for NeMo-RL. Covers docs/index.md updates and docstring format. Do NOT use for: bug fixes, test fixes, dependency bumps, refactoring, CI/CD changes, performance tuning, or any task that does not involve writing or updating documentation.", "publisher": "nvidia", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Documentation conventions for NeMo-RL. Covers docs/index.md updates and docstring format. Do NOT use for: bug fixes, test fixes, dependency bumps, refactoring, CI/CD changes, performance tuning, or any task that does not involve writing or updating documentation." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/nvidia/skills", "path": "skills/nemo-rl-docs/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/nvidia/skills/nemo-rl-docs", "key": "nvidia/skills/skills/nemo-rl-docs/SKILL.md" }, "license": "Apache-2.0" }, "instructions": "# Documentation Conventions\n\n## Keep docs/index.md Up to Date\n\nWhen a new markdown doc is added under `docs/**/*.md` or a markdown file is renamed, ensure that @docs/index.md is updated and the document appears in the most appropriate section.\n\n## Docstring Format\n\nUse [Google style](https://google.github.io/styleguide/pyguide.html) docstrings for classes and functions. These are parseable by Sphinx.\n\nFor interfaces that may be used outside a file, prefer docstrings over comments. Comments should be reserved for code within a function or interfaces local to a file.\n\n## Document New Features\n\nWhen a new feature is added, update or create documentation in the `docs/` directory that most closely matches the feature. Look at existing docs to find the best fit — if none exists, create a new doc and add it to @docs/index.md.\n\nDocumentation changes are **not required** for bug fixes or CI-related changes.", "cost": { "context_tokens": 227 } }

nemo-rl-docs

About

Documentation Conventions

Keep docs/index.md Up to Date

Docstring Format

Document New Features

Use it

Install nemo-rl-docs and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews