DD openclaw-sentinel
(no description)
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Add a description to the frontmatter: without it the skill never triggers.
- 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
-
high Dangerous commands
cmd-encoded-execREADME.md:48Executes a base64/encoded payload (documentation of a security skill)- **Encoded Execution** — eval(base…ode(...)), exec(compile(...)), eval/exec with encoded strings
security skill -
high Dangerous commands
cmd-encoded-execSKILL.md:73Executes a base64/encoded payload (documentation of a security skill)| **Encoded Execution** | eval(base…ode(...)), exec(compile(...)), eval/exec with encoded strings |
security skill
Medium and low: 3
-
low Dangerous commands
cmd-eval-dynamicREADME.md:48Dynamic code execution from decoded/untrusted input (documentation of a security skill)- **Encoded Execution** — eval(base…ode(...)), exec(compile(...)), eval/exec with encoded strings
security skill -
low Dangerous commands
cmd-eval-dynamicSKILL.md:73Dynamic code execution from decoded/untrusted input (documentation of a security skill)| **Encoded Execution** | eval(base…ode(...)), exec(compile(...)), eval/exec with encoded strings |
security skill
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1029 tokens
- 100Running it twice. No mutating operations
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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (7 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 39.