SKILLEMALL.ai
GitHub ↗ RU Sign in

AF doca-caps

Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for a debug session or install smoke-test. Trigger even when the user does not explicitly mention "doca_caps" or "capabilities print tool" — typical implicit phrasings include "what does DOCA actually see on this box", "is my BlueField PF visible to DOCA", "is Flow available on my RHEL host", "enumerate VF representors for pf0", "doca_caps: command not found", or "empty output for RDMA, is the tool broken". Refuse and route elsewhere for DOCA installation, library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary — those belong to other skills.

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

Use this skill when the user wants to invoke the read-only docacaps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing…

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

IntegrationSoftware developmentMarketingtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
F
55/100
Will not run
References files that are not bundled: TASKS.md, TASKS.md, TASKS.md
Tools and files w 18
0
Failures and branches w 10
0
Progress reporting w 2
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: TASKS.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: ../../doca-setup/SKILL.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: ../../doca-debug/TASKS.md
  • warning missing-ref reference to a missing file: ../../doca-programming-guide/TASKS.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: ../../doca-setup/TASKS.md
  • warning missing-ref reference to a missing file: ../../doca-setup/TASKS.md
  • warning missing-ref reference to a missing file: ../../doca-public-knowledge-map/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-programming-guide/SKILL.md

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: TASKS.md, TASKS.md, TASKS.md
  • 0Tools and files. 14 referenced file(s) missing: TASKS.md, TASKS.md, TASKS.md
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 31 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2059 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
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 31 items
  • +3Output format is stated explicitly
  • +4Has examples (0 code blocks)
  • +1License stated

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