Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
A skill your agent uses when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptivehints…
Install Nemo Relay Plugin Adaptive Tuning
$ npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-plugin-adaptive-tuning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-plugin-adaptive-tuning --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-plugin-adaptive-tuning .claude/skills/nemo-relay-plugin-adaptive-tuning && 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-plugin-adaptive-tuning" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-plugin-adaptive-tuning into .claude/skills/nemo-relay-plugin-adaptive-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-plugin-adaptive-tuning", 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-plugin-adaptive-tuningType 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-plugin-adaptive-tuning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-plugin-adaptive-tuning --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-plugin-adaptive-tuning .agents/skills/nemo-relay-plugin-adaptive-tuning && 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-plugin-adaptive-tuning" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-plugin-adaptive-tuning into .agents/skills/nemo-relay-plugin-adaptive-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-plugin-adaptive-tuning", 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-plugin-adaptive-tuning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-plugin-adaptive-tuning --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-plugin-adaptive-tuning .cursor/skills/nemo-relay-plugin-adaptive-tuning && 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-plugin-adaptive-tuning" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-plugin-adaptive-tuning into .cursor/skills/nemo-relay-plugin-adaptive-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-plugin-adaptive-tuning", 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-plugin-adaptive-tuning--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-plugin-adaptive-tuning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/NeMo-Relay nemo-relay-plugin-adaptive-tuning --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-plugin-adaptive-tuning .gemini/skills/nemo-relay-plugin-adaptive-tuning && 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-plugin-adaptive-tuning" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-plugin-adaptive-tuning into .gemini/skills/nemo-relay-plugin-adaptive-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-plugin-adaptive-tuning", 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-plugin-adaptive-tuningInstalls 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-plugin-adaptive-tuning -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-plugin-adaptive-tuning .github/skills/nemo-relay-plugin-adaptive-tuning && 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-plugin-adaptive-tuning" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-plugin-adaptive-tuning into .github/skills/nemo-relay-plugin-adaptive-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-plugin-adaptive-tuning", 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-plugin-adaptive-tuning -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-plugin-adaptive-tuning --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-plugin-adaptive-tuning .opencode/skills/nemo-relay-plugin-adaptive-tuning && 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-plugin-adaptive-tuning" agent skill from https://github.com/NVIDIA/NeMo-Relay/tree/main/skills/nemo-relay-plugin-adaptive-tuning into .opencode/skills/nemo-relay-plugin-adaptive-tuning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nemo-relay-plugin-adaptive-tuning", 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-plugin-adaptive-tuning- GitHub stars
- 192
- Token cost
- ~1.1k tokens
- SKILL.md length
- 550 words
- Files
- 7 (incl. references)
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptivehints…
- Works in 10 steps: Confirm the app emits scope events and… → Capture a baseline for the workflow you… → Enable adaptive telemetry with in-memory… → …
- Baseline NeMo Relay instrumentation exists and the user wants to configure
- SKILL.md covers Use This When, Do Not Use This When, Default Guidance and Embedded Adaptive Model, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nemo Relay Plugin Adaptive Tuning is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Use this skill when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptivehints, toolparallelism, ACG, hint consumption, or measured rollout.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `BENCHMARK.md`, `evals/evals.json` and `references/config.md`).
It sits in DevOps & Cloud, covering Observability. 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
- Baseline NeMo Relay instrumentation exists and the user wants to configure
- Evaluate adaptive plugin behavior
- Including telemetry
- Toolparallelism
Example prompts
- “/nemo-relay-plugin-adaptive-tuning”
Requirements
- Python 3
- Node.js
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Confirm the app emits scope events and the managed tool or LLM events needed
- Capture a baseline for the workflow you want to improve.
- Enable adaptive telemetry with in-memory state.
- Read references/config.md when exact plugin configuration fields are needed.
- Run representative traffic and inspect reports or runtime events.
- If configuration validation fails or expected events are absent, return the
- Before enabling scheduling, verify tool idempotency and race behavior. Before
- Enable the smallest behavior change in config.
- Read references/hints.md when application logic consumes adaptive hints,
- Compare results against the baseline. If latency, correctness, or failure
What it can do on your machine
Read from SKILL.md and the folder at commit 16d73b4. 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 Plugin Adaptive Tuning loads about 1.1k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 550 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 16d73b4, republished under its Apache-2.0 licence (© NVIDIA). 550 words, ~1,130 tokens.
Download SKILL.mdSave it as
.claude/skills/nemo-relay-plugin-adaptive-tuning/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- 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_memoryandredis. - Tool-parallelism modes are
observe_only,inject_hints, andschedule. - Adaptive Cache Governor providers are
passthrough,anthropic, andopenai; omit ACG until prompt-cache planning is needed. - Helper APIs exist in Rust
nemo_relay_adaptive, Pythonnemo_relay.adaptive, and Node.jsnemo-relay-node/adaptive. Go and raw FFI are source-first or advanced surfaces.
Default Path
Use this rollout sequence:
- 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.
- Capture a baseline for the workflow you want to improve.
- Enable adaptive telemetry with in-memory state.
- Read
references/config.mdwhen exact plugin configuration fields are needed. - Run representative traffic and inspect reports or runtime events.
- If configuration validation fails or expected events are absent, return the diagnostics and stop. Keep the last known working configuration active.
- Before enabling scheduling, verify tool idempotency and race behavior. Before enabling ACG, verify that provider request payloads are stable.
- Enable the smallest behavior change in config.
- Read
references/hints.mdwhen application logic consumes adaptive hints, tool-parallelism guidance, or ACG diagnostics. - 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.
Show full SKILL.md (143 more words)Show less
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-startednemo-relay-instrument-callsnemo-relay-plugin-observabilitynemo-relay-plugin-build
© 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 6 other files (references) in skills/nemo-relay-plugin-adaptive-tuning of NVIDIA/NeMo-Relay.
- SKILL.md
- BENCHMARK.md
- evals/evals.json
- references/config.md
- references/hints.md
- skill-card.md
- skill.oms.sig
Open the folder on GitHubat commit 16d73b4
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 Plugin Adaptive Tuning 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 Plugin Adaptive Tuning this skillNVIDIA/NeMo-Relay | 192 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 9 repos | ~4.3k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Caveman Gateway Setup
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
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 Plugin Adaptive Tuning
What does Nemo Relay Plugin Adaptive Tuning do?
A skill your agent uses when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptivehints…. Nemo Relay Plugin Adaptive Tuning is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Use this skill when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptivehints, toolparallelism, ACG, hint consumption, or measured rollout.
When should I use Nemo Relay Plugin Adaptive Tuning?
Nemo Relay Plugin Adaptive Tuning fits situations like: baseline NeMo Relay instrumentation exists and the user wants to configure; evaluate adaptive plugin behavior; including telemetry; toolparallelism.
How do I install Nemo Relay Plugin Adaptive Tuning in Claude Code?
Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-plugin-adaptive-tuning -a claude-code`. Or copy the skill folder (skills/nemo-relay-plugin-adaptive-tuning in NVIDIA/NeMo-Relay) into .claude/skills/nemo-relay-plugin-adaptive-tuning in your project. Claude Code loads it when a task matches its description.
How do I install Nemo Relay Plugin Adaptive Tuning in Codex?
Run `npx skills add NVIDIA/NeMo-Relay --skill nemo-relay-plugin-adaptive-tuning -a codex`. Or copy the skill folder (skills/nemo-relay-plugin-adaptive-tuning in NVIDIA/NeMo-Relay) into .agents/skills/nemo-relay-plugin-adaptive-tuning in your project. Codex loads it when a task matches its description.
Can I use Nemo Relay Plugin Adaptive Tuning 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-plugin-adaptive-tuning -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-plugin-adaptive-tuning, .gemini/skills/nemo-relay-plugin-adaptive-tuning, .github/skills/nemo-relay-plugin-adaptive-tuning and .opencode/skills/nemo-relay-plugin-adaptive-tuning in your project.
What does Nemo Relay Plugin Adaptive Tuning need to run?
SKILL.md names no scripts, command-line tools or credentials: Nemo Relay Plugin Adaptive Tuning is instructions for the agent only. Our summary lists: Python 3; Node.js.
Does Nemo Relay Plugin Adaptive Tuning 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 Plugin Adaptive Tuning 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 Plugin Adaptive Tuning use?
Nemo Relay Plugin Adaptive Tuning 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 Plugin Adaptive Tuning use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Nemo Relay Plugin Adaptive Tuning?
Skills that share tags, products or a category with Nemo Relay Plugin Adaptive Tuning: Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nemo Relay Plugin Adaptive Tuning?
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 8, 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.