CD outlook_calendar
View, create, update, and delete events in the user's Outlook Calendar.
View, create, update, and delete events in the user's Outlook Calendar.
As a process D 41/100 · Unfinished process — References files that are not bundled: <connect_url>, <disconnect_url>
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 · 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-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: <connect_url> - warning
missing-refreference to a missing file: <disconnect_url> - note
frontmatter-keyunknown frontmatter key "icon"
Process rating: all ten parameters 41/100
Will not run. References files that are not bundled: <connect_url>, <disconnect_url>
- 0Tools and files. 2 referenced file(s) missing: <connect_url>, <disconnect_url>
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 9 mutating operations with no state check
- 40Consistency. Frontmatter name (outlook_calendar) differs from the folder (outlook-calendar)
- 50When it triggers. No condition that starts the skill
- 65Failures and branches. 3 branches
- 100Steps. 21 steps
- 100Execution cost. Instruction body is 1232 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 71: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.