SKILLEMALL.ai
GitHub ↗ RU Sign in

AD schedule-manager

管理用户日程与任务安排。用于以下场景：(1) 用户要求"安排日程""规划任务""帮我排日程"；(2) 用户要求"新增日程""添加任务""记住这个日程"；(3) 用户要求"查看日程""今日安排""明天任务""本周日程""下周日程""本月日程""下月日程"；(4) 用户要求"修改日程""改一下DDL""调整优先级"；(5) 用户要求"完成了""删除日程"。

ClawHub Agent Skills author: H3avySword v1.0.4 MIT-0 4 files body ≈ 777 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
D
39/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. 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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description 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. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (schedule-manager) differs from the folder (schedules-manager)
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 100Steps. 40 steps
  • 100Execution cost. Instruction body is 777 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

  • +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
  • +5Description quotes 5 example trigger phrases
  • +3Description length 177: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.

External checks

ClawHub: clean
This skill is a straightforward local schedule manager that saves tasks in a workspace CSV file and optionally creates reminders after user confirmation.
LLM: benign (high) · VirusTotal: · 29 May 2026