SKILLEMALL.ai

AF doca-version

Use this skill when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common, applications/VERSION, doca_caps --version, and bfver/mlnx-release on BlueField, reasoning about NGC container tags, looking up whether a capability is on the installed release, or diagnosing build-vs-runtime drift. Trigger even when the user does not explicitly say "DOCA version" or "four-way match" — typical implicit phrasings include "program built but does nothing on the wire", "undefined reference to a symbol the docs claim exists", "DOCA_ERROR_NOT_SUPPORTED at runtime", "counter didn't increment", "what does `latest` mean for this tag", or "is my LTS still supported". Refuse and route elsewhere for installing or choosing DOCA packages (doca-setup), per-library API/capability questions (matching library skill), the cross-library DOCA_ERROR_* taxonomy (doca-programming-guide), or the general debug ladder (doca-debug) — those belong to other skills.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 2 692 tokens Open the sourceclawhub.ai analyzed 2 d ago

Use this skill when the user is doing DOCA version handling — detecting the installed release, validating the four-way match across pkg-config doca-common…

As a process F 52/100 · Will not run — References files that are not bundled: TASKS.md, CAPABILITIES.md, TASKS.md

IntegrationSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
F
52/100
Will not run
References files that are not bundled: TASKS.md, CAPABILITIES.md, TASKS.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: ../doca-structured-tools-contract/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-public-knowledge-map/SKILL.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: ../../AGENTS.md
  • warning missing-ref reference to a missing file: ../doca-setup/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-hardware-safety/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-container-deployment/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-bare-metal-deployment/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-structured-tools-contract/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-programming-guide/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-debug/SKILL.md

Process rating: all ten parameters 52/100

Will not run. References files that are not bundled: TASKS.md, CAPABILITIES.md, TASKS.md
  • 0Tools and files. 20 referenced file(s) missing: TASKS.md, CAPABILITIES.md, TASKS.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. 5 mutating operations with no state check
  • 100Steps. 23 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2692 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 1019: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 23 items
  • +4Has examples (0 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.