CB market-watch
Market monitoring and alert system for prices and news. Use when the user asks to watch a price, monitor market conditions, get notified when an asset hits a target, or keep an eye on breaking news. Covers any USDT-paired crypto and A-shares (real-time via TongDaXin).
As a process B 66/100 · Nearly there — weak spots: result and completion, 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.
- 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 · 4
-
high Dangerous commands
cmd-persistencescripts/install-watchdog.sh:62Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load "$PLIST"
Medium and low: 3
-
medium Dangerous commands
cmd-persistenceREADME_zh.md:327Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation table row)| 看门狗配置 | `~/Library/LaunchAgents/com.openclaw.market-watch.{agent}.plist` | macOS launchd 配置 |table -
medium Dangerous commands
cmd-persistenceREADME.md:301Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation table row)| Watchdog plist | `~/Library/LaunchAgents/com.openclaw.market-watch.{agent}.plist` | macOS launchd config |table -
medium Dangerous commands
cmd-persistencescripts/install-watchdog.sh:30Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PLIST="$HOME/Library/LaunchAgents/${LABEL}.plist"code literal
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "repository"
Process rating: all ten parameters 66/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1614 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -34 of 8 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 268: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.