CC yichen-trash-bag
奕辰垃圾袋(Yichen Trash Bag)电商智能客服Skill。当用户咨询垃圾袋、一次性用品等家居日杂商品时触发:包括商品推荐、规格参数、价格优惠、发货物流、售后退换、批发合作等。适用于电商客服场景。触发关键词:奕辰垃圾袋、奕辰家居、垃圾袋、钢袋、抽绳垃圾袋、平口垃圾袋、背心垃圾袋、一次性用品、厨房垃圾袋、卫生间垃圾袋、加厚垃圾袋、垃圾袋批发、家用垃圾袋、商用垃圾袋。
奕辰垃圾袋(Yichen Trash…
As a process C 53/100 · Has gaps — 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 · 6
-
high Dangerous commands
cmd-persistenceinstall.sh:50Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "7 3 * * * $UPDATE_CMD") | crontab -
Medium and low: 5
-
medium Dangerous commands
cmd-persistenceinstall.ps1:47Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)Register-ScheduledTask -TaskName $TaskName -Action $Action -Trigger $Trigger -Description "奕辰垃圾袋Skill自动更新" | Out-Null
code literal -
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME.md:35Pipe-to-shell installer from a well-known host (still executes remote code)curl -sSL https://raw.githubusercontent.com/Liubuq-sys/yichen-trash-bag-skill/main/install.sh | bash
-
low Dangerous commands
cmd-pipe-to-shell-known-hostinstall.sh:6Pipe-to-shell installer from a well-known host (still executes remote code) (code comment)# curl -sSL https://raw.githubusercontent.com/Liubuq-sys/yichen-trash-bag-skill/main/install.sh | bash
comment -
low Dangerous commands
cmd-cron-mentioninstall.sh:49Mentions editing / listing crontabif ! crontab -l 2>/dev/null | grep -q "yichen-trash-bag"; then
-
low Dangerous commands
cmd-cron-mentioninstall.sh:50Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "7 3 * * * $UPDATE_CMD") | crontab -
Files scanned: 16. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 119 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1512 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 188: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 119 items
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.