doca-debug SKILL.md skillA
doca-debug from nvidia/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nvidia/skills/doca-debug@git:20261028.3d06e7ePins git:20261028.3d06e7e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nvidia/skills
- Path
skills/doca-debug/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261028.3d06e7e, committed Oct 28, 2026
- First version recorded
- Jul 17, 2026
- Size
- 12,755 bytes
- Repository stars
- 3,871
- License
- Apache-2.0
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# DOCA debug ## Examples - **"My DOCA build / link / runtime failed — which layer is it?"** — this is in scope. Walk the layered ladder; do not jump to library-internal debug first. - **"How do I turn up verbosity for any DOCA library or tool?"** — use the log-level / trace-flavor surface, then capture state for a forum post. ## Instructions An `undefined reference` is a **Link-layer symptom**, not proof of a missing library or an application-code defect. Before recommending edits, request these observations from the **same host/container and shell that ran the failing build**: - `pkg-config --modversion doca-common` and the selected library's version; for Flow, `pkg-config --modversion doca-flow`. - `pkg-config --libs doca-<library>`; for Flow, `pkg-config --libs doca-flow`. - The actual failing compiler/linker invocation from the build log and its full error output. `pkg-config` reports flags, not the command that failed. **If these outputs are missing, request them and pause before prescribing a repair.** Listing a check is not evidence that it passed. Do not append a speculative fix, guessed `-L`/`-l` flags, predicted library filenames, or a …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/doca-debug@sha256:f385f57aa5a7023cThe line at the top of this page pins the label git:20261028.3d06e7e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jb5r3v4vbw7stw5q)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 17, 2026 and Oct 28, 2026, about one every 34 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.3d06e7e latest | 2026-10-28 | 3d06e7e | 12,755 B | A | view · diff |
| git:20261022.a4cf47e | 2026-10-22 | a4cf47e | 12,776 B | A | view · diff |
| git:20261014.bbb601a | 2026-10-14 | bbb601a | 13,339 B | A | view · diff |
| git:20260717.f64fa0e | 2026-07-17 | f64fa0e | 10,238 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12755 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nvidia/skills · 3,871 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jb5r3v4vbw7stw5q GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/doca-debug GET https://markdownregistry.com/api/v1/blob/f385f57aa5a7023c6c5dea21837f0a16754f578d3b8a1ed5b9c90c75137229cb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.