Use this skill when choosing or configuring NeMo Relay 0.6 or 0.7 observability through the built-in plugin, subscribers, or exporters, including raw ATOF events, ATIF trajectories, OpenTelemetry, OpenInference, or custom event handling.
SkillScore91Maintained
Automatic
◆AI Engineer pack
Last verified 8/12/2026
What it changes
Passed 18 of 20 test cases with the skill, and 5 of 20 without it.
Without skill23%
With skill91%
Checks it passed that the model alone missed
The response states that a skill.load mark is emitted.
The response specifies OpenInferenceSubscriber for version 0.6.
The response uses AtofExporter for local raw lifecycle event export.
and 20 more in the full report
15 fixed5 passed either way2 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+27%
Agent turns
0%
Response time
-60%
Model gemini-3.6-flashMeasured 8/12/2026v120 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
When an agent tool reads a complete SKILL.md file during execution in NeMo Relay, what mark name is emitted and what single field is included in the payload?
What was checked, without and with the skill
Checked
Without skill
With skill
The response states that a skill.load mark is emitted.
Missed
Passed
The response states that the skill.load payload contains only skill_name.
Missed
Passed
case-12 · 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.md133 lines5 files
Configure Observability Plugins
Start with one exporter managed by the built-in Observability plugin. This is
the default for reusable process configuration and the best first plugin for
most users because it makes Relay's captured activity visible.
Choose one proof output before layering additional telemetry destinations.
Use manual subscriber or exporter APIs only when a test, script, or application
needs direct control over registration names, collection windows, or flush
timing. Both paths consume the same canonical event stream.
Select The Relay Version
Determine whether the application uses NeMo Relay 0.6 or 0.7 before proposing
configuration or binding APIs. Prefer the installed package version, lockfile,
or manifest. Ask the user when the version cannot be established; do not mix
the two surfaces in one example.
0.6 uses observability configuration version 2. OpenTelemetry and
OpenInference are separate exporters with OpenTelemetryConfig /
OpenTelemetrySubscriber and OpenInferenceConfig /
OpenInferenceSubscriber.
0.7 uses observability configuration version 3. One typed OpenTelemetry
exporter provides full, gen_ai, and openinference projections.
Choose The Output
Select the output that best matches the user's immediate inspection target:
Console or custom event handling
Use a manual subscriber for short-lived in-process inspection.
Raw canonical lifecycle events
Use ATOF JSONL; read references/atof.md.
Portable execution trajectories
Use ATIF; read references/atif.md.
OTLP tracing
For 0.6, choose the separate OpenTelemetry or OpenInference exporter. For
0.7, choose a typed OpenTelemetry endpoint (full, gen_ai, or
openinference). Read references/opentelemetry.md and, for an
OpenInference-aware backend, references/openinference.md.