Agent skill · NVIDIA
doca-debug
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca_* symbol, a runtime call returning DOCA_ERROR_*, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime → program → driver), verbosity controls (--sdk-log-level, DOCA_LOG_LEVEL, the doca-{lib}-trace flavor), container-debug constraints, or how to capture state for a Developer Forum post. Trigger even when the user does not say "DOCA debug" — implicit phrasings include "undefined reference to doca_*", "how do I get more logs", "packets aren't reaching the wire", "doca_caps returned nothing", or "hugepages empty in the container". Refuse and route elsewhere for library-specific debug (Flow pipe trace, RDMA QP, Comch stats), env-class pkg-config or hugepages symptoms, the DOCA_ERROR_* taxonomy and lifecycle interpretation, and performance or incident-response work — those belong to other skills.
What it needs
About 5k tokens when loaded.
What this skill does
DOCA debug Where to start: This skill is the canonical layered-ladder reference both doca-setup ## debug and doca-programming-guide ## debug escalate to. If the symptom does not fit cleanly in env-class or program-class, start at TASKS.md ## debug — the full layered ladder lives there. Example questions this skill answers well The CLASSES of debug questions this skill is built to answer, each with one worked example. "My DOCA build / link / runtime / program failed — which layer is it?" — worked example: "ld says undefined reference to docaflowinit — which layer?" Answered by the canonical layered ladder in TASKS.md ## debug (layer 4 = Link). "How do I turn up verbosity for any DOCA library or tool?" — worked example: "My DOCA Flow program is silent — where do I get more log output?" Answered by the trace-flavor / log-level surface in CAPABILITIES.md ## Observability the run-with-verbosity workflow in TASKS.md ## run. "How do I capture state for a forum question or bug report?" — worked example: "I'd like to file a forum question with reproducible context — what should I include?" Answered by the capture-a-reproducible-state workflow in TASKS.md ## test. "What does this DOCA tool's output mean / which tool answers this?" — worked example: "docacaps returned nothing for RDMA — does that mean unsupported?" Answered by the tool-vs-capability decision tree in CAPABILITIES.md ## Capabilities and modes cross-link to doca-caps. "I'm debugging inside the NGC container — what's observable?" — worked example: "hugepages is empty inside the container; is that a real problem or a container thing?" Answered by the container-specific debug constraints in CAPABILITIES.md ## Safety policy TASKS.md ## debug layer 5 (Runtime). "Where do I ask for help with this?" — worked example: "Where is the customer-facing DOCA forum and what should the post contain?" Answered by the Developer-Forum routing rule in TASKS.md ## debug plus doca-public-knowledge-map. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/doca-debug