AD schedule-manager
本地日程管理系统。当用户提到日程、安排、会议、提醒、行程时使用此技能。 使用 Python + SQLite 在本地管理团队日程，支持增删改查、冲突检测、邮件汇总、钉钉提醒。 注意：所有日程操作通过 schedule_manager.py 完成。
As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ReferenceSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
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 · 0
✓ No critical or high findings
Files scanned: 8. 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 39/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. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (schedule-manager) differs from the folder (smartschedule)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 26 steps
- 100Execution cost. Instruction body is 1399 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
- +1No license
- +2Single-language instructions
- +3Description length 123: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (6 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: suspicious
This scheduling skill is not clearly malicious, but it needs review because it can run in the background and send schedule details to chat or email with unclear controls.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026