Agent skill · NVIDIA
nemo-relay-migrate-from-flow
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.
What it needs
About 3k tokens when loaded.
What this skill does
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 1. Inspect the working tree and identify touched surfaces: Rust, Python, Node.js, Go, C FFI, CLI/config, docs, or integrations. 2. Resolve SKILLDIR to the absolute directory containing this SKILL.md and TARGETPATH to the source repository or target project. Run the bundled helper in dry-run mode before editing: python3 "$SKILLDIR/scripts/migratefromnemoflow.py" "$TARGETPATH" --rename-paths 3. 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. 4. Obtain explicit confirmation for the resolved target root, then rerun with --write, --rename-paths, and --confirm-root "$TARGETPATH". 5. Apply language-specific cleanup for package manager lockfiles, generated artifacts, and public API examples. 6. Search for remaining Flow names and verify the affected language surfaces. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/nemo-relay-migrate-from-flow