claudemods

Sourcesnvidia/skills

nvidia/skills Indexed

Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end.

Open upstream repository

Indexed The index holds package records for this repository. The package count is historical registry records; it does not mean those packages are available now.

Repository

Canonical name
NVIDIA/skills
GitHub repository ID
1167034425
Package records
394 (historical registry records, not current availability)

Discovery and queue

First recorded source
marketplace:anthropics/claude-plugins-official
Discovered
Queue state
ok
Recorded errors
0
Last settled processing
Next-check eligibility
Eligible from

The first recorded source is what the queue stored first, not the full discovery history. The error count increases when processing ends in the error state and resets after a successful settlement; it is not a count of all attempts. “Last settled processing” is when it finished, not when it started.

Eligibility is calculated as of . It is not a schedule: each collector run handles only a limited number of sources, and being eligible does not promise when a check happens.

Last saved scan

Repository metadata read
Scan status
complete
Scan saved
Extractor version
2
Continuation record
None

The scan record is separate from the queue state: the queue state shows processing progress, the scan record shows what was last saved. A continuation record only means unfinished state is stored; it has no remaining count.

Source-file evidence coverage

Raw counts of the pinned source files that stored package versions reference in this repository. They show what has been recorded, not how complete the repository is.

Scope and limits

Counts distinct pinned file links (repository, commit, path) across all stored versions, from any package, that name exactly this repository's canonical name. Files of packages owned by this repository are not counted unless some version links to them here. Alias names are not merged and no history is guessed from a current name.

“Known” means a regular-file identity is recorded. It does not mean a whole directory or package is covered. Links that are not valid pinned file URLs are not counted.

395 pinned source files referenced

  • 395 known
  • 0 absent at commit
  • 0 file listing truncated
  • 0 unsupported
  • 0 not recorded
  • 0 read failed

Deduplicated by repository, commit and path; the same path at two commits counts as two file identities. These are not component-group counts.

Failed source-commit reads 0

No source commit has a stored failed read for files that are still unrecorded.

Linked packages 394

Linked by verified repository identity. The count is historical registry records, not current availability.

Showing 21–40 of 394 results

  • deepstream-run-mv3dtSkill

    Run and operate the DeepStream Multi-View 3D Tracking reference app, also known as MV3DT. Use when the user asks to set up prerequisites, run shipped MV3DT samples, run Multi-View 3D Tracking on custom synchronized MP4 datasets, import cam…

  • deepstream-sopSkill

    Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via …

  • dicom-metadata-extractSkill

    Used for extracting selected metadata from one DICOM file and flagging standard-tag PHI presence. Not for anonymization or clinical use.

  • dicom-series-preflightSkill

    Used for header-only preflight of one DICOM series folder before conversion or inference. Not for de-identification or clinical clearance.

  • dicom-series-to-volumeSkill

    Used for converting one CT DICOM series folder to a HU NIfTI volume with affine evidence. Not for multi-frame DICOM or clinical use.

  • diffdock-nimSkill

    Run DiffDock molecular docking via NVIDIA NIM to predict small-molecule binding poses against protein targets. Use for DiffDock, molecular docking, ligand docking, blind docking, SMILES or SDF ligands, ranked poses, confidence scores, host…

  • digital-health-clinical-asr-buildSkill

    Stage 2 of the Clinical ASR Flywheel. Use when curating clinical terms, tagging IPA, and synthesizing a NeMo manifest. NOT for scoring (use /digital-health-clinical-asr-eval).

  • digital-health-clinical-asr-evalSkill

    Stage 3 of Clinical ASR Flywheel. Score a NeMo manifest, produce the five-section KER leaderboard (by-ipa_source diagnostic). Not for ASR auth (/riva-asr).

  • digital-health-clinical-asr-finetuneSkill

    Stage 4 of the Clinical ASR Flywheel. Use when priority KER is above 0.3 to run stock NeMo SFT on Parakeet TDT v2 and offline cycle N+1 re-eval. NOT for generic word boosting (use /finetune-asr).

  • digital-health-clinical-asr-setupSkill

    Stage 1 of Clinical ASR Flywheel. Use when bootstrapping a cycle: NVCF+MW disclosure, NVIDIA_API_KEY check, deps install, TTS+ASR smoke test.

  • doca-aes-gcmSkill

    Use this skill when the user is doing hands-on DOCA AES-GCM work on a BlueField DPU or ConnectX NIC — configuring `doca_aes_gcm_task_encrypt` / `_task_decrypt`, querying `doca_aes_gcm_cap_*` for per-key-type (only `DOCA_AES_GCM_KEY_128` / …

  • doca-argpSkill

    Use this skill for hands-on DOCA Arg Parser CLI work on a shipped sample or new DOCA-using app — adding / removing / renaming flags; wiring `doca_argp_init` → register params → `doca_argp_start` → `doca_argp_destroy` in order; picking a pa…

  • doca-argusSkill

    Use this skill when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for suspicious activity, integrity violations, and operatio…

  • doca-bare-metal-deploymentSkill

    Use this skill for launching, supervising, debugging, OR platform lifecycle on a BlueField — BFB install, RShim/TMFIFO, host PF rebind, post-BFB recovery — taking a DOCA-linked binary to a healthy run directly on hardware (host x86 + BlueF…

  • doca-benchSkill

    Run `doca_bench` (DOCA 2.7.0 or newer) to measure throughput, bulk latency, precision latency, or maximum bandwidth for RDMA, Compress, AES-GCM, SHA, DMA, EC, Ethernet, Comch, or GPUNetIO on a host or BlueField Arm. Use it to discover enab…

  • doca-bench-extensionSkill

    Use this skill when the operator is authoring, building, loading, or debugging a custom doca-bench plug-in — a versioned shared library with DOCA_EXPERIMENTAL-marked C entry points that doca-bench loads to measure a workload class its buil…

  • doca-bf3-deploymentSkill

    Use this skill for BlueField-3 (BF3) day-1 platform bring-up via the classic RShim/BFB path: pushing a BlueField bundle (BFB) to the DPU over RShim with bfb-install from the host, the host-to-DPU TMFIFO management channel (tmfifo_net0, the…

  • doca-bf4-deploymentSkill

    WARNING: guides potentially IRREVERSIBLE BlueField-4 hardware operations (PLDM firmware burns, ISO reflashes, power cycles, BMC factory resets) that can brick firmware, corrupt boot media, or cause outages — a maintenance window and rollba…

  • doca-capsSkill

    Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS…

  • doca-collectx-deploymentSkill

    Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent…

Saved scan notes 0

No additional scan notes are stored.

Recorded aliases 0

When last recorded, these names pointed to this repository. This is a recorded resolution, not a live GitHub check; packages and metadata are never merged because of it.

No aliases pointing to this repository are recorded.

Unsupported marketplace entries 0

Entries in this repository's marketplace that this registry does not support yet. They are preserved source data and are never fetched or executed.

No unsupported entries are recorded.