CC email-daily-summary
基于 browser-。支持自动化配置和灵活的参数设置,适适用于不同工作场景,改善操作效率。邮件摘要工具。支持自动化配置和灵活的参数设置,适用于多种工作场景,提升工作效率和准确性。基于。Use when 需要提升效率、自动化流程、批量处理、工作流优化时使用。不适用于需要人工创意判断的任务。适用于独立开发者、企业团队和自动化工作流场景。
基于 browser-。支持自动化配置和灵活的参数设置,适适用于不同工作场景,改善操作效率。邮件摘要工具。支持自动化配置和灵活的参数设置,适用于多种工作场景,提升工作效率和准确性。基于。Use when…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
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.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 · 3
-
high Dangerous commands
cmd-persistenceSKILL.md:279Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load $HOME/Library/LaunchAgents/com.email.dailysummary.plist
Medium and low: 2
-
medium Dangerous commands
cmd-persistenceSKILL.md:276Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)创建 `$HOME/Library/LaunchAgents/com.email.dailysummary.plist`,设置 `StartCalendarInterval` 为 Hour=9, Minute=0,ProgramArguments 指向脚本路径,然后:
quoted -
low Dangerous commands
cmd-cron-mentionSKILL.md:269Mentions editing / listing crontabcrontab -e
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Map keys must be unique at line 29, column 1: category: Communication homepage: "" ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 168 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary_zh" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
Process rating: all ten parameters 51/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
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (email-daily-summary) differs from the folder (email-digest-free)
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 60 steps
- 100Execution cost. Instruction body is 2414 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 15 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 168: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.