DD china-install-skills
China Install Skills - ClawHub skill installer for mainland China users, bypasses API rate limits via direct Convex API access
China Install Skills - ClawHub skill installer for mainland China users, bypasses API rate limits via direct Convex API access
As a process D 46/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.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 12
-
high Dangerous commands
cmd-persistencescripts/setup-cron.sh:39Persistence mechanism (cron / launchd / scheduled task / autorun registry)EXISTING_CRON=$(crontab -l 2>/dev/null | grep -F "$AUTO_UPDATE_SCRIPT" || true)
-
high Dangerous commands
cmd-persistencescripts/setup-cron.sh:58Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null | grep -v -F "$AUTO_UPDATE_SCRIPT"; echo "$CRON_JOB") | crontab - 2>/dev/null
Medium and low: 10
-
medium Dangerous commands
cmd-persistencescripts/setup-cron.sh:16Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v -F "$AUTO_UPDATE_SCRIPT" | crontab - 2>/dev/null || true
detector -
medium Dangerous commands
cmd-persistencescripts/setup-cron.sh:53Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v -F "$AUTO_UPDATE_SCRIPT" | crontab - 2>/dev/null || true
detector -
low Dangerous commands
cmd-cron-mentionREADME.md:88Mentions editing / listing crontabcrontab -l
-
low Dangerous commands
cmd-cron-mentionREADME.md:97Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionscripts/setup-cron.sh:16Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v -F "$AUTO_UPDATE_SCRIPT" | crontab - 2>/dev/null || true
-
low Dangerous commands
cmd-cron-mentionscripts/setup-cron.sh:39Mentions editing / listing crontabEXISTING_CRON=$(crontab -l 2>/dev/null | grep -F "$AUTO_UPDATE_SCRIPT" || true)
-
low Dangerous commands
cmd-cron-mentionscripts/setup-cron.sh:53Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v -F "$AUTO_UPDATE_SCRIPT" | crontab - 2>/dev/null || true
-
low Dangerous commands
cmd-cron-mentionscripts/setup-cron.sh:58Mentions editing / listing crontab(crontab -l 2>/dev/null | grep -v -F "$AUTO_UPDATE_SCRIPT"; echo "$CRON_JOB") | crontab - 2>/dev/null
-
low Dangerous commands
cmd-cron-mentionscripts/setup-cron.sh:69Mentions editing / listing crontab (string literal in code, not executed)echo " crontab -l"
code literal -
low Dangerous commands
cmd-cron-mentionSKILL.md:263Mentions editing / listing crontabcrontab -e
Files scanned: 15. 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 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1184 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -31 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 126: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.