Agent skill · nvidia
nvshmem-select-remote-transport
Select an NVSHMEM remote transport from target system and kernel evidence. Use for inter-node selection, compatibility checks, or configuration.
What it needs
About 9k tokens when loaded.
What this skill does
Select an NVSHMEM Remote Transport Purpose Recommend one NVSHMEM transport configuration from static evidence. Separate hard eligibility from expected kernel fit, distinguish documented facts from inference. Focus on read-only system probes and source inspection. Do not run NVSHMEM applications, correctness tests, or performance benchmarks. Prerequisites Require an inventory of installed transport plugins before recommending a transport that must be available in the selected installation. Record the installed NVSHMEM version when it is readily available, but do not require patch-level version verification for ordinary transport selection or stable settings such as NVSHMEMREMOTETRANSPORT. Require exact-version evidence only when the decision depends on a release gate, known issue, changed setting, or release-specific operation or memory-mode limitation. Use the sibling $nvshmem-docs workflow, or its readable ../nvshmem-docs/SKILL.md, when the user requests current/exact official verification or an exact-version-sensitive decision cannot be resolved from the bundled matrix. Do not invoke it merely because the target patch differs from a source version reviewed by the matrix. Require no API key, privileged command, network access for inspection, or benchmark execution. Inputs Core Recommendation Inputs Installed transport-plugin inventory, or explicit user confirmation of the available transport. Target fabric/provider: InfiniBand, RoCE, EFA, Slingshot/CXI, UCX-managed, or NVLink-only. For kernel/workload analysis only, selected CUDA kernel/application source, or a profile covering: host, on-stream, or device API use; RMA, AMO, signaling, synchronization, or collective operations; typical and range of message sizes; issuing threads, warps, and CTAs; peer fan-out and expected simultaneous message rate. Job scale: total PEs and local PEs per node. Intended outcome: general default, latency-sensitive, throughput-oriented, or compatibility-first. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/nvshmem-select-remote-transport