Agent skill · nvidia
nemo-fabric-integrate
Use this skill when integrating NVIDIA NeMo Fabric into a consumer application, service, evaluation harness, or platform through the typed Python SDK — translating the consumer's own application, job, or deployment config into an in-memory FabricConfig, choosing the single-invocation convenience API or an explicitly started runtime, validating with plan and doctor, and consuming normalized results, artifacts, and telemetry.
What it needs
About 10k tokens when loaded.
What this skill does
Integrate NVIDIA NeMo Fabric Through The Python SDK Use this skill when a consumer codebase — an application, service, evaluation harness, or platform — needs to run agent harnesses through NeMo Fabric's typed Python SDK. The consumer owns its own configuration object and translates it into an in-memory FabricConfig; NeMo Fabric owns adapter selection, the runtime lifecycle, and normalized results. Integration Boundary Use the public, in-memory contract. These rules keep a consumer integration supported and upgrade-safe: Import only from the public nemofabric package. Never import native or any adapter-internal module. Build configuration as a typed FabricConfig in memory and pass it directly to NeMo Fabric. Create every deployment or evaluation variant with ordinary Python functions and modelcopy(deep=True). A platform integration can serialize the typed config inside a private transient run specification when it crosses a process boundary; that transport is not a public authoring format. Let NeMo Fabric own harness control. Do not reimplement start, invoke, or stop logic, and do not manage adapter threads, sessions, or processes directly. Treat runtimeid, invocationid, and requestid as opaque correlation strings, not parsable or reusable state. Refer to config-mapping.md for how to translate a consumer config object into FabricConfig, and for the full list of mechanics that stay hidden behind this boundary. Install And Set Up The Environment The consumer or its execution environment owns installation; NeMo Fabric validates runtime assumptions but never installs harnesses or credentials at run time. NeMo Fabric supports Python 3.11 through 3.14. Use Python 3.11 through 3.13 for Hermes Agent; the Harbor integration requires Python 3.12 or later. Install the runtime with uv pip install nemo-fabric (add the harbor extra for the Harbor integration). Refer to the installation guide. Select the harness adapter through HarnessConfig.adapterid. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/nemo-fabric-integrate