Agent skill · nvidia
doca-pipeline-language-developer-tools
Use this skill when the operator is driving the DOCA Pipeline Language (DPL) Developer Tools to inspect or debug DPL programs on a BlueField DPU — DPL Nspect for runtime state such as tables, keys, and counters, DPL Debugger for packet flow, DPL Admin for dynamic configuration changes in the DPL Runtime Daemon, P4 Runtime Shell as a P4Runtime control plane manager, or DPL Runtime Controller SDK for custom P4Runtime applications and DPL shared memory APIs. Trigger even when the user does not explicitly mention "DPL Developer Tools" — implicit phrasings include "inspect the DPL tables on the DPU", "why can't I start a DPL debug session", "change a dpl_rtd configuration item without restarting", "build my own P4Runtime app for DPL", or "visualize packet flow through my DPL program". Refuse and route elsewhere: authoring, compiling and deploying DPL programs to the DOCA Pipeline Language Service Guide, DOCA install/bring-up to doca-setup, and hardware or firmware state changes to doca-hardware-safety.
What it needs
About 9k tokens when loaded.
What this skill does
DOCA Pipeline Language Developer Tools Scope boundaries These requests are out of scope: say so, name the skill that owns the request, and stop. installing DOCA and bringing up the DPL Runtime Service container: doca-setup/SKILL.md. Name doca-setup in the answer and route the whole install/bring-up there; do not walk the install steps from this skill or from the DPL Installation Guide. DPU mode or firmware state changes: doca-hardware-safety/SKILL.md. which DOCA version is installed, version compatibility: doca-version/SKILL.md. authoring, compiling and deploying DPL programs (DOCA Pipeline Language Service Guide): doca-public-knowledge-map/SKILL.md. Examples "How do I inspect the DPL runtime tables on the DPU?" — this is in scope. Use DPL Nspect; do not author or compile DPL programs here. "I want to visualize packet flow through my DPL program." — this is in scope. Use DPL Debugger; ensure the program was compiled with the debug flag -g and loaded into dplrtd using the P4Runtime controller. "How do I dynamically change a configuration item in dplrtd?" — this is in scope. Use DPL Admin; inspect current state first. "Can I build a custom P4Runtime application for DPL?" — this is in scope. Use the DPL Runtime Controller SDK. "My DPL program is loaded but I cannot start a debug session." — check the debug-flag prerequisite and the P4Runtime load path before assuming the tool is broken. Quick facts The authoritative source for the tool names, flags, and paths is the public DOCA Pipeline Language Developer Tools guide for your release; confirm them with the installed tool's help before quoting any of them. As that guide describes it: The developer tools are a suite for validating and debugging DPL applications: DPL Compiler, P4 Runtime Shell, DPL Nspect, DPL Debugger, DPL Admin, and DPL Runtime Controller SDK. All tools interact with the DPL Runtime Daemon (dplrtd) running on the BlueField DPU. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/doca-pipeline-language-developer-tools