Agent skill · software engineering · nvidia
doca-dms
Operate NVIDIA DOCA Management Service on a BlueField, Arm/x86 host, or Kubernetes pod: from DOCA 3.5 the local `dms-cli` (one command per YANG path, no server), and the `dmsd` + `dmspe` service: choose deployment and authentication, configure `-allowed_users` and `dmsgroup`, use gNMI Get/Set, 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 telemetry streaming and aggregation to doca-dts (DOCA Telemetry Service).
Why this skill is useful
Provides specific commands and workflows for managing NVIDIA DOCA services that the AI wouldn't reliably generate on its own.
What it needs
Requires doca installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
DOCA Management Service (DMS) Examples "Read or change a BlueField setting locally." — use dms-cli (DOCA 3.5+); explore the path with --tree first. "Manage a remote BlueField over gRPC." — this is in scope. Use dmsd + dmspe with the chosen auth; do not drop to ad-hoc SSH for the management plane. "gNOI reboot from orchestrator." — treat reboot / OS install / factory-reset as destructive: require target-bound explicit confirmation first. Instructions Follow Loading order below. Open the tasks companion for configure / gNMI / debug. Open the capabilities companion for auth and gNOI scope. Do not open every companion file. ⚠️ 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 the tasks companion and start at configure. If the question is what shape of service is DMS and what protocols does it speak, start at the capabilities companion. If DOCA is not installed on the management endpoint yet, route to doca-setup/SKILL.md first. How to use this skill. Read this file, then search the companion file for the ## <name> heading the question needs and read that whole section. Answer completely from it, quoting only its symbols and commands. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-dms