NVIDIA Model Config Skill
Overview
This skill packages three reusable pieces:
- A script (
scripts/merge_nvidia_config.py) that inserts the NVIDIA provider block into anyopenclaw.jsonfile and configuresapiKeyas a SecretRef by default. - Model entries for Mixtral, Moonshot Kimi, Kimi K2.5, Nemotron Super (1M ctx), Llama 3.1 Nemotron Ultra 253B (128K ctx), and MiniMax M2.5 (204.8K ctx) — delete extras or add more from
openclaw models list --provider nvidia --all. - Instructions for backups, secrets, and where
NVIDIA_API_KEYmust be set so the gateway can resolve it (this is not onlyopenclaw.json).
Use the skill whenever you want to replicate the NVIDIA models.providers.nvidia entry without guessing which keys or nested objects to copy.
Quick start
- Copy or download this skill (e.g.,
rsync -av skills/nvidia-model-config /path/to/other/workspace/skills/). - Obtain your NVIDIA API key and keep it secret (do not commit it).
- Run the script from the target workspace:
python skills/nvidia-model-config/scripts/merge_nvidia_config.py \
--config openclaw.json --backup
--configdefaults toopenclaw.jsonin the current directory.--backupsaves the original file asopenclaw.json.bakbefore overwriting.- By default, the script writes
models.providers.nvidia.apiKeyas:{"source":"env","provider":"default","id":"NVIDIA_API_KEY"}
- Set your key in the runtime environment where the OpenClaw gateway runs. That is not always the same as your interactive shell.
Interactive shell / CLI only (e.g. testing openclaw in a terminal):
export NVIDIA_API_KEY="$YOUR_KEY"
Gateway under systemd (typical on Linux) — the service does not read ~/.bashrc. Put the key in a file the unit loads, for example:
- File:
~/.config/openclaw/gateway.env(mode600):
NVIDIA_API_KEY=your_key_here
- User unit drop-in
~/.config/systemd/user/openclaw-gateway.service.d/override.conf:
[Service]
Environment=NVIDIA_API_KEY=
EnvironmentFile=-/home/YOUR_USER/.config/openclaw/gateway.env
The empty Environment=NVIDIA_API_KEY= clears any inherited value so EnvironmentFile is the single source of truth. Then:
systemctl --user daemon-reload
systemctl --user restart openclaw-gateway.service
You can also keep a personal ~/.config/openclaw/secrets.env and source it from ~/.bashrc for CLI-only use; that does not replace the gateway env above.
If you want to preview the changes before writing, add --dry-run and capture the printed JSON.
What the script does
- Removes legacy plaintext copies of
NVIDIA_API_KEYfrom config (env.vars.*andenv.*) when present. - Creates or updates the
models.providers.nvidiablock with bundled NVIDIA models (Nemotron Super 1M ctx, Nemotron Ultra 253B ~128K ctx, MiniMax M2.5 ~204.8K ctx, plus Mixtral/Kimi entries). NVIDIA may return403if your key is not entitled to a model; pick a model that matches your account and catalog. - Keeps the
api/baseUrlvalues in sync with NVIDIA’sintegrate.api.nvidia.comendpoint. - Supports an explicit legacy mode when needed:
NVIDIA_API_KEY="$YOUR_KEY" \
python skills/nvidia-model-config/scripts/merge_nvidia_config.py \
--config openclaw.json --inline-key
Use --inline-key only for short-lived local tests.
Optional adjustments
- Set default model with
openclaw models set nvidia/<model-id>(full id isnvidia/+ provider model id, e.g.nvidia/nvidia/nemotron-3-super-120b-a12bwhen the provider entry id isnvidia/nemotron-3-super-120b-a12b). - If the target install manages agent defaults manually, add fallback entries under
agents.defaults.model.fallbacksso clients can recover if the primary model fails. - Double-check other agents’
modelslists if they need aliases.
Distribution tips
- Bundle this skill directory and any instructions or scripts you use into a
.zip/.skillfile to share with teammates. - In your documentation, point operators to this SKILL so Codex can reload it and the script automatically when they ask to “add NVIDIA models.”
- Keep real API keys outside of Git. Use environment variables or SecretManagers and rely on the script to merge them at runtime.