Nemo Relay Migrate From Flow
NVIDIAOfficialCreated by NVIDIA Corporation and Affiliates
- Skill
- Workflow
- Software development
- Apache-2.0
- Medium risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured workflow and automation helper for migrating existing NeMo Flow applications, documentation, and configurations to NeMo Relay. It focuses on mechanical renaming across multiple programming languages and surfaces, including Python, Rust, Node.js, Go, C FFI, and CLI configurations, while ensuring safe handling of project-specific settings and dependencies.
What it does
- Identifies and renames NeMo Flow identifiers to NeMo Relay across source code and documentation.
- Provides a dry-run mode to review all proposed file renames and text edits before application.
- Handles language-specific updates for package managers, imports, and build configurations.
- Flags legacy configuration files that require manual migration for user review.
- Verifies the migration through targeted search and language-specific test execution.
- Ensures safe file system operations by requiring explicit confirmation of the target root.
When to use it
- When upgrading an existing project from NeMo Flow to NeMo Relay.
- When updating documentation or examples to reflect the NeMo Relay branding and API structure.
- When migrating cross-language repositories that contain Python, Rust, Node.js, or Go code.
- When needing to update CLI configurations or environment variables from NeMo Flow to NeMo Relay.
Advantages
- Reduces manual effort for large-scale codebase renames.
- Provides a safe, review-first approach with dry-run capabilities.
- Supports a wide range of languages and integration surfaces.
- Prevents accidental modification of sensitive or project-local configuration files.
- Includes built-in verification steps to ensure code integrity post-migration.
Usage examples
- “I need to migrate my project at /home/user/my-app from NeMo Flow to NeMo Relay. How do I start?”
- The agent will guide you to set the SKILL_DIR and TARGET_PATH variables, then execute the migration script in dry-run mode to generate a report of all pending changes for your review.
- “I have reviewed the dry-run report for my migration. How do I apply the changes?”
- The agent will instruct you to run the migration script with the --write and --confirm-root flags to safely apply the renames and edits to your project files.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/nemo-relay-migrate-from-flow/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip nemo-relay-migrate-from-flow.zip -d .agents/skills
Documentation by NVIDIA Corporation and Affiliates
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_DIRto the absolute directory containing thisSKILL.mdandTARGET_PATHto 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-pathsReview the reported text edits, path renames, and legacy project configuration warnings with the user. Do not migrate project-local
.nemo-flow/config.tomlor.nemo-flow/plugins.tomlinto.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-RelayPython:
nemo-flow->nemo-relay,nemo_flow->nemo_relay,python/nemo_flow->python/nemo_relayRust:
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/observabilityGo:
github.com/NVIDIA/NeMo-Flow/go/nemo_flow->github.com/NVIDIA/NeMo-Relay/go/nemo_relay, package aliasesnemo_flow->nemo_relay, and source directoriesgo/nemo_flow->go/nemo_relayC FFI:
nemo_flow.h->nemo_relay.h,nemo_flow_*->nemo_relay_*,NemoFlow*->NemoRelay*, andNEMO_FLOW_*->NEMO_RELAY_*CLI/config:
nemo-flow->nemo-relay,~/.config/nemo-flow->~/.config/nemo-relay,NEMO_FLOW_*->NEMO_RELAY_*, andx-nemo-flow-*->x-nemo-relay-*. Do not blindly rename project-local.nemo-flow/config.tomlor.nemo-flow/plugins.tomlinto.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.tomlcrate names, workspace dependencies, package references, anduse nemo_relay::...imports. Let Cargo regenerateCargo.lockwhen dependencies changed.Node.js: update
package.json, workspace names, package-lock entries, native addon artifact names, and imports fromnemo-relay-node. Run the package manager to refresh locks.Go: update
go.mod, import paths, package declarations, aliases, and any local directory layout undergo/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
--writeis passedskips common vendor, build, cache, and generated directories
skips lockfiles unless
--include-lockfilesis passedskips symbolic links and credential-bearing dotenv files
detects project-local
.nemo-flow/config.tomland.nemo-flow/plugins.toml, leaves them unchanged, and reports that they require manual migration to a supported user or explicit configuration pathrequires the reviewed target root to be repeated with
--confirm-rootbefore writing, and refuses filesystem-root or home-directory writesanchors 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-pathsrewrites 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 testor 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-startednemo-relay-instrument-callsnemo-relay-debug-runtime-integration
Files
- ATTRIBUTION.mdAdded by AutoGineer969 B
- BENCHMARK.md4.7 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md6.9 KiB
- evals/evals.json7.6 KiB
- scripts/migrate_from_nemo_flow.pyScript23.5 KiB
- skill-card.md4.0 KiB
- skill.oms.sig4.7 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Python, Needs Node.js
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- NVIDIA Corporation and Affiliates
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/nemo-relay-migrate-from-flow · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA Corporation and Affiliates or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download nemo-relay-migrate-from-flow.zip