BF schedule-manager
日程任务管理 - 查看/添加/修改/删除定时任务和临时提醒
As a process F 33/100 · Will not run — References files that are not bundled: ../../daily-tasks.md, ../../scripts/run-task.sh, ../../calendar/README.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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 Dangerous commands
cmd-cron-mentionscripts/schedule.py:166Mentions editing / listing crontab (string literal in code, not executed)"# 编辑:crontab -e",
code literal -
low Dangerous commands
cmd-cron-mentionscripts/schedule.py:167Mentions editing / listing crontab (string literal in code, not executed)"# 查看:crontab -l",
code literal -
low Dangerous commands
cmd-cron-mentionSKILL.md:266Mentions editing / listing crontabcrontab -l
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: ../../daily-tasks.md - warning
missing-refreference to a missing file: ../../scripts/run-task.sh - warning
missing-refreference to a missing file: ../../calendar/README.md
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: ../../daily-tasks.md, ../../scripts/run-task.sh, ../../calendar/README.md
- 0Tools and files. 3 referenced file(s) missing: ../../daily-tasks.md, ../../scripts/run-task.sh, ../../calendar/README.md
- 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
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1172 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)
- +3Description length 29: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -215 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 23 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (15 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 50.
External checks
ClawHub: suspicious
The skill appears to be a task/reminder scheduler, but it can modify the user's crontab and send reminder content to Feishu with incomplete safety disclosure.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026