BC openclaw-docker
Manage Docker containers and Compose projects via OpenClaw tools
Manage Docker containers and Compose projects via OpenClaw tools
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:284High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…ywo+qwL+oL8H…C1U+vRfLQDvw==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:300High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-Yqfm+XDx0+Prh3…1yC+JWZ2…IL7+vK+Clp7…D7g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:313High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…xZl+RoGR…fbT/ZgrF…0EA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:326High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…3bJ+V0If…IXN+CL65…a4w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:342High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…H47+FFon…OsV/4+RRsz…0ig==",
quoted
Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 739 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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)
- +3Description length 64: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.