SKILLEMALL.ai
GitHub ↗ RU Sign in

BF tao-run-on-docker

Docker conventions for running NVIDIA GPU container workloads — NGC authentication, --gpus flag, mount patterns, env-var passthrough, container inspection, data-root relocation for split-disk hosts, and common error modes. Use when another skill requires running an nvcr.io container or any docker run command on a GPU host. Trigger keywords — docker, docker run, nvcr.io, NGC, --gpus, nvidia-container-toolkit, container image, docker login, docker pull.

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

Docker conventions for running NVIDIA GPU container workloads — NGC authentication, --gpus flag, mount patterns, env-var passthrough, container inspection…

As a process F 48/100 · Will not run — References files that are not bundled: references/skill_info.yaml

ReferenceDockerInfrastructuretype 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
B
79/100
safety, quality, tests
Safety 60%
79
Quality 40%
79
Run on models
none yet
Process rating
F
48/100
Will not run
References files that are not bundled: references/skill_info.yaml
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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

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 · 5

✓ No critical or high findings

Medium and low: 5
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Bash
  • medium Dangerous commands cmd-privilege SKILL.md:255
    Privilege escalation / world-writable permissions
    sudo mv /var/lib/docker /var/lib/docker.old
  • medium Dangerous commands cmd-privilege SKILL.md:257
    Privilege escalation / world-writable permissions
    sudo tee /etc/docker/daemon.json <<'EOF'
  • medium Dangerous commands cmd-privilege SKILL.md:263
    Privilege escalation / world-writable permissions
    sudo rm -rf /var/lib/docker.old
  • low Dangerous commands cmd-privilege SKILL.md:198
    Privilege escalation / world-writable permissions (quoted — discussed, not commanded)
    exception. Never substitute `chmod 777` as the normal fix.
    quoted

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: references/skill_info.yaml

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: references/skill_info.yaml
  • 0Tools and files. 1 referenced file(s) missing: references/skill_info.yaml
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 18 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3668 tokens
  • 100Running it twice. Mutating operations check current state
  • low 15 top-level sections: this looks like several domains in one skill
  • 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

  • +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 455: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 18 items
  • +4Has examples (14 code blocks)
  • +1License stated

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