AF 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.
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…
As a process F 54/100 · Will not run — References files that are not bundled: ../doca-setup/TASKS.md, ../doca-programming-guide/TASKS.md, TASKS.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../doca-setup/TASKS.md - warning
missing-refreference to a missing file: ../doca-programming-guide/TASKS.md - warning
missing-refreference to a missing file: TASKS.md - warning
missing-refreference to a missing file: CAPABILITIES.md - warning
missing-refreference to a missing file: TASKS.md - warning
missing-refreference to a missing file: TASKS.md - warning
missing-refreference to a missing file: CAPABILITIES.md - warning
missing-refreference to a missing file: ../tools/doca-caps/SKILL.md - warning
missing-refreference to a missing file: CAPABILITIES.md - warning
missing-refreference to a missing file: ../doca-public-knowledge-map/SKILL.md - warning
missing-refreference to a missing file: ../doca-programming-guide/CAPABILITIES.md - warning
missing-refreference to a missing file: ../libs/doca-flow/TASKS.md - warning
missing-refreference to a missing file: CAPABILITIES.md - warning
missing-refreference to a missing file: TASKS.md - warning
missing-refreference to a missing file: ../doca-programming-guide/SKILL.md - warning
missing-refreference to a missing file: ../doca-setup/SKILL.md - warning
missing-refreference to a missing file: ../libs/doca-flow/SKILL.md - warning
missing-refreference to a missing file: ../services/doca-dms/SKILL.md
Process rating: all ten parameters 54/100
- 0Tools and files. 18 referenced file(s) missing: ../doca-setup/TASKS.md, ../doca-programming-guide/TASKS.md, TASKS.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2207 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1016: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Structure: 6 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (0 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.