calendar-ops-skill

Triggers when the user wants to query or modify real calendar data: checking today's or this week's agenda, spotting conflicts, creating meetings, rescheduling, or deleting events. Typical phrasings include "what time is my meeting tomorrow", "book xx for me", or "schedule a meeting". **Do not use for**: casually mentioning times or countdowns in conversation (→ answer directly), or recurring background jobs like "run this script at 9am every day" (→ schedule-ops-skill).

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clear, actionable skill body with strong workflow sequencing and validation checkpoints for destructive operations. The main improvement opportunities are trimming a few rhetorical 'Why?' lines and adding at least one complete tool-call argument example.

Suggestions

Trim non-essential rationales (e.g. 'double-booking wastes everyone's time and makes the user look unprofessional') to keep only the operational reason, improving token efficiency.

Add one fully-formed CalendarMutate create payload example (with sourceId, kind, start/end ISO timestamps, and timezone offset) so the most common action is copy-paste ready.

Consider moving the 'Common Pitfalls' detail into a brief reference file and keeping only the top risks inline, which would sharpen progressive disclosure now that the body runs long.

Dimension	Reasoning	Score
Conciseness	The body is lean with tool tables and short 'Why?' rationales that mostly earn their tokens; minor padding (e.g. 'double-booking wastes everyone's time and makes the user look unprofessional') could be trimmed without losing guidance.	4 / 5
Actionability	Gives concrete commands (`date '+%Y-%m-%dT%H:%M:%S%z'`), specific tool modes, and field values (allDay: true, kind: event\|reminder) with ISO 8601 offset examples; full copy-paste argument payloads are not provided, leaving a minor gap.	4 / 5
Workflow Clarity	Paths A–E are clearly numbered and sequenced with explicit validation checkpoints — conflict checks before create, user confirmation before delete, 'Never silently skip the conflict', and listing candidates for ambiguous matches — including feedback loops for destructive operations.	5 / 5
Progressive Disclosure	Well-organized with clear section headers (Tool Roster, Decision Flow, Common Pitfalls, Tool Cheat Sheet) and no bundle files to navigate; the body exceeds the simple-skill line and is multi-purpose, so it does not fully qualify for the single-purpose exception.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that concretely enumerates capabilities, supplies natural trigger phrasings, and draws explicit negative boundaries against a sibling skill. Trigger term coverage is the only minor soft spot, missing a few common synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'checking today's or this week's agenda, spotting conflicts, creating meetings, rescheduling, or deleting events' — giving comprehensive coverage rather than just naming the domain.	5 / 5
Completeness	Explicitly answers both 'what' (query/modify calendar data, agenda, conflicts, create/reschedule/delete) and 'when' with concrete trigger phrasings, plus a 'Do not use for' negative boundary.	5 / 5
Trigger Term Quality	Includes natural phrasings users actually say ('what time is my meeting tomorrow', 'book xx for me', 'schedule a meeting') plus synonyms like 'agenda' and 'conflicts'; a few common variations (e.g. 'what's on my calendar') are absent, so it sits just below fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche with explicit boundary guidance distinguishing it from schedule-ops-skill and casual time mentions, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: itsablabla/openloaf-web
Path: apps/server/src/ai/builtin-skills/calendar-ops/en/SKILL.md
Commit: a1ab5be

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.