nvidia-skill-finder
Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill. Trigger on NVIDIA products, hardware, software,…
Extract per-molecule embeddings from any encoder-bearing KERMT checkpoint. Use a local checkpoint or optionally download a pinned Hugging Face model bundle using HF_TOKEN if configured. Run containerized embedding extraction and write model bundles, per-readout .npy embeddings,
$ npx -y skills add NVIDIA/skills --skill bionemo-kermt-embed --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/bionemo-kermt-embedContext preview
The summary Claude sees to decide when to auto-load this skill.
Extract per-molecule embeddings from any encoder-bearing KERMT checkpoint. Use a local checkpoint or optionally download a pinned Hugging Face model bundle using HF_TOKEN if configured. Run containerized embedding extraction and write model bundles, per-readout .npy embeddings,
name: kermt-embed description: Extract per-molecule embeddings from any encoder-bearing KERMT checkpoint. Use a local checkpoint or optionally download a pinned Hugging Face model bundle using HF_TOKEN if configured. Run containerized embedding extraction and write model bundles, per-readout .npy embeddings, canonical SMILES, and validity arrays to user-selected host directories. license: Apache-2.0 compatibility: Requires docker, nvidia-container-toolkit, and a CUDA-capable NVIDIA GPU. Designed for Claude Code, Codex, and Nemotron. metadata: owner: evax@nvidia.com classification: workflow-skill risk_tier: skill # Line/token budget: targets ~150 lines / ~1800 tokens — within the # 500-line / 5000-token cap for skill files.
Extract per-molecule embeddings from any encoder-bearing KERMT checkpoint. The skill is the workflow orchestrator: validate ckpt, validate CSV, clean SMILES, launch the runner blocking, return the per-readout `.npy` files.
Set `SKILL_DIR` to the absolute path of this installed skill directory. Export `KERMT_REPO` as the absolute path to the KERMT checkout used for model execution. The bundled container helper mounts that checkout at `/workspace` and this skill at `/skill` (read-only). Commands inside the container use `/skill/scripts/`; defaults are bundled in `config/`. See [Released models](references/released-models.md) for checkpoint bundle requirements.
The optional released-model branch reads `config/released_model.json` for the Hugging Face repository, pinned revision, and filenames. The bundled `scripts/fetch_released_model.py` downloads the model bundle over HTTPS into the host directory the user selects. Public models work without credentials; if `HF_TOKEN` is set, the container helper forwards it for Hugging Face authentication. Prepared data, logs, and workflow results go into the chosen run directory.
`hidden 800` per readout, so ~10–20 MB per 1k molecules across the 4 readouts. Plus a small `canonical_smiles.npy` + `validity.npy` per run.
Required:
are ignored (no targets needed).
Checkpoint (optional — defaults to the released model if omitted):
hybrid, and finetuned ckpts are all accepted. The validator only refuses ckpts with no encoder. **If omitted**, the skill offers to download the released pretrained hybrid model **nvidia/NV-KERMT-70M-v2** and embed with it — see "Resolve & validate the checkpoint" (workflow step 3).
the interactive prompt (for non-interactive / agent runs). Mutually exclusive with `--ckpt`.
`$KERMT_REPO/models/NV-KERMT-70M-v2/`). An already-complete bundle there is reused, not re-downloaded.
Optional:
`prepare_data.json` in `<dir>`.
Let `$KERMT_REPO` be the path to your kermt repo checkout.
1. **Pre-flight: container + system probe.**
"$SKILL_DIR/scripts/kermt_container.sh" check_system
2. **Compute run directory.**
RUN_DIR=$KERMT_REPO/runs/embed_$(date -u +%Y-%m-%dT%H-%M-%SZ)
3. **Resolve & validate the checkpoint.**
**Resolve — only if `--ckpt` was omitted.** Default to the released pretrained hybrid model **nvidia/NV-KERMT-70M-v2**:
"No checkpoint given — download the released model nvidia/NV-KERMT-70M-v2 (NVIDIA Open Model License, https://huggingface.co/nvidia/NV-KERMT-70M-v2) and embed with it? [y/N]". **Never download without an explicit yes** (or `--pretrained-release`). If both `--ckpt` and `--pretrained-release` are given, abort — they conflict.
`--model-dir <dir>` if given. An already-complete bundle is reused.
"$SKILL_DIR/scripts/kermt_container.sh" run --model-dir <save-dir> -- \
"python /skill/scripts/fetch_released_model.py --out /model"Parse the JSON; abort on `ok: false` (surface `errors`). On success set `<user-ckpt> = <save-dir>/kermt_contrastive_v2.0.pt`.
**Validate** the resolved (or user-provided) ckpt:
"$SKILL_DIR/scripts/kermt_container.sh" run --ckpt <user-ckpt> -- \
"python /skill/scripts/check_checkpoint.py --mode embed --ckpt /ckpt"Parse JSON. Abort on `ok: false`. The validator only refuses encoder-less ckpts (rare).
4. **Validate the data.**
"$SKILL_DIR/scripts/kermt_container.sh" run --data <user-csv> -- \
"python /skill/scripts/check_data.py --mode embed --csv /data/<basename>"5. **Prepare the data** (clean-only — no features step).
"$SKILL_DIR/scripts/kermt_container.sh" run --data <user-csv> --run-dir $RUN_DIR -- \
"python /skill/scripts/prepare_data.py --mode embed \\
--csv /data/<basename> --out /runs/data"Outputs land at `$RUN_DIR/data/prepare_data.json` with a single `clean_csv` path. `task/extract_embeddings.py` featurizes from SMILES on the fly.
6. **Launch the runner (blocking).**
"$SKILL_DIR/scripts/kermt_container.sh" run \\
--ckpt <user-ckpt> --run-dir $RUN_DIR -- \\
"python /skill/scripts/run_extract_embeddings.Official, NVIDIA-verified Agent Skills for Claude Code, Codex, and other coding agents.
Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill. Trigger on NVIDIA products, hardware, software,…
Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and…
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras;…
Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample…