AC emailbox
职业邮箱收发与数据处理一体化工具。IMAP/SMTP protocol for 12+ providers (Gmail/Outlook/QQ/163/Yahoo/iCloud etc). Send/receive/search/schedule emails, HTML templates, attachments, forwarding, data integration. 邮件收发、搜索、定时发送、附件、HTML模板、转发、文档数据联动。
As a process C 50/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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
✓ No critical or high findings
Medium and low: 4
-
low Dangerous commands
cmd-cron-mentionscripts/schedule_mail.py:81Mentions editing / listing crontab (string literal in code, not executed)f" crontab -l > ~/crontab_backup.txt\n"
code literal -
low Dangerous commands
cmd-cron-mentionscripts/schedule_mail.py:82Mentions editing / listing crontab (string literal in code, not executed)f" crontab -e\n"
code literal -
low Dangerous commands
cmd-cron-mentionscripts/schedule_mail.py:369Mentions editing / listing crontab (string literal in code, not executed)print(f" If you added a crontab entry for this schedule, remove it manually with: crontab -e")
code literal -
low Dangerous commands
cmd-cron-mentionSKILL.md:363Mentions editing / listing crontabcrontab -l > ~/crontab_backup.txt
Files scanned: 9. 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 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 15 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3365 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 224: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (23 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.
External checks
ClawHub: suspicious
This email skill appears purpose-built, but it handles powerful mailbox credentials and keeps scheduled email content on disk in ways users should review carefully.
LLM: suspicious (high) · VirusTotal: · 9 Jul 2026