Use this skill when NeMo Relay is installed or imported but application-side runtime behavior is missing or incorrect, including load failures, inactive scopes, missing events, and plugin or adaptive wiring problems.
SkillScore77Maintained
Automatic
◆AI Engineer pack
Last verified 8/12/2026
What it changes
Passed 16 of 21 test cases with the skill, and 8 of 21 without it.
Without skill36%
With skill77%
Checks it passed that the model alone missed
Inspects active scope ancestry.
Checks global versus scope-local registration.
Verifies middleware names and priority values.
and 16 more in the full report
9 fixed8 passed either way5 still failing0 broke
Pass-rate lift
+41 pp
Tokens
-5%
Agent turns
0%
Response time
-43%
Model gemini-3.6-flashMeasured 8/12/2026v117 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
We enabled an adaptive tuning policy in NeMo Relay, but the runtime behavior remains completely identical to baseline execution. What four components must be verified?
What was checked, without and with the skill
Checked
Without skill
With skill
Confirms that instrumentation actually emits events.
Missed
Passed
Verifies that the adaptive component is explicitly enabled.
Passed
Passed
Checks that active policy rules allow the behavior.
Missed
Passed
Ensures the execution call path reaches the configured component.
Missed
Passed
case-15 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md73 linessingle file
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?
Common Failure Classes
Python native extension missing
Go dynamic library not on the loader path
Node native addon not built or not loading
Execute call outside a scope
Missing events because registration never happened
Concurrency causing the wrong scope stack to be active
Adaptive component never initialized or config validation ignored
Embedded Troubleshooting Matrix
Rust build failure: run the narrowest core build first, then expand to the
affected binding or workspace command.
Python import failure: rebuild the virtual environment and native
extension with uv sync, then run a small Python test or import check from
the same environment as the application.
Node.js addon failure: reinstall and rebuild the native addon from the
Node binding package before debugging application code.
Go loader failure: build the release FFI shared library and point both the
linker and runtime loader at the release output directory; use the macOS
dynamic-library path variable (DYLD_LIBRARY_PATH) on macOS.
Scope stack empty: the work is outside an active scope or crossed a thread,
task, goroutine, or worker boundary without the intended stack.
Work leaks across requests: separate requests are sharing one scope stack;