New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Nemo Relay Migrate From Flow

by NVIDIA in NVIDIA/NeMo-Relay

A skill your agent uses 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…

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Nemo Relay Migrate From Flow

skills CLI
$ npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-migrate-from-flow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-migrate-from-flow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nemo-relay-migrate-from-flow .claude/skills/nemo-relay-migrate-from-flow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nemo-relay-migrate-from-flow
GitHub stars
192
Token cost
~1.8k tokens
SKILL.md length
753 words
Files
6 (incl. scripts)
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses 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…

  • Works in 6 steps: Inspect the working tree and identify… → Resolve SKILL_DIR to the absolute… → Review the reported text edits, path… → …
  • Migrating applications
  • SKILL.md covers Default Workflow, Mechanical Rename Map, Language Cleanup and Automation Helper, plus 2 more sections
  • Runs Python scripts from its folder; calls python3, rg and cargo

What it does

Nemo Relay Migrate From Flow is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts (for example `BENCHMARK.md`, `evals/evals.json` and `scripts/migrate_from_nemo_flow.py`).

It sits in DevOps & Cloud, covering Observability. It works with Python, Rust, Node.js and NVIDIA AI Platform. The repository describes itself as: Multi-language agent runtime and library for execution scope management, lifecycle events, and middleware on tool and LLM calls. The licence is Apache-2.0.

When your agent uses it

  • Migrating applications
  • Repository code from NeMo Flow to NeMo Relay across Python
  • Observability surfaces

Example prompts

  • “/nemo-relay-migrate-from-flow”

Requirements

  • Python 3
  • Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Inspect the working tree and identify touched surfaces: Rust, Python,
  2. Resolve SKILL_DIR to the absolute directory containing this SKILL.md and
  3. Review the reported text edits, path renames, and legacy project
  4. Obtain explicit confirmation for the resolved target root, then rerun with
  5. Apply language-specific cleanup for package manager lockfiles, generated
  6. Search for remaining Flow names and verify the affected language surfaces.

What it can do on your machine

Read from SKILL.md and the folder at commit 16d73b4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • rg
    • cargo
    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nemo Relay Migrate From Flow loads about 1.8k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 753 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from NVIDIA/NeMo-Relay at commit 16d73b4, republished under its Apache-2.0 licence (© NVIDIA). 753 words, ~1,776 tokens.

Download SKILL.mdSave it as .claude/skills/nemo-relay-migrate-from-flow/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
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.
license
Apache-2.0
metadata.author
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

  1. Inspect the working tree and identify touched surfaces: Rust, Python, Node.js, Go, C FFI, CLI/config, docs, or integrations.
  2. 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
  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 "$TARGET_PATH".
  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.

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.
Show full SKILL.md (331 more words)Show less

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:

bash
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.
  • nemo-relay-get-started
  • nemo-relay-instrument-calls
  • nemo-relay-debug-runtime-integration

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts) in skills/nemo-relay-migrate-from-flow of NVIDIA/NeMo-Relay.

  • SKILL.md
  • BENCHMARK.md
  • evals/evals.json
  • scripts/migrate_from_nemo_flow.py
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 16d73b4

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in NVIDIA/NeMo-Relay, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Nemo Relay Migrate From Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nemo Relay Migrate From Flow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemo Relay Migrate From Flow this skillNVIDIA/NeMo-Relay192—~1.8kAutomated safety check: PassApache-2.0
Debugging Techniquesancoleman/ai-design-components526—~3.3kAutomated safety check: PassMIT
CI Pipeline Synthesizerkajisho5/ffmpeg-skill1.9k1 repos~1.1kAutomated safety check: PassMIT
Logfire Instrumentationbasicmachines-co/basic-memory4.1k—~2.3kAutomated safety check: PassAGPL-3.0
Examples Checkereclipse-ankaios/ankaios125—~2kAutomated safety check: PassApache-2.0
Deploy To Tempsgotempsh/temps826—~1.3kAutomated safety check: NotesApache-2.0

