Skip to main content
skill CX Codex

nemo-relay-plugin-adaptive-tuning — Claude Code skill

nemo-relay-plugin-adaptive-tuning is a Claude Code skill that configures and evaluates NeMo Relay adaptive behavior from runtime signals, including telemetry, parallelism, hints, and prompt-cache planning.

Apache-2.0 178 installs ★ 4,106 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add NVIDIA/skills --skill nemo-relay-plugin-adaptive-tuning -a claude-code
Open on GitHub

What nemo-relay-plugin-adaptive-tuning does

This skill guides adaptive NeMo Relay tuning against a known baseline. It covers baseline capture, in-memory telemetry, runtime-event inspection, configuration diagnostics, and measured rollout. The adaptive component is configured with kind adaptive, rather than by adding separate tuning logic at each call site.

The configuration areas include state, telemetry, adaptive hints, tool parallelism, ACG, and rollout policy. State can use in_memory or redis; tool parallelism supports observe_only, inject_hints, and schedule. ACG providers are passthrough, anthropic, and openai. Use references/config.md for fields and references/hints.md when application code consumes guidance.

Baseline NeMo Relay instrumentation is required first, including scope events and a relevant managed tool or LLM event stream. Before enabling schedule, verify idempotency and race behavior; before ACG, verify stable provider payloads.

What it helps with

  • capture a workflow baseline
  • enable adaptive telemetry with in-memory state
  • evaluate tool hints and parallelism
  • compare a rollout with prior results

Example prompts for the agent

  • Inspect the NeMo Relay baseline and design the smallest adaptive rollout.
  • Configure telemetry with in_memory state, then compare runtime events with the baseline.
  • Check whether schedule and ACG are safe for this tool and LLM event flow.

How to install nemo-relay-plugin-adaptive-tuning

1Skills CLI (Vercel)

npx skills add NVIDIA/skills --skill nemo-relay-plugin-adaptive-tuning -a claude-code

2Manually: put the files in place

~/.claude/skills/nemo-relay-plugin-adaptive-tuning/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/nemo-relay-plugin-adaptive-tuning/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about nemo-relay-plugin-adaptive-tuning

How do I install nemo-relay-plugin-adaptive-tuning in Claude Code?

Run npx skills add NVIDIA/skills --skill nemo-relay-plugin-adaptive-tuning -a claude-code, then open ~/.claude/skills/nemo-relay-plugin-adaptive-tuning/SKILL.md.

What does nemo-relay-plugin-adaptive-tuning do?

It guides configuration and evaluation of NeMo Relay’s adaptive component, covering telemetry, state, hints, tool parallelism, ACG, and measured rollout.

What must be checked before enabling schedule?

Verify tool idempotency and race behavior first. If latency, correctness, or failure rate regresses, restore the last known working configuration.

Source text

SKILL.md · Apache-2.0
---
name: nemo-relay-plugin-adaptive-tuning
description: Use this skill when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptive_hints, tool_parallelism, ACG, hint consumption, or measured rollout.
license: Apache-2.0
metadata:
  author: NVIDIA Corporation and Affiliates
---

# Tune Adaptive Plugin Behavior

## Use This When

Use this skill when a user has baseline NeMo Relay instrumentation and wants to
improve latency, parallelism, prompt-cache behavior, or model-request behavior
from runtime signals.
Keep adaptive behavior measured against a known baseline.

## Do Not Use This When

Do not use this skill when the application is not instrumented yet. Start with
`nemo-relay-instrument-calls` or `nemo-relay-get-started` first.

## Default Guidance

- Observe first, compare against a baseline, then enable one behavior change at
  a time.
- Use the adaptive plugin component rather than inventing separate tuning logic
  or hand-registering adaptive behavior at every call site.
- Start with in-memory state and telemetry-only behavior for local development.
- Move to persistent state only when learned signals must survive restarts or be
  shared across workers.
- Add active behavior only after representative runtime events show what should
  change.

## Embedded Adaptive Model

- Adaptive behavior is configured through the first-party plugin component with
  kind `adaptive`.
- Adaptive requires existing NeMo Relay scopes and at least one relevant
  managed tool or LLM lifecycle event stream because it learns from runtime
  signals.
- Main configuration areas are state, telemetry, adaptive hints, tool
  parallelism, Adaptive Cache Governor (ACG), and rollout policy.
