BD icloud-calendar
Manage iCloud calendars from natural language. Create, query, update, and delete events on your iPhone calendar via CalDAV. Trigger words: schedule, reminder, meeting, appointment, calendar, event, 日程, 提醒, 会议, 安排, 日历. Supports smart duration inference, auto calendar selection (work/personal), location parsing, keyword-based bulk delete/update, RRULE recurring events.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokentest_add_event.py:214High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)sensitive = 'Secr…xyz'
fixturequoted -
low Secrets in code
secret-high-entropy-tokentest_add_event.py:215High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)eq(sanitize_for_log(sensitive), 'Secr…345' + ELLIPSIS, 'sensitive text truncated at 30 chars')
fixturequoted
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Manage iCloud calendars from natural language. Create, query, upda… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 46/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. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (icloud-calendar) differs from the folder (icloud-cal)
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 43 steps
- 100Execution cost. Instruction body is 1238 tokens
- low 12 top-level sections: this looks like several domains in one skill
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 369: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (8 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.