Similar skills

  • Debugging Techniques

    ancoleman/ai-design-components

    Debugging workflows for Python (pdb, debugpy), Go (delve), Rust (lldb), and Node.js, including container debugging (kubectl debug, ephemeral containers) and production-safe debugging techniques with…

    526 GitHub stars~3.3k tokensUpdated 10 mo ago
    DevelopmentAuto-check passed

  • CI Pipeline Synthesizer

    kajisho5/ffmpeg-skill

    Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects.

    1.9k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check passed

  • Logfire Instrumentation

    basicmachines-co/basic-memory

    Adds Pydantic Logfire tracing, logging and metrics to Python, JavaScript or TypeScript and Rust projects, with the correct setup order and library extras.

    4.1k GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Examples Checker

    eclipse-ankaios/ankaios

    Check Ankaios examples by building and running each example in the devcontainer and validating they work correctly.

    125 GitHub stars~2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Deploy To Temps

    gotempsh/temps

    Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration.

    826 GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Writing Dockerfiles

    ancoleman/ai-design-components

    Writing optimized, secure, multi-stage Dockerfiles with language-specific patterns (Python, Node.js, Go, Rust), BuildKit features, and distroless images.

    526 GitHub stars~3.2k tokensUpdated 10 mo ago
    DevOps & CloudAuto-check: notes

More from NVIDIA/NeMo-Relay

All 30 skills in this repo

  • Draft Release Notes

    NVIDIA/NeMo-Relay

    Official

    Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.

    192 GitHub stars~575 tokensUpdated today
    Auto-check passed

  • Add Middleware

    NVIDIA/NeMo-Relay

    Official

    Add a new NeMo Relay guardrail or intercept type, registration surface, or pipeline stage.

    192 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Contribute Docs

    NVIDIA/NeMo-Relay

    Official

    Author or edit NeMo Relay documentation or examples when repository-specific MDX, public API, integration, or release-history conventions matter.

    192 GitHub stars~710 tokensUpdated today
    Auto-check passed

  • Maintain CI

    NVIDIA/NeMo-Relay

    Official

    Change or review NeMo Relay GitHub Actions workflows where permissions, pinned actions, caching, reusable workflows, or release gates require repository-specific handling.

    192 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Nemo Relay Install

    NVIDIA/NeMo-Relay

    Official

    A skill your agent uses when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, or maintained framework integrations, or when explaining Hermes Agent's…

    192 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Nemo Relay Plugin Build

    NVIDIA/NeMo-Relay

    Official

    A skill your agent uses when building or packaging reusable NeMo Relay runtime behavior as an embedded configuration component or a manifest-backed rustdynamic native or worker gRPC plugin, with…

    192 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Nemo Relay Migrate From Flow

What does Nemo Relay Migrate From Flow do?

A skill your agent uses 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…. Nemo Relay Migrate From Flow is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization.js, Go, C FFI, CLI, configuration, and observability surfaces.

When should I use Nemo Relay Migrate From Flow?

Nemo Relay Migrate From Flow fits situations like: migrating applications; repository code from NeMo Flow to NeMo Relay across Python; observability surfaces.

How do I install Nemo Relay Migrate From Flow in Claude Code?

Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-migrate-from-flow -a claude-code`. Or copy the skill folder (skills/nemo-relay-migrate-from-flow in NVIDIA/NeMo-Relay) into .claude/skills/nemo-relay-migrate-from-flow in your project. Claude Code loads it when a task matches its description.

How do I install Nemo Relay Migrate From Flow in Codex?

Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-migrate-from-flow -a codex`. Or copy the skill folder (skills/nemo-relay-migrate-from-flow in NVIDIA/NeMo-Relay) into .agents/skills/nemo-relay-migrate-from-flow in your project. Codex loads it when a task matches its description.

Can I use Nemo Relay Migrate From Flow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-migrate-from-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nemo-relay-migrate-from-flow, .gemini/skills/nemo-relay-migrate-from-flow, .github/skills/nemo-relay-migrate-from-flow and .opencode/skills/nemo-relay-migrate-from-flow in your project.

What does Nemo Relay Migrate From Flow need to run?

Going by SKILL.md and its folder, Nemo Relay Migrate From Flow needs Python for the scripts in its folder and the command-line tools its instructions call (python3, rg, cargo and go). Our summary lists: Python 3; Node.js.

Does Nemo Relay Migrate From Flow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nemo Relay Migrate From Flow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Nemo Relay Migrate From Flow use?

Nemo Relay Migrate From Flow is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nemo Relay Migrate From Flow use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nemo Relay Migrate From Flow?

Skills that share tags, products or a category with Nemo Relay Migrate From Flow: Debugging Techniques (ancoleman/ai-design-components, 526 stars), CI Pipeline Synthesizer (kajisho5/ffmpeg-skill, 1.9k stars), Logfire Instrumentation (basicmachines-co/basic-memory, 4.1k stars) and Examples Checker (eclipse-ankaios/ankaios, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemo Relay Migrate From Flow?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NeMo-Relay, which has 192 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 8, 2026.

Source: NVIDIA/NeMo-Relay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.