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-relay-migrate-from-flow - Skill

Name: nemo-relay-migrate-from-flow
Author: nvidia

Imported from nvidia/skills (skills/nemo-relay-migrate-from-flow/SKILL.md). Install upstream with npx skills add nvidia/skills --skill nemo-relay-migrate-from-flow. Copyright stays with the author (Apache-2.0).

Migrate From NeMo Flow To NeMo Relay

Use this skill when a user has existing NeMo Flow code or documentation and wants it converted to NeMo Relay. Treat the migration as a mechanical rename plus language-specific validation, not a behavior rewrite. Keep compatibility exceptions explicit before applying broad renames.

Default Workflow

Inspect the working tree and identify touched surfaces: Rust, Python, Node.js, Go, C FFI, CLI/config, docs, or integrations.
Resolve SKILL_DIR to the absolute directory containing this SKILL.md and TARGET_PATH to the source repository or target project. Run the bundled helper in dry-run mode before editing: python3 "$SKILL_DIR/scripts/migrate_from_nemo_flow.py" "$TARGET_PATH" --rename-paths
Review the reported text edits, path renames, and legacy project configuration warnings with the user. Do not migrate project-local .nemo-flow/config.toml or .nemo-flow/plugins.toml into .nemo-relay. Move those settings manually to a supported user or explicit configuration path after review.
Obtain explicit confirmation for the resolved target root, then rerun with --write, --rename-paths, and --confirm-root "$TARGET_PATH".
Apply language-specific cleanup for package manager lockfiles, generated artifacts, and public API examples.
Search for remaining Flow names and verify the affected language surfaces.

Mechanical Rename Map

Brand and repository: NeMo Flow -> NeMo Relay, NeMo-Flow -> NeMo-Relay
Python: nemo-flow -> nemo-relay, nemo_flow -> nemo_relay, python/nemo_flow -> python/nemo_relay
Rust: nemo-flow -> nemo-relay, nemo-flow-adaptive -> nemo-relay-adaptive, nemo_flow:: -> nemo_relay::
Node.js: nemo-flow-node -> nemo-relay-node, including related entry points such as /typed, /plugin, /adaptive, and /observability
Go: github.com/NVIDIA/NeMo-Flow/go/nemo_flow -> github.com/NVIDIA/NeMo-Relay/go/nemo_relay, package aliases nemo_flow -> nemo_relay, and source directories go/nemo_flow -> go/nemo_relay
C FFI: nemo_flow.h -> nemo_relay.h, nemo_flow_* -> nemo_relay_*, NemoFlow* -> NemoRelay*, and NEMO_FLOW_* -> NEMO_RELAY_*
CLI/config: nemo-flow -> nemo-relay, ~/.config/nemo-flow -> ~/.config/nemo-relay, NEMO_FLOW_* -> NEMO_RELAY_*, and x-nemo-flow-* -> x-nemo-relay-*. Do not blindly rename project-local .nemo-flow/config.toml or .nemo-flow/plugins.toml into .nemo-relay; those files require manual migration to a supported user or explicit configuration path.

Do not replace bare flow, Flow, or FlowError. Those can be domain words or intentional compatibility names.

Language Cleanup

Python: update pyproject.toml, imports, type stubs, integration package paths, extras, and native module names. Regenerate or refresh lockfiles with the user's package workflow after source edits.
Rust: update Cargo.toml crate names, workspace dependencies, package references, and use nemo_relay::... imports. Let Cargo regenerate Cargo.lock when dependencies changed.
Node.js: update package.json, workspace names, package-lock entries, native addon artifact names, and imports from nemo-relay-node. Run the package manager to refresh locks.
Go: update go.mod, import paths, package declarations, aliases, and any local directory layout under go/nemo_relay.
C FFI: update header includes, exported symbol names, status and callback type names, macro constants, loader paths, and downstream bindings.
Docs and examples: update badges, package install commands, repository links, hosted docs URLs, CLI commands, config paths, and integration names.

Automation Helper

Use $SKILL_DIR/scripts/migrate_from_nemo_flow.py for first-pass edits. The helper:

runs as a dry run unless --write is passed
skips common vendor, build, cache, and generated directories
skips lockfiles unless --include-lockfiles is passed
skips symbolic links and credential-bearing dotenv files
detects project-local .nemo-flow/config.toml and .nemo-flow/plugins.toml, leaves them unchanged, and reports that they require manual migration to a supported user or explicit configuration path
requires the reviewed target root to be repeated with --confirm-root before writing, and refuses filesystem-root or home-directory writes
anchors writes and renames to verified directory handles without following symbolic links, and refuses write mode on platforms that cannot provide those guarantees
uses atomic no-replace path renames and exits nonzero when any requested mutation fails
can report or perform path renames with --rename-paths
rewrites only explicit NeMo Flow identifiers, package names, repository names, config paths, headers, environment variables, and FFI type prefixes

The helper does not classify arbitrary JSON, YAML, TOML, or INI files as secret. Review every configuration file in the dry-run report. If any reported file is unreviewed or credential-bearing, do not use --write on that root. Apply the reviewed changes manually and leave secret-bearing files untouched without reading or displaying their values.

