SKILLEMALL.ai
GitHub ↗ RU Sign in

CC doca-flow

Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA packet steering, classifier, representor, rule-matching, hairpin, or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Route plain DPDK `rte_flow`, kernel TC, OVS, BFB bring-up, and DPU OS installation elsewhere. DPU OS installation is destructive and always requires explicit confirmation.

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

Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets…

As a process C 51/100 · Has gaps — References files that are not bundled: TASKS.md, TASKS.md, CAPABILITIES.md

GeneratorSoftware developmenttype 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
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
C
51/100
Has gaps
References files that are not bundled: TASKS.md, TASKS.md, CAPABILITIES.md
Tools and files w 18
0
Result and completion w 14
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: 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: ../../doca-setup/SKILL.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: 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: 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: ../../doca-public-knowledge-map/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-programming-guide/SKILL.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: ../../tools/doca-flow-tune/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-hardware-safety/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-debug/SKILL.md

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: TASKS.md, TASKS.md, CAPABILITIES.md
  • 0Tools and files. 20 referenced file(s) missing: TASKS.md, TASKS.md, CAPABILITIES.md
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 7 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 33 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3171 tokens
  • low 11 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 621: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 33 items
  • +4Has examples (2 code blocks)
  • +1License stated

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