AF doca-programming-guide
Use this skill when the user is writing their first DOCA app or asking a library-agnostic programming question — picking a shipped sample to copy and modify, wiring the canonical pkg-config doca-{library} + meson build (or FFI from Rust / Go / Python against the public C ABI), walking the cfg-create → init → start → use → stop → destroy lifecycle, validating a spec before commit, or decoding a DOCA_ERROR_* return with doca_error_get_descr(). Trigger even when the user does not say "DOCA programming guide" — implicit phrasings: "write my first DOCA program", "meson line for doca_rdma_*", "got DOCA_ERROR_BAD_STATE on my first call", "call DOCA from Rust without writing C", "built clean but nothing on the wire", "what order do doca_*_pipe calls go in". Refuse and route for install / hugepages / pkg-config not resolving doca-{library} (doca-setup), docs or version lookup (doca-public-knowledge-map), and library-internal API construction like Flow pipe topology or RDMA QP setup (matching library skill).
Use this skill when the user is writing their first DOCA app or asking a library-agnostic programming question — picking a shipped sample to copy and modify…
As a process F 49/100 · Will not run — References files that are not bundled: TASKS.md, TASKS.md, CAPABILITIES.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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- 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: CAPABILITIES.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: ../doca-setup/SKILL.md - warning
missing-refreference to a missing file: ../doca-public-knowledge-map/SKILL.md - warning
missing-refreference to a missing file: ../libs/doca-flow/SKILL.md - warning
missing-refreference to a missing file: CAPABILITIES.md - warning
missing-refreference to a missing file: TASKS.md
Process rating: all ten parameters 49/100
- 0Tools and files. 12 referenced file(s) missing: TASKS.md, TASKS.md, CAPABILITIES.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Steps. 29 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3083 tokens
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 1013: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Structure: 8 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (0 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.