SKILLEMALL.ai
GitHub ↗ RU Sign in

CD Calendar

创建日历事项, 查询日程, 分析忙闲和空闲时间。

The skillemall take

The skill promises to create calendar events, query schedules, and analyze busy versus free time. Three files, no scripts, 610 body tokens. Quality scores are modest: 49 for quality, 48 for process out of 100. No critical findings, but no medium-level issues documented either—either there weren't any or testing was skipped. No model run, no sandbox test. Supports Claude, Cursor, and a dozen other platforms, but without actual verification it's unclear how reliably it parses calendar data or calculates free slots.

Install it if calendar operations aren't mission-critical and you're willing to patch as you go. If you need stable schedule handling, wait for a version with higher scores and at least one model run.

kellyvv/PhoneClaw Agent Skills author: kellyvv 3 files body ≈ 610 tokens Open the sourcegithub.com↗ analyzed 4 d ago

创建日历事项, 查询日程, 分析忙闲和空闲时间。

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

ProcedurePersonal productivitytype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
49
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "name-zh"
  • note frontmatter-key unknown frontmatter key "icon"
  • note frontmatter-key unknown frontmatter key "disabled"
  • note frontmatter-key unknown frontmatter key "type"
  • note frontmatter-key unknown frontmatter key "requires-time-anchor"
  • note frontmatter-key unknown frontmatter key "chip_prompt"
  • note frontmatter-key unknown frontmatter key "chip_label"
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "side_effects"
  • note frontmatter-key unknown frontmatter key "examples"

Process rating: all ten parameters 48/100

  • 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
  • 30Running it twice. 2 mutating operations with no state check
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 39 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 610 tokens
  • low The response is described with custom markup (4 tags): a typed call is more reliable

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 24: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 39 items

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