YugabyteDB ASH Instrumentation
yugabyte/yugabyte-db
Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.
A skill your agent uses when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation.
Install Nemo Relay Instrument Context Isolation
$ npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-instrument-context-isolation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-instrument-context-isolation --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/skills/nemo-relay-instrument-context-isolation .claude/skills/nemo-relay-instrument-context-isolation && 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 "nemo-relay-instrument-context-isolation" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-instrument-context-isolation into .claude/skills/nemo-relay-instrument-context-isolation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-instrument-context-isolation", 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/skills/nemo-relay-instrument-context-isolationType 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 nemo-relay-instrument-context-isolation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-instrument-context-isolation --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/skills/nemo-relay-instrument-context-isolation .agents/skills/nemo-relay-instrument-context-isolation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nemo-relay-instrument-context-isolation" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-instrument-context-isolation into .agents/skills/nemo-relay-instrument-context-isolation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-instrument-context-isolation", 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 nemo-relay-instrument-context-isolation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-instrument-context-isolation --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/skills/nemo-relay-instrument-context-isolation .cursor/skills/nemo-relay-instrument-context-isolation && 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 "nemo-relay-instrument-context-isolation" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-instrument-context-isolation into .cursor/skills/nemo-relay-instrument-context-isolation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-instrument-context-isolation", 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 skills/nemo-relay-instrument-context-isolation--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 nemo-relay-instrument-context-isolation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-instrument-context-isolation --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/skills/nemo-relay-instrument-context-isolation .gemini/skills/nemo-relay-instrument-context-isolation && 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 "nemo-relay-instrument-context-isolation" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-instrument-context-isolation into .gemini/skills/nemo-relay-instrument-context-isolation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-instrument-context-isolation", 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 nemo-relay-instrument-context-isolationInstalls 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 nemo-relay-instrument-context-isolation -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/skills/nemo-relay-instrument-context-isolation .github/skills/nemo-relay-instrument-context-isolation && 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 "nemo-relay-instrument-context-isolation" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-instrument-context-isolation into .github/skills/nemo-relay-instrument-context-isolation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-instrument-context-isolation", 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 nemo-relay-instrument-context-isolation -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 nemo-relay-instrument-context-isolation --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/skills/nemo-relay-instrument-context-isolation .opencode/skills/nemo-relay-instrument-context-isolation && 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 "nemo-relay-instrument-context-isolation" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-instrument-context-isolation into .opencode/skills/nemo-relay-instrument-context-isolation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-instrument-context-isolation", 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
nemo-relay-instrument-context-isolation- GitHub stars
- 192
- Token cost
- ~667 tokens
- SKILL.md length
- 290 words
- Files
- 5
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation.
- Concurrent requests
- SKILL.md covers Core Rule, Embedded Scope Model, Per-Language Defaults and Common Failures, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Agents need independent NeMo Relay scope stacks and correct ancestry propagation
What it does
Nemo Relay Instrument Context Isolation is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Use this skill when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `BENCHMARK.md`, `evals/evals.json` and `skill-card.md`).
It sits in Development, covering Async programming. 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
- Concurrent requests
- Agents need independent NeMo Relay scope stacks and correct ancestry propagation
Example prompts
- “/nemo-relay-instrument-context-isolation”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 804d570. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Nemo Relay Instrument Context Isolation loads about 667 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 290 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 804d570, republished under its Apache-2.0 licence (© NVIDIA). 290 words, ~667 tokens.
Download SKILL.mdSave it as
.claude/skills/nemo-relay-instrument-context-isolation/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- nemo-relay-instrument-context-isolation
- description
- Use this skill when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation.
- license
- Apache-2.0
- metadata.author
- NVIDIA Corporation and Affiliates
Use Context Isolation
Use this skill when an application runs concurrent requests, worker pools, async tasks, goroutines, or multiple agents in the same process. Treat scope-stack ownership as part of the request boundary.
Core Rule
Each independent request, agent, or workflow needs its own scope stack. Do not share one mutable stack across unrelated concurrent work unless you want shared ancestry and shared scope-local middleware.
Embedded Scope Model
- A root scope is always present, and pushed scopes form a parent-child tree beneath it.
- Scope hierarchy determines event parentage, lifetime boundaries, and visibility for scope-local middleware and subscribers.
- Standard scope types include
Agent,Function,Tool,Llm,Retriever,Embedder,Reranker,Guardrail,Evaluator,Custom, andUnknown. - Scope start and end events can carry semantic
inputandoutputpayloads when the scope represents a request, task, or meaningful result boundary. - Scope-local registrations disappear when the owning scope closes; use them for behavior that should not outlive a request or agent run.
- Mark events are useful for retries, checkpoints, interrupts, and important state transitions that are not full spans.
Per-Language Defaults
- Python: rely on task-local behavior via
get_scope_stack()andcontextvars, or explicitly propagate when work leaves the current execution context - Rust core: use runtime helpers such as
create_scope_stack(),current_scope_stack(), andset_thread_scope_stack(...)when an integration needs explicit stack ownership - Go: use
NewScopeStack()andScopeStack.Run(...)for goroutine-safe usage - Node.js: create and set a scope stack explicitly for the current execution
path with
createScopeStack()andsetThreadScopeStack(...)
Common Failures
- Events from different requests appear under one root UUID
- Scope-local middleware leaks across requests
- Worker-thread work runs without the expected active scope
- Integrations activate NeMo Relay without an explicitly initialized stack
- Relying on a thread-local stack after crossing async tasks, goroutines, or JS worker boundaries
Related Skills
nemo-relay-instrument-callsnemo-relay-plugin-observabilitynemo-relay-debug-runtime-integration
© 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
SKILL.md and 4 other files in skills/nemo-relay-instrument-context-isolation of NVIDIA/NeMo-Relay.
- SKILL.md
- BENCHMARK.md
- evals/evals.json
- skill-card.md
- skill.oms.sig
Open the folder on GitHubat commit 804d570
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in NVIDIA/NeMo-Relay, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Nemo Relay Instrument Context Isolation 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 |
|---|---|---|---|---|---|---|
| Nemo Relay Instrument Context Isolation this skillNVIDIA/NeMo-Relay | 192 | — | ~667 | Automated safety check: Pass | Apache-2.0 | |
| YugabyteDB ASH Instrumentationyugabyte/yugabyte-db | 11k | — | ~4.5k | Automated safety check: Pass | Custom licence | |
| Mirage VFS Adapter Authoringstrukto-ai/mirage | 3.7k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Golang Patternsantoniopaya22/go-rest-template | 172 | 9 repos | ~3.5k | Automated safety check: Pass | None | |
| Rust Async Patternsdiodeme/Gold-Band | 143 | 10 repos | ~3.1k | Automated safety check: Pass | AGPL-3.0 | |
| Swift Concurrencyhenrypldev/react-native-nitro-mlx | 100 | 3 repos | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Mirage VFS Adapter Authoring
strukto-ai/mirage
Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.
Golang Patterns
antoniopaya22/go-rest-template
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
Rust Async Patterns
diodeme/Gold-Band
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns.
Swift Concurrency
henrypldev/react-native-nitro-mlx
Diagnose Swift Concurrency issues, refactor callback-based code to async/await, and guide Swift 6 migration when working with tasks, actors, @MainActor, Sendable, data races, thread safety, or…
Rust Engineer
farm-fe/farm
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions.
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
Categories
Questions about Nemo Relay Instrument Context Isolation
What does Nemo Relay Instrument Context Isolation do?
A skill your agent uses when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation. Nemo Relay Instrument Context Isolation is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Use this skill when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation.
When should I use Nemo Relay Instrument Context Isolation?
Nemo Relay Instrument Context Isolation fits situations like: concurrent requests; agents need independent NeMo Relay scope stacks and correct ancestry propagation.
How do I install Nemo Relay Instrument Context Isolation in Claude Code?
Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-instrument-context-isolation -a claude-code`. Or copy the skill folder (skills/nemo-relay-instrument-context-isolation in NVIDIA/NeMo-Relay) into .claude/skills/nemo-relay-instrument-context-isolation in your project. Claude Code loads it when a task matches its description.
How do I install Nemo Relay Instrument Context Isolation in Codex?
Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-instrument-context-isolation -a codex`. Or copy the skill folder (skills/nemo-relay-instrument-context-isolation in NVIDIA/NeMo-Relay) into .agents/skills/nemo-relay-instrument-context-isolation in your project. Codex loads it when a task matches its description.
Can I use Nemo Relay Instrument Context Isolation 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 nemo-relay-instrument-context-isolation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nemo-relay-instrument-context-isolation, .gemini/skills/nemo-relay-instrument-context-isolation, .github/skills/nemo-relay-instrument-context-isolation and .opencode/skills/nemo-relay-instrument-context-isolation in your project.
What does Nemo Relay Instrument Context Isolation need to run?
SKILL.md names no scripts, command-line tools or credentials: Nemo Relay Instrument Context Isolation is instructions for the agent only. Our summary lists: Node.js.
Does Nemo Relay Instrument Context Isolation 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 Nemo Relay Instrument Context Isolation 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 Nemo Relay Instrument Context Isolation use?
Nemo Relay Instrument Context Isolation 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 Nemo Relay Instrument Context Isolation use?
About 667 tokens (SKILL.md is roughly 2.7k 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 Nemo Relay Instrument Context Isolation?
Skills that share tags, products or a category with Nemo Relay Instrument Context Isolation: YugabyteDB ASH Instrumentation (yugabyte/yugabyte-db, 11k stars), Mirage VFS Adapter Authoring (strukto-ai/mirage, 3.7k stars), Golang Patterns (antoniopaya22/go-rest-template, 172 stars) and Rust Async Patterns (diodeme/Gold-Band, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nemo Relay Instrument Context Isolation?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NeMo-Relay, which has 192 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 9, 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.