SKILLEMALL.ai
GitHub ↗ RU Sign in

AF doca-upgrade

Use this skill when the user is contemplating a DOCA upgrade or downgrade — moving a host to a newer DOCA release, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back. The discipline is detect → report → ASK → only-then guided upgrade: detect what is installed, discover what newer release exists, report the gap, then STOP and ask for explicit confirmation — never upgrade automatically. Trigger even without the word "upgrade": "is there a newer DOCA", "should I move to the next release", "I want the latest features", "my component is being deprecated, what now", or "roll me back". Route elsewhere for version detection (doca-version), first-time install (doca-setup), any hardware/firmware/reboot step (doca-hardware-safety), and public-docs / sunset routing (doca-public-knowledge-map).

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

Use this skill when the user is contemplating a DOCA upgrade or downgrade — moving a host to a newer DOCA release, refreshing the BlueField BFB, bumping the…

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

AnalyzerData and analyticsAI and agentstype 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
44/100
Will not run
References files that are not bundled: TASKS.md, CAPABILITIES.md, ../doca-hardware-safety/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-hardware-safety/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-version/SKILL.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: 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-version/TASKS.md
  • warning missing-ref reference to a missing file: CAPABILITIES.md
  • warning missing-ref reference to a missing file: ../doca-version/TASKS.md
  • warning missing-ref reference to a missing file: ../doca-version/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-debug/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-programming-guide/SKILL.md
  • warning missing-ref reference to a missing file: ../doca-structured-tools-contract/SKILL.md

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: TASKS.md, CAPABILITIES.md, ../doca-hardware-safety/SKILL.md
  • 0Tools and files. 19 referenced file(s) missing: TASKS.md, CAPABILITIES.md, ../doca-hardware-safety/SKILL.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. 1 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
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3042 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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 823: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 6 example trigger phrases
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (0 code blocks)
  • +1License stated

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