NeMo Relay Migration Assistant
Safely migrate NeMo Flow projects to NeMo Relay.
The skill requires a dry run, review of proposed changes, and explicit confirmation of the resolved target root. The helper constrains the root, refuses writes to the filesystem root or home directory, avoids symlink traversal, skips dotenv files and common generated directories, and uses atomic replacement plus no-replace renames. No malware, credential theft, or covert exfiltration is shown. Points are deducted because there is no rollback, backup, or transaction-level recovery mechanism, configuration review responsibility remains largely with the user, and repository license metadata is NOASSERTION despite Apache-2.0 declarations in the skill and repository.
The SKILL.md, helper script, and evaluation tasks are consistent on the core workflow, including dry-run, root confirmation, nonzero failure handling, and change-detection checks. Points are deducted because no committed tests cover the key paths, static review cannot establish that platform-specific secure syscalls, language cleanup, and lockfile handling work in practice, and several cleanup steps depend on the user's toolchain.
The audience, migration scenarios, supported language surfaces, and exclusions for bare flow/Flow/FlowError are clearly described, and the skill does not depend on external APIs or overseas online services. Points are deducted because non-fit scenarios, input/output contracts, and negative trigger conditions are incomplete, and the documentation provides limited direct support for Chinese-language users.
The material is layered into workflow, rename mappings, language cleanup, automation, verification, and related skills. Apache-2.0 is declared by the skill; the skill card supplies ownership, version, evaluation summary, and risk notes, while repository files provide licensing and security contacts. Points are deducted because the benchmark identifies missing recommended Instructions and Examples sections, and there is no clear changelog, stable release policy, or skill-specific maintenance/update path; license metadata is also NOASSERTION.
The skill can directly guide a mechanical NeMo Flow to NeMo Relay rename across multiple languages, CLI, configuration, documentation, and FFI, with callable dry-run and write commands. The supplied evaluation report indicates useful results on positive tasks, but provides no independently reviewable migrated artifacts or outputs. Points are deducted because mechanical renaming does not establish behavioral, dependency, or API compatibility, while language cleanup and lockfile updates still require user tooling and follow-up validation.
The source includes an explicit replacement map, implemented helper, verification commands, evaluation tasks, and reported metrics, providing meaningful audit clues. Points are deducted because the evaluation claims are report-level evidence without committed tests covering key paths or independently reproducible CI evidence; execution cannot be verified from a static read.
- Write mode modifies multiple source files and paths in the target project; manually review the dry run, especially configuration files, and do not write when any file is unreviewed or credential-bearing.
- The helper performs explicit identifier replacement only; it does not establish actual NeMo Relay API, dependency, ABI, build, or runtime compatibility. Use a recoverable branch or copy and run language-specific tests.
- No explicit rollback procedure is provided; failures during path renames or file replacement may leave a partially completed migration.
- The reported evaluation results and version information are not independently reproduced by a committed test suite or CI covering the key paths.
What does this skill do, and when should you use it?
This skill migrates applications, examples, integrations, documentation, manifests, and repository code from NeMo Flow to NeMo Relay. It covers Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces. The workflow treats migration as a mechanical rename followed by language-specific cleanup and validation, not a behavior rewrite. The skill declares the Apache-2.0 license.
It inspects the working tree, identifies affected language and file surfaces, resolves the skill and target paths, and runs a Python migration helper in dry-run mode to report text edits and path renames. After the user confirms the target root, it performs the requested writes and renames. It then guides updates to dependencies, imports, package paths, headers, configuration, and documentation, followed by searches for remaining Flow identifiers and targeted tests.
- Migrating a NeMo Flow Python project whose package names, imports, or native module names must become NeMo Relay.
- Updating a repository with Rust crates, Cargo configuration, and workspace dependencies during the rename.
- Handling a cross-language repository containing Node.js packages, Go modules, or C FFI headers and symbols.
- Refreshing CLI commands, environment variables, configuration directories, documentation examples, and integration links without changing generic flow terminology.
- Applying reviewed, controlled bulk edits where a dry-run report and explicit target-root confirmation are required.
What are this skill's strengths and limitations?
- Covers Python, Rust, Node.js, Go, C FFI, CLI, configuration, documentation, and integrations.
- Uses a dry run by default and requires target-root confirmation before writing.
- Explicitly separates compatibility exceptions and avoids replacing bare flow, Flow, or FlowError terms.
- The helper skips common build, cache, vendor, and generated directories, symbolic links, and credential-bearing dotenv files.
- It focuses on naming and path migration, not behavioral rewrites or proof of functional equivalence.
- Lockfiles are skipped by default and generally need regeneration through Cargo, uv/pip, npm, or Go tooling.
- Configuration files are not automatically classified as secrets, so every reported configuration file requires review.
- The SKILL.md provides no concrete target-project matrix or universal test suite; validation depends on the target repository.
- The repository metadata lists the license as NOASSERTION, while the skill declares Apache-2.0 and the collection README declares Apache-2.0 plus CC BY-4.0.
How do you install this skill?
Install the skill with the skills CLI flow documented in the repository README:
npx skills add nvidia/skills --skill nemo-relay-migrate-from-flow --yes
The README does not specify a fixed installation directory; the CLI prompts for the skill and installation target.
How do you use this skill?
Ask a compatible agent for a migration, for example: “Migrate this project from NeMo Flow to NeMo Relay, starting with a dry-run report.” The agent should first run:
python3 "$SKILL_DIR/scripts/migrate_from_nemo_flow.py" "$TARGET_PATH" --rename-paths
After reviewing the report and confirming the target root, it should run:
python3 "$SKILL_DIR/scripts/migrate_from_nemo_flow.py" "$TARGET_PATH" --write --rename-paths --confirm-root "$TARGET_PATH"
Then apply language-specific cleanup, search for remaining explicit Flow identifiers, and run targeted tests for affected surfaces. The exact test commands depend on the target repository; the skill does not provide one universal test suite.