Set shell-safe absolute paths before invoking the helper. Replace the example values with the resolved skill directory and either the source repository or the user's target project:

SKILL_DIR="/resolved/absolute/path/to/nemo-relay-migrate-from-flow"
TARGET_PATH="/resolved/absolute/path/to/target-project"

python3 "$SKILL_DIR/scripts/migrate_from_nemo_flow.py" "$TARGET_PATH" --rename-paths
python3 "$SKILL_DIR/scripts/migrate_from_nemo_flow.py" "$TARGET_PATH" \
  --write --rename-paths --confirm-root "$TARGET_PATH"

Use --include-lockfiles only when the user wants lockfiles edited directly; otherwise regenerate them with Cargo, uv/pip, npm, or Go tooling.

Verification

Search for remaining explicit Flow identifiers: rg -n "NeMo Flow|NeMo-Flow|nemo_flow|nemo-flow|NEMO_FLOW|NemoFlow|nemo_flow\\.h|nemo_flow_"
Run targeted tests for every affected language surface.
For Rust changes, run cargo test or the repository's Rust test recipe.
For Python changes, run the relevant import check and tests in the target environment.
For Node.js changes, run package install, type checks, and package tests.
For Go changes, run go test ./... from the updated module.
For docs-only migrations, build or link-check docs if the site navigation, install commands, or API references changed.

Related Skills

nemo-relay-get-started
nemo-relay-instrument-calls
nemo-relay-debug-runtime-integration

