SKILLEMALL.ai
GitHub ↗ RU Sign in

AF doca-telemetry-utils

Use this skill when the user is invoking `doca_telemetry_utils` on a host with DOCA installed — discovering the diagnostic-counter schema, translating counter names to binary Data IDs, validating per-device counter support before committing a DOCA Telemetry exporter config, or reverse-resolving a captured Data ID. Trigger even when the user does not explicitly mention "doca_telemetry_utils" or "Data ID" — typical implicit phrasings include "my exporter ships but the collector sees nothing", "this metric silently drops downstream", "which counters does this BlueField expose", "translate this 0x... back to a counter name", "what do node / pcie_index / depth mean here", or "is this counter supported on this device before I commit it". Refuse and route elsewhere for developer-side collector / exporter library programming, DTS deployment, or DOCA install / repair — those belong to doca-telemetry, doca-public-knowledge-map, and doca-setup.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 3 884 tokens Open the sourceclawhub.ai↗ analyzed 26 h ago

Use this skill when the user is invoking docatelemetryutils on a host with DOCA installed — discovering the diagnostic-counter schema, translating counter…

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

AnalyzerWriting and documentsInfrastructureData and analyticstype 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
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
F
53/100
Will not run
References files that are not bundled: TASKS.md, TASKS.md, TASKS.md
Tools and files w 18
0
Result and completion w 14
0
Running it twice w 4
30
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: ../../libs/doca-telemetry/SKILL.md
  • warning missing-ref reference to a missing file: ../../libs/doca-telemetry/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: CAPABILITIES.md
  • warning missing-ref reference to a missing file: ../../doca-version/SKILL.md
  • warning missing-ref reference to a missing file: ../../libs/doca-telemetry-exporter/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-setup/SKILL.md
  • warning missing-ref reference to a missing file: ../../doca-debug/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

Process rating: all ten parameters 53/100

Will not run. References files that are not bundled: TASKS.md, TASKS.md, TASKS.md
  • 0Tools and files. 17 referenced file(s) missing: TASKS.md, TASKS.md, TASKS.md
  • 0Result and completion. Does not say what the result is
  • 30Running it twice. 16 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. 37 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3884 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (5 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)
  • +3Description length 947: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 37 items
  • +4Has examples (0 code blocks)
  • +1License stated

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