SKILLEMALL.ai
GitHub ↗ RU Sign in

AF doca-telemetry

Use this skill to read DOCA hardware-counter events from a `doca_dev` through the per-domain Telemetry reader libraries: `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, and `_pci`. It covers capability checks, context creation, startup, and per-domain reads or samples. Trigger for implicit requests such as "read PCC counters from my BlueField app", "sample DPA counter exports", or "expose PHY, PCI, or DIAG counters from this doca_dev". This is the counter-reader surface, not a NetFlow, IPFIX, or local-socket collector. Route publishing and export to `doca-telemetry-exporter`; route deployed DOCA Telemetry Service (DTS), collectors, and plain stdout logging elsewhere.

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

Use this skill to read DOCA hardware-counter events from a docadev through the per-domain Telemetry reader libraries: docatelemetrypcc, dpa, diag, adpretx…

As a process F 45/100 · Will not run — References files that are not bundled: TASKS.md, CAPABILITIES.md, ../../doca-setup/SKILL.md

ProcedureInfrastructureMarketingtype 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
45/100
Will not run
References files that are not bundled: TASKS.md, CAPABILITIES.md, ../../doca-setup/SKILL.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: ../../doca-setup/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-telemetry-exporter/SKILL.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: ../../doca-public-knowledge-map/SKILL.md
  • warning missing-ref reference to a missing file: TASKS.md
  • warning missing-ref reference to a missing file: ../../doca-version/SKILL.md
  • warning missing-ref reference to a missing file: references/details.md
  • warning missing-ref reference to a missing file: references/details.md
  • warning missing-ref reference to a missing file: references/details.md
  • warning missing-ref reference to a missing file: references/details.md

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: TASKS.md, CAPABILITIES.md, ../../doca-setup/SKILL.md
  • 0Tools and files. 12 referenced file(s) missing: TASKS.md, CAPABILITIES.md, ../../doca-setup/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 7 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 70Failures and branches. 4 branches
  • 100Steps. 11 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2498 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (6 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

  • +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
  • +5Description quotes 3 example trigger phrases
  • +3Description length 687: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (0 code blocks)
  • +1License stated

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