Motel Debug
kitlangton/motel
Debug applications with motel, a local OpenTelemetry ingest and query server.
Change NeMo Relay event fields, subscribers, ATIF output, or typed OpenTelemetry and OpenInference projections.
Install Maintain Observability
$ npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-observability --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/maintain-observability .claude/skills/maintain-observability && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "maintain-observability" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-observability into .claude/skills/maintain-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-observability", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-observabilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-observability --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/maintain-observability .agents/skills/maintain-observability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintain-observability" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-observability into .agents/skills/maintain-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-observability", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-observability --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/maintain-observability .cursor/skills/maintain-observability && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "maintain-observability" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-observability into .cursor/skills/maintain-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-observability", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/NeMo-Relay.git --path .agents/skills/maintain-observability--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-observability --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/maintain-observability .gemini/skills/maintain-observability && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "maintain-observability" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-observability into .gemini/skills/maintain-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-observability", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/NeMo-Relay maintain-observabilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/maintain-observability .github/skills/maintain-observability && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "maintain-observability" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-observability into .github/skills/maintain-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-observability", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/NeMo-Relay maintain-observability --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/maintain-observability .opencode/skills/maintain-observability && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "maintain-observability" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/maintain-observability into .opencode/skills/maintain-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-observability", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
maintain-observability- GitHub stars
- 190
- Token cost
- ~858 tokens
- SKILL.md length
- 332 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Change NeMo Relay event fields, subscribers, ATIF output, or typed OpenTelemetry and OpenInference projections.
- Instrumentation examples that leave observability contracts unchanged
- SKILL.md covers Surfaces To Keep In Sync, Design Checklist, Validation and References
- Calls just
- Tasks that involve Observability
What it does
Maintain Observability is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Change NeMo Relay event fields, subscribers, ATIF output, or typed OpenTelemetry and OpenInference projections. Do not use for instrumentation examples that leave observability contracts unchanged.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Observability. It works with OpenTelemetry. The repository describes itself as: Multi-language agent runtime and library for execution scope management, lifecycle events, and middleware on tool and LLM calls. The licence is Apache-2.0.
When your agent uses it
- Instrumentation examples that leave observability contracts unchanged
- Tasks that involve Observability
Example prompts
- “/maintain-observability”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 651453f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
just
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Maintain Observability loads about 858 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 332 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NVIDIA/NeMo-Relay at commit 651453f, republished under its Apache-2.0 licence (© NVIDIA). 332 words, ~858 tokens.
Download SKILL.mdSave it as
.claude/skills/maintain-observability/SKILL.md (or your agent's skills folder).- name
- maintain-observability
- description
- Change NeMo Relay event fields, subscribers, ATIF output, or typed OpenTelemetry and OpenInference projections. Do not use for instrumentation examples that leave observability contracts unchanged.
- license
- Apache-2.0
Maintain Observability Surfaces
Use this skill when changing event fields, exporter behavior, subscriber config,
or binding parity for ATIF or the full, gen_ai, and openinference
OpenTelemetry projections.
Surfaces To Keep In Sync
- Core event model and emitted fields
crates/core/src/observability/atif.rscrates/core/src/observability/otel.rscrates/core/src/observability/openinference.rs- FFI and binding-native wrappers where the config or lifecycle is exposed
- Python, Go, and Node.js config objects and subscriber/exporter methods
- Observability config version 3, where one
opentelemetrysection contains typed endpoints and OpenInference has no standalone public surface - Docs under
docs/about-nemo-relay/concepts/subscribers.mdxanddocs/configure-plugins/observability/
Design Checklist
- Is this an event-model change, exporter-config change, or lifecycle change?
- Do all bindings expose the same logical knobs and semantics?
- Does every OpenTelemetry endpoint require a type and nonblank destination?
- Does each endpoint resolve
header_envvalues at activation and reject missing, blank, or duplicate headers? - Do layered ATOF sink, ATIF storage, and OpenTelemetry endpoint lists concatenate with higher-precedence entries first?
- Are OpenTelemetry and OpenInference dependencies unconditional rather than Cargo feature-gated?
- Does
gen_aiavoidnemo_relay.*, project sanitized LLM instructions and messages into the standard content attributes, and emit minimal spans for scopes without GenAI semantics so their parentage is preserved? - Does
enable_full_payloadspreserve complete sanitized LLM request input and annotations while leaving credential removal and sanitizers active? - Does Relay derive compliant trace and span IDs consistently across typed OpenTelemetry endpoints while preserving lifecycle parentage?
- Are mark events, start/end events, and orphan cases still handled correctly?
- Does a sanitized tool result annotation remain opaque under
category_profile.tool_result_annotation, ATIF observation-resultextra.tool_result_annotation, and the singlenemo_relay.tool.result.annotationattribute infullandopeninference, whilegen_aiomits it? - Do examples and docs use each exporter's documented flush/deregister order before shutdown?
- Are span or trajectory fields still derived from the intended event data?
Validation
- Run the affected Rust crate tests plus
just test-rustif event fields changed. - Run only the binding suites whose exposed configuration, lifecycle, event, or exporter contract changed.
- Update and validate docs or examples when the public workflow, documented observability contract, or emitted output changed.
References
docs/about-nemo-relay/concepts/subscribers.mdxdocs/configure-plugins/observability/about.mdxdocs/configure-plugins/observability/opentelemetry.mdxcrates/core/src/observability/atif.rscrates/core/src/observability/otel.rscrates/core/src/observability/openinference.rs
© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/maintain-observability of NVIDIA/NeMo-Relay.
Open the folder on GitHubat commit 651453f
Compare with similar skills
Maintain Observability next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Maintain Observability this skillNVIDIA/NeMo-Relay | 190 | — | ~858 | Automated safety check: Pass | Apache-2.0 | |
| Motel Debugkitlangton/motel | 298 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Tempsgotempsh/temps | 822 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Axiom Metrics Queryopenclaw/clawhub | 9.5k | — | ~2.6k | Automated safety check: Pass | MIT | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 412 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Agent Kill Switchvivekchand/clawmetry | 424 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Temps
gotempsh/temps
Manage, deploy, operate, and instrument applications with Temps.
Axiom Metrics Query
openclaw/clawhub
Explores and queries OpenTelemetry metrics in Axiom MetricsDB, listing datasets, metrics and tags first and picking the right aggregation for each metric's type.
UModel Root Cause Analysis
alibaba/UnifiedModel
Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.
Agent Kill Switch
vivekchand/clawmetry
Give the human an off switch and a cost meter for the coding agents on this machine, using ClawMetry.
Agentmeasure
roy-tong/AgentMeasure
Check whether agent telemetry preserves measurement semantics.
More from NVIDIA/NeMo-Relay
All 30 skills in this repo- Official
Draft Release Notes
NVIDIA/NeMo-Relay
Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.
- Official
Nemo Relay Migrate From Flow
NVIDIA/NeMo-Relay
A skill your agent uses when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI…
- Official
Add Middleware
NVIDIA/NeMo-Relay
Add a new NeMo Relay guardrail or intercept type, registration surface, or pipeline stage.
- Official
Contribute Docs
NVIDIA/NeMo-Relay
Author or edit NeMo Relay documentation or examples when repository-specific MDX, public API, integration, or release-history conventions matter.
- Official
Maintain CI
NVIDIA/NeMo-Relay
Change or review NeMo Relay GitHub Actions workflows where permissions, pinned actions, caching, reusable workflows, or release gates require repository-specific handling.
- Official
Nemo Relay Install
NVIDIA/NeMo-Relay
A skill your agent uses when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, or maintained framework integrations, or when explaining Hermes Agent's…
Related
Works with
Categories
Questions about Maintain Observability
What does Maintain Observability do?
Change NeMo Relay event fields, subscribers, ATIF output, or typed OpenTelemetry and OpenInference projections. Maintain Observability is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Change NeMo Relay event fields, subscribers, ATIF output, or typed OpenTelemetry and OpenInference projections.
When should I use Maintain Observability?
Maintain Observability fits situations like: instrumentation examples that leave observability contracts unchanged; tasks that involve Observability.
How do I install Maintain Observability in Claude Code?
Run `npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a claude-code`. Or copy the skill folder (.agents/skills/maintain-observability in NVIDIA/NeMo-Relay) into .claude/skills/maintain-observability in your project. Claude Code loads it when a task matches its description.
How do I install Maintain Observability in Codex?
Run `npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a codex`. Or copy the skill folder (.agents/skills/maintain-observability in NVIDIA/NeMo-Relay) into .agents/skills/maintain-observability in your project. Codex loads it when a task matches its description.
Can I use Maintain Observability in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/NeMo-Relay --skill maintain-observability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain-observability, .gemini/skills/maintain-observability, .github/skills/maintain-observability and .opencode/skills/maintain-observability in your project.
What does Maintain Observability need to run?
Going by SKILL.md and its folder, Maintain Observability needs the command-line tools its instructions call (just). Our summary lists: Node.js.
Does Maintain Observability access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Maintain Observability safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Maintain Observability use?
Maintain Observability is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Maintain Observability use?
About 858 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Maintain Observability?
Skills that share tags, products or a category with Maintain Observability: Motel Debug (kitlangton/motel, 298 stars), Temps (gotempsh/temps, 822 stars), Axiom Metrics Query (openclaw/clawhub, 9.5k stars) and UModel Root Cause Analysis (alibaba/UnifiedModel, 412 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maintain Observability?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NeMo-Relay, which has 190 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 7, 2026.
Source: NVIDIA/NeMo-Relay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.