Agent skill · nvidia
nemo-fabric-build-adapter
Build, migrate, review, and maintain third-party NVIDIA NeMo Fabric adapters against the public adapter contract. Use when creating adapter or target descriptors, mapping AgentConfig into an agent harness or custom-agent runtime, implementing start/invoke/stop, declaring schemas and capabilities, packaging discovery metadata, or assessing adapter conformance. Do not use for consumer applications that only call the NVIDIA NeMo Fabric SDK.
What it needs
About 6k tokens when loaded.
What this skill does
Build an NVIDIA NeMo Fabric Adapter Build against the published southbound contract. Keep the adapter thin: let NeMo Fabric own planning and consumer-facing behavior, and let the adapter own only target translation and lifecycle state. Read the Contract Read the current adapter contract before changing code. Start with the overview, choose an integration shape, then follow the numbered descriptor, configuration, execution, results, registration, and verification stages. Read the custom-agent page when the target loads application-defined agents or workflows. Read the optional native OpenAI streaming page only when the adapter claims that capability. Use the committed adapter-contract JSON Schemas or the schemas installed with the matching NeMo Fabric release for exact wire shapes. Do not reconstruct a schema from examples or copy field lists into adapter code. Establish the Boundary Establish the adapter boundary before defining its descriptor: 1. Identify the adapter implementation and its stable adapterid. 2. Choose a harness adapter, a shared framework adapter with registered targets, or a dedicated custom-agent adapter. 3. Reuse one shared adapter across custom agents when the framework provides stable loading and invocation semantics. Use a dedicated adapter when the agent itself is the only unambiguous execution boundary. 4. List the normalized fields the target can actually enforce. 5. Separate adapter-wide harness.settings, per-target workflow.settings, and typed extensions. 6. Keep installation, environment preparation, Relay orchestration, caller scheduling, and consumer result enrichment outside the adapter. If the requested behavior cannot be expressed by the current contract, surface the gap. Do not silently consume an unsupported northbound field or hide it in an unrelated extension. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/nemo-fabric-build-adapter