BC cron-expression-helper
创建、验证和展示cron表达式的工具。当用户需要创建cron表达式、验证cron语法、查看cron表达式的下一次执行时间、或生成最近10个符合cron表达式的时间点时使用。支持标准cron格式（5字段：分钟 小时 日 月 星期）和扩展格式。
As a process C 51/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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Obfuscation
obf-hex-escape-chainscripts/simple_test.py:45Escaped/char-code string obfuscation (test fixture / example file; quoted — discussed, not commanded)if b'\xe8\xa1\xa8\xe8\xbe\xbe\xe5\xbc\x8f\xe8\xa7\xa3\xe9\x87\x8a' in stdout_bytes: # "表达式解释"的UTF-8字节
fixturequoted -
low Obfuscation
obf-hex-escape-chainscripts/simple_test.py:62Escaped/char-code string obfuscation (test fixture / example file; quoted — discussed, not commanded)if b'\xe7\xa4\xba\xe4\xbe\x8b' in stdout_bytes or b'Cron\xe8\xa1\xa8\xe8\xbe\xbe\xe5\xbc\x8f\xe7\xa4\xba\xe4\xbe\x8b' in stdout_bytes:
fixturequoted -
low Obfuscation
obf-hex-escape-chainscripts/simple_test.py:79Escaped/char-code string obfuscation (test fixture / example file; quoted — discussed, not commanded)if b'\xe6\x89\xa7\xe8\xa1\x8c\xe6\x97\xb6\xe9\x97\xb4' in stdout_bytes or b'Cron\xe8\xa1\xa8\xe8\xbe\xbe\xe5\xbc\x8f' in stdout_bytes:
fixturequoted
Files scanned: 10. 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 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 452 tokens
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
- -42 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 120: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: clean
This is a local cron-expression helper with some accuracy and file-save caveats, but no hidden credential access, network use, persistence, or destructive behavior was found.
LLM: benign (high) · VirusTotal: suspicious · 28 May 2026