Debug Runtime Integration

Debug Runtime Integration is a Quality skill for Claude Code, published by NVIDIA in NeMo-Relay.

165 stars67 forkson NVIDIA/NeMo-RelayAdded 2026/09/08+23% in starsRepository updated 2026/09/07

agentsaiatifatofclaude-codecodexdeepagentshermes-agentlangchainlanggraphmiddlewarenvidiaobservabilityopenclawopeninferenceoptimizationotelruntimesecurity

Install in seconds

Install Debug Runtime Integration

Copy Debug Runtime Integration into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-debug-runtime-integration ~/.claude/skills/nemo-relay-debug-runtime-integration

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/NVIDIA/NeMo-Relay.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/nemo-relay-debug-runtime-integration/SKILL.md in NVIDIA/NeMo-Relay
Installs to: ~/.claude/skills/nemo-relay-debug-runtime-integration
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1897 skills

What Debug Runtime Integration does

Debug Runtime Integration helps identify why NeMo Relay loads but runtime behavior is missing or incorrect, including scope, event, plugin, and export wiring issues. Use it when integration works partially but the expected callbacks or telemetry do not appear.

Debug Runtime Integration is cataloged under Quality on DirSkills. Debug Runtime Integration comes from a repository tagged agents, ai, atif, atof and claude-code.

Documentation

README

Excerpt

Debug Runtime Integration

Use this skill when NeMo Relay is present in the application but something is not working. Start by proving which runtime layer is failing before changing configuration.

First Checks

Can the binding or native artifact load?
Is there an active scope when the failing call runs?
Is the work happening on the expected scope stack?
Is the subscriber/exporter/plugin configuration actually active?
Did the app choose the right public API layer: managed execute vs manual lifecycle vs typed wrappers vs adaptive/plugins?

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Debug Runtime Integration

What else does NVIDIA publish alongside Debug Runtime Integration?
Debug Runtime Integration is one of 25 skills that DirSkills catalogs from NVIDIA/NeMo-Relay, the repository it ships in. Its siblings there include Adaptive Tuning, Add Binding Feature and Add Middleware. Each one is a separate skill with its own page in this directory, installs the same way Debug Runtime Integration does, and is maintained by NVIDIA in that same repository. The rest of the collection is listed on the NVIDIA/NeMo-Relay page.
How does Debug Runtime Integration compare to other Quality skills?
Debug Runtime Integration ranks #1783 by stars among the 1897 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Debug Runtime Integration against them. Open each page to compare what they document and how they install.