- State backends are `in_memory` and `redis`.
- Tool-parallelism modes are `observe_only`, `inject_hints`, and `schedule`.
- Adaptive Cache Governor providers are `passthrough`, `anthropic`, and
  `openai`; omit ACG until prompt-cache planning is needed.
- Helper APIs exist in Rust `nemo_relay_adaptive`, Python `nemo_relay.adaptive`,
  and Node.js `nemo-relay-node/adaptive`. Go and raw FFI are
  source-first or advanced surfaces.

## Default Path

Use this rollout sequence:

1. Confirm the app emits scope events and the managed tool or LLM events needed
   for the behavior being evaluated. Do not require both call types when the
   workflow uses only one.
2. Capture a baseline for the workflow you want to improve.
3. Enable adaptive telemetry with in-memory state.
4. Read `references/config.md` when exact plugin configuration fields are needed.
5. Run representative traffic and inspect reports or runtime events.
6. If configuration validation fails or expected events are absent, return the
   diagnostics and stop. Keep the last known working configuration active.
7. Before enabling scheduling, verify tool idempotency and race behavior. Before
   enabling ACG, verify that provider request payloads are stable.
8. Enable the smallest behavior change in config.
9. Read `references/hints.md` when application logic consumes adaptive hints,
   tool-parallelism guidance, or ACG diagnostics.
10. Compare results against the baseline. If latency, correctness, or failure
    rate regresses, restore the last known working configuration and retain the
    sanitized diagnostics for review.

## Failure Modes To Avoid

- Do not enable scheduling before tool idempotency and race behavior are known.
- Do not enable prompt-cache planning before provider payloads are stable.
- Do not treat adaptive hints as mandatory instructions unless the consuming
  path explicitly defines that contract.
- Do not use environment variables as the primary adaptive configuration model.
- Do not tune from a single run or unrepresentative traffic.
- Do not suppress or replace original tool and model errors.
- Do not add retries until the call owner defines their safety.
- Revert adaptive behavior when it increases the failure rate.

## Load A Reference When

- You need the exact adaptive config shape -> `references/config.md`
- You need to consume adaptive hints or scheduling guidance in app logic ->
  `references/hints.md`

## Use Another Skill When

- You need to build reusable plugin behavior instead of configuring the built-in
  adaptive component -> `nemo-relay-plugin-build`

## Related Skills

- `nemo-relay-get-started`
- `nemo-relay-instrument-calls`
- `nemo-relay-plugin-observability`
- `nemo-relay-plugin-build`

© NVIDIA Corporation and Affiliates · Apache-2.0 · NVIDIA/skills

Similar skills

All skills for AI and ML →

From the same set312

The whole set →
nemotron-asr-finetune nemotron-asr-finetune coordinates domain and language adaptation for NVIDIA Nemotron Speech and Riva ASR, picking the lowest-cost path from word boosting to full fine-tuning. CX Codex +1 210installs nemo-relay-debug-runtime-integration The nemo-relay-debug-runtime-integration skill traces NeMo Relay runtime faults across loading, scopes, events, plugins, and adaptive wiring. Use it when the package is present but app behavior is wrong. CX Codex +1 197installs nemo-relay-instrument-typed-wrappers nemo-relay-instrument-typed-wrappers configures NeMo Relay typed wrappers and provider codecs while keeping JSON middleware semantics intact. CX Codex +1 182installs nemo-relay-plugin-build nemo-relay-plugin-build is a skill for packaging reusable NeMo Relay behavior as config components or dynamic plugins, with validation and rollback for plugins shared across apps or teams. CX Codex +1 181installs nemo-relay-migrate-from-flow nemo-relay-migrate-from-flow — a skill that automates code, documentation, and config migration from NeMo Flow to NeMo Relay. Handles Python, Rust, Node.js, Go, C FFI, CLI, and observability surfaces. CX Codex +1 171installs doca-bench This skill guides doca_bench runs to measure DOCA library performance on a host or BlueField Arm. Use it to check throughput or latency and record a baseline before changing a system. CX Codex +1 166installs nemo-relay-get-started The nemo-relay-get-started skill routes first-time NeMo Relay users to the right quick-start, then checks whether the initial integration actually works. CX Codex +1 163installs doca-debug doca-debug finds the failing DOCA layer, from installation and linking to runtime and drivers. Use it for unresolved symbols, DOCAERROR results, silent tools, and crashes. CX Codex +1 162installs

Project sponsors

Companies that keep this analytics open