Agent skill · NVIDIA
doca-sta
Use this skill when the user is doing hands-on NVMe-over-Fabrics storage-target work on a BlueField DPU or ConnectX NIC with DOCA STA — standing up a doca_sta DOCA Core context that accelerates the target-side NVMe-oF data path over RDMA, defining doca_sta_subsystem targets (NQN + namespaces) backed by local NVMe-PCI backend disks (doca_sta_be), checking device support via doca_sta_cap_is_supported, sizing the per-connection I/O queues, or debugging DOCA_ERROR_* from a STA call. Trigger even when the user does not say "DOCA STA" — typical implicit phrasings include "my NVMe-oF Connect never completes", "Identify Controller times out over RoCE", "16 I/O queues at depth 1024 — does this BlueField support that", "offload the nvmf target onto the DPU", or "DOCA_ERROR_IO_FAILED on an NVMe read". Refuse and route elsewhere for DOCA install, raw RDMA data movement, raw packet I/O, flow-rule programming, or initiator-side / host NVMe stack work — those belong to other skills.
What it needs
About 8k tokens when loaded.
What this skill does
DOCA STA (Storage Target Acceleration) Where to start: This skill assumes DOCA is already installed and the user is doing hands-on NVMe-over-Fabrics storage-target work on a BlueField-class device with DOCA. Open TASKS.md if the user wants to do something (configure / modify / build / run / test / debug); open CAPABILITIES.md when the question is what can DOCA STA express on this version. If the user has not installed DOCA yet, route to doca-setup first. If the user is asking "is this an NVMe-oF initiator/host transport?", the answer is no — doca-sta accelerates the target side: it presents NVMe-oF docastasubsystem targets backed by local NVMe-PCI disks; the model lives in CAPABILITIES.md ## Capabilities and modes. Example questions this skill answers well The CLASSES of DOCA STA questions this skill is built to answer, each with one worked example. The agent should treat the class as the load-bearing piece — the worked example is a single instance. "How do I bring up an NVMe-oF target that uses the BlueField to accelerate the storage data path?" — worked example: "define a docastasubsystem (NQN) with one namespace backed by a local NVMe-PCI disk (docastabe) and accept NVMe-over-RDMA connections from a remote initiator". Answered by the target-model-and-lifecycle workflow in TASKS.md ## configure + CAPABILITIES.md ## Capabilities and modes target-object table. "Can this BlueField accelerate an NVMe-oF target at all?" — worked example: "my data center is RoCE end-to-end; does this device support DOCA STA target acceleration?". STA transport is RDMA-only (there is no NVMe-over-TCP path). Answered by the capability-query rule (docastacapissupported against a docadevinfo) in CAPABILITIES.md ## Capabilities and modes the discovery step in TASKS.md ## configure. "How deep can I size my I/O queues, and how many I/O queues per connection?" — worked example: "I want 16 I/O queues at depth 1024 each — does this device support that?". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/doca-sta