DD mail-mate
(no description)
As a process D 41/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 · 10
-
high Dangerous commands
cmd-persistencesetup_cron.sh:76Persistence mechanism (cron / launchd / scheduled task / autorun registry)( crontab -l 2>/dev/null || true ) | grep -v -F "$TAG" > "$TMP" || true
Medium and low: 9
-
medium Dangerous commands
cmd-persistenceREADME.md:239Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l | grep -v imap-mail-pipeline | crontab - # 移除本 Skill 的任务
detector -
low Exfiltration
exfil-webhook-urlpusher.py:114Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)webhook_url 格式:https://api.telegram.org/bot<TOKEN>/sendMessage
placeholder -
low Exfiltration
exfil-webhook-urlREADME.md:179Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)| Telegram | `tg` | `https://api.telegram.org/bot<TOKEN>/sendMessage` | 目标 `chat_id` |
placeholder -
low Exfiltration
read-dotenvREADME.md:214Reads a .env file (detector / deny-list definition)- cron 触发时自动 `source .env`,再执行 `python3 main.py`,stdout/stderr 追加到指定日志文件。
detector -
low Dangerous commands
cmd-cron-mentionREADME.md:238Mentions editing / listing crontabcrontab -l # 查看所有任务
-
low Dangerous commands
cmd-cron-mentionREADME.md:239Mentions editing / listing crontabcrontab -l | grep -v imap-mail-pipeline | crontab - # 移除本 Skill 的任务
-
low Dangerous commands
cmd-cron-mentionsetup_cron.sh:76Mentions editing / listing crontab( crontab -l 2>/dev/null || true ) | grep -v -F "$TAG" > "$TMP" || true
-
low Dangerous commands
cmd-cron-mentionsetup_cron.sh:84Mentions editing / listing crontab (string literal in code, not executed)echo "可用 'crontab -l' 查看,用 'crontab -e' 手动编辑。"
code literal -
low Exfiltration
exfil-webhook-urlskill.md:194Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)| Telegram | `tg` | `https://api.telegram.org/bot<TOKEN>/sendMessage` | 目标 `chat_id` |
placeholder
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 41/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
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2220 tokens
- low 13 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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -217 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 24 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.