Install nemo-relay-migrate-from-flow 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-relay-migrate-from-flow", "kind": "skill", "name": "nemo-relay-migrate-from-flow", "description": "Use this skill when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces.", "publisher": "nvidia", "version": "1.0.0", "capabilities": { "domains": [ "coding", "marketing" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use this skill when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/nvidia/skills", "path": "skills/nemo-relay-migrate-from-flow/SKILL.md", "ref": "HEAD", "url": "https://github.com/nvidia/skills/blob/HEAD/skills/nemo-relay-migrate-from-flow/SKILL.md", "key": "nvidia/skills/skills/nemo-relay-migrate-from-flow/SKILL.md" }, "license": "Apache-2.0" }, "instructions": "# Migrate From NeMo Flow To NeMo Relay\n\nUse this skill when a user has existing NeMo Flow code or documentation and\nwants it converted to NeMo Relay. Treat the migration as a mechanical rename\nplus language-specific validation, not a behavior rewrite.\nKeep compatibility exceptions explicit before applying broad renames.\n\n## Default Workflow\n\n1. Inspect the working tree and identify touched surfaces: Rust, Python,\n Node.js, Go, C FFI, CLI/config, docs, or integrations.\n2. Resolve `SKILL_DIR` to the absolute directory containing this `SKILL.md` and\n `TARGET_PATH` to the source repository or target project. Run the bundled\n helper in dry-run mode before editing:\n `python3 \"$SKILL_DIR/scripts/migrate_from_nemo_flow.py\" \"$TARGET_PATH\" --rename-paths`\n3. Review the reported text edits, path renames, and legacy project\n configuration warnings with the user. Do not migrate project-local\n `.nemo-flow/config.toml` or `.nemo-flow/plugins.toml` into `.nemo-relay`.\n Move those settings manually to a supported user or explicit configuration\n path after review.\n4. Obtain explicit confirmation for the resolved target root, then rerun with\n `--write`, `--rename-paths`, and `--confirm-root \"$TARGET_PATH\"`.\n5. Apply language-specific cleanup for package manager lockfiles, generated\n artifacts, and public API examples.\n6. Search for remaining Flow names and verify the affected language surfaces.\n\n## Mechanical Rename Map\n\n- Brand and repository: `NeMo Flow` -> `NeMo Relay`,\n `NeMo-Flow` -> `NeMo-Relay`\n- Python: `nemo-flow` -> `nemo-relay`, `nemo_flow` -> `nemo_relay`,\n `python/nemo_flow` -> `python/nemo_relay`\n- Rust: `nemo-flow` -> `nemo-relay`, `nemo-flow-adaptive` ->\n `nemo-relay-adaptive`, `nemo_flow::` -> `nemo_relay::`\n- Node.js: `nemo-flow-node` -> `nemo-relay-node`, including related entry\n points such as `/typed`, `/plugin`, `/adaptive`, and `/observability`\n- Go: `github.com/NVIDIA/NeMo-Flow/go/nemo_flow` ->\n `github.com/NVIDIA/NeMo-Relay/go/nemo_relay`, package aliases\n `nemo_flow` -> `nemo_relay`, and source directories `go/nemo_flow` ->\n `go/nemo_relay`\n- C FFI: `nemo_flow.h` -> `nemo_relay.h`, `nemo_flow_*` ->\n `nemo_relay_*`, `NemoFlow*` -> `NemoRelay*`, and `NEMO_FLOW_*` ->\n `NEMO_RELAY_*`\n- CLI/config: `nemo-flow` -> `nemo-relay`,\n `~/.config/nemo-flow` -> `~/.config/nemo-relay`, `NEMO_FLOW_*` ->\n `NEMO_RELAY_*`, and `x-nemo-flow-*` -> `x-nemo-relay-*`. Do not blindly\n rename project-local `.nemo-flow/config.toml` or `.nemo-flow/plugins.toml`\n into `.nemo-relay`; those files require manual migration to a supported user\n or explicit configuration path.\n\nDo not replace bare `flow`, `Flow`, or `FlowError`. Those can be domain words\nor intentional compatibility names.\n\n## Language Cleanup\n\n- **Python**: update `pyproject.toml`, imports, type stubs, integration\n package paths, extras, and native module names. Regenerate or refresh lockfiles\n with the user's package workflow after source edits.\n- **Rust**: update `Cargo.toml` crate names, workspace dependencies, package\n references, and `use nemo_relay::...` imports. Let Cargo regenerate\n `Cargo.lock` when dependencies changed.\n- **Node.js**: update `package.json`, workspace names, package-lock entries,\n native addon artifact names, and imports from `nemo-relay-node`. Run the\n package manager to refresh locks.\n- **Go**: update `go.mod`, import paths, package declarations, aliases, and any\n local directory layout under `go/nemo_relay`.\n- **C FFI**: update header includes, exported symbol names, status and callback\n type names, macro constants, loader paths, and downstream bindings.\n- **Docs and examples**: update badges, package install commands, repository\n links, hosted docs URLs, CLI commands, config paths, and integration names.\n\n## Automation Helper\n\nUse `$SKILL_DIR/scripts/migrate_from_nemo_flow.py` for first-pass edits. The\nhelper:\n\n- runs as a dry run unless `--write` is passed\n- skips common vendor, build, cache, and generated directories\n- skips lockfiles unless `--include-lockfiles` is passed\n- skips symbolic links and credential-bearing dotenv files\n- detects project-local `.nemo-flow/config.toml` and `.nemo-flow/plugins.toml`,\n leaves them unchanged, and reports that they require manual migration to a\n supported user or explicit configuration path\n- requires the reviewed target root to be repeated with `--confirm-root` before\n writing, and refuses filesystem-root or home-directory writes\n- anchors writes and renames to verified directory handles without following\n symbolic links, and refuses write mode on platforms that cannot provide those\n guarantees\n- uses atomic no-replace path renames and exits nonzero when any requested\n mutation fails\n- can report or perform path renames with `--rename-paths`\n- rewrites only explicit NeMo Flow identifiers, package names, repository names,\n config paths, headers, environment variables, and FFI type prefixes\n\nThe helper does not classify arbitrary JSON, YAML, TOML, or INI files as secret.\nReview every configuration file in the dry-run report. If any reported file is\nunreviewed or credential-bearing, do not use `--write` on that root. Apply the\nreviewed changes manually and leave secret-bearing files untouched without\nreading or displaying their values.\n\nSet shell-safe absolute paths before invoking the helper. Replace the example\nvalues with the resolved skill directory and either the source repository or the\nuser's target project:\n\n```bash\nSKILL_DIR=\"/resolved/absolute/path/to/nemo-relay-migrate-from-flow\"\nTARGET_PATH=\"/resolved/absolute/path/to/target-project\"\n\npython3 \"$SKILL_DIR/scripts/migrate_from_nemo_flow.py\" \"$TARGET_PATH\" --rename-paths\npython3 \"$SKILL_DIR/scripts/migrate_from_nemo_flow.py\" \"$TARGET_PATH\" \\\n --write --rename-paths --confirm-root \"$TARGET_PATH\"\n```\n\nUse `--include-lockfiles` only when the user wants lockfiles edited directly;\notherwise regenerate them with Cargo, uv/pip, npm, or Go tooling.\n\n## Verification\n\n- Search for remaining explicit Flow identifiers:\n `rg -n \"NeMo Flow|NeMo-Flow|nemo_flow|nemo-flow|NEMO_FLOW|NemoFlow|nemo_flow\\\\.h|nemo_flow_\"`\n- Run targeted tests for every affected language surface.\n- For Rust changes, run `cargo test` or the repository's Rust test recipe.\n- For Python changes, run the relevant import check and tests in the target\n environment.\n- For Node.js changes, run package install, type checks, and package tests.\n- For Go changes, run `go test ./...` from the updated module.\n- For docs-only migrations, build or link-check docs if the site navigation,\n install commands, or API references changed.\n\n## Related Skills\n\n- `nemo-relay-get-started`\n- `nemo-relay-instrument-calls`\n- `nemo-relay-debug-runtime-integration`", "cost": { "context_tokens": 1685 } }

nemo-relay-migrate-from-flow

About

Migrate From NeMo Flow To NeMo Relay

Default Workflow

Mechanical Rename Map

Language Cleanup

Automation Helper

Verification

Related Skills

Install nemo-relay-migrate-from-flow 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

Use it

Manifest

Reviews