Agent skill · NVIDIA
doca-dms
Operate NVIDIA DOCA Management Service (`dmsd` + `dmspe`) on a BlueField, Arm/x86 host, or Kubernetes pod: choose deployment and authentication, configure `-allowed_users` and `dmsgroup`, use gNMI Get/Set/Subscribe, run supported gNOI workflows, and debug frontend/backend failures. Trigger even without "DMS" for "manage a remote BlueField over gRPC", "gNOI reboot from orchestrator", or fleet-management requests. SAFETY: reboot, OS install, factory-reset, and managed-file deletion are destructive and require target-bound explicit confirmation; never invoke them speculatively. Route installation and library/API build questions elsewhere, and route turnkey aggregation to the externally-productized DOCA Telemetry Service.
What it needs
About 6k tokens when loaded.
What this skill does
DOCA Management Service (DMS) ⚠️ Destructive operations. The gNOI reboot, OS install, factory-reset, and managed-file deletion operations are irreversible and service-impacting — they can take a production BlueField or ConnectX offline or wipe its configuration. Before issuing any of them the agent MUST: (1) verify the target device identity, and (2) obtain explicit confirmation bound to that target and action. In an interactive session this is an explicit user reply naming/accepting both; in unattended execution it must be an approved-system authorization artifact bound to both. Otherwise stop with confirmationrequired. Never invoke them speculatively or as a side effect of another task. See the public DMS guide's safety guidance for these operations. Where to start: This skill is for operating DMS, not for linking against a library. If the user wants to deploy or run the daemon, open TASKS.md and start at configure. If the question is what shape of service is DMS and what protocols does it speak, start at CAPABILITIES.md. If DOCA is not installed on the management endpoint yet, route to doca-setup first. Example questions this skill answers well The CLASSES of DMS questions this skill is built to answer, each with one worked example. The class is the load-bearing piece; the worked example is one instance. "Where should DMS run for my target topology?" — worked example: "I have a host without a DPU; can I still manage a remote ConnectX?". Answered by the deployment-shape decision in CAPABILITIES.md ## Capabilities and modes TASKS.md ## configure. "Which authentication mode should I pick for my security posture?" — worked example: "a multi-tenant production env vs a single-tenant lab". Answered by the auth-mode trade-off table in CAPABILITIES.md ## Safety policy the auth-wiring step in TASKS.md ## configure. "How do I issue a gNMI Get / Set against a modeled path?" — worked example: "set /interfaces/interface/config/mtu on a remote interface". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/doca-dms