CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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).

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 well-structured operational guide: clear decision paths with genuine validation checkpoints for destructive and ambiguous operations, and highly concrete tool guidance. Weaknesses are minor — some rhetorical padding, a duplicated tool table, and the absence of a complete example tool payload.

Suggestions

Drop the Tool Cheat Sheet section (or replace the Tool Roster with it) — it duplicates the roster's tool/mode/action information in a second table.

Add one complete example CalendarMutate create payload (all required fields: sourceId, kind, title, start/end with timezone offset) so creation is copy-paste ready.

Trim editorial asides that add no operational value, e.g. "double-booking wastes everyone's time and makes the user look unprofessional" — the required behavior (check conflicts, never skip) already carries the instruction.

DimensionReasoningScore

Conciseness

Almost entirely operational (exact date command, tool modes, field names), with minor trimmable asides ("double-booking wastes everyone's time and makes the user look unprofessional", "The cost of guessing wrong is far higher than asking once more") and a Tool Cheat Sheet that largely duplicates the Tool Roster table.

4 / 5

Actionability

Gives concrete, executable guidance (exact Bash command, tool modes, actions, field names, ISO 8601 offset examples), but no complete example payload of a full CalendarMutate create call showing the required fields beyond kind/sourceId.

4 / 5

Workflow Clarity

Five clearly sequenced decision paths with explicit validation checkpoints: mandatory conflict check before create ("Never silently skip the conflict and create anyway"), user confirmation before irreversible delete, candidate listing on ambiguous matches, and asking for missing critical fields — with an error-recovery branch (conflict found → suggest nearest free slots).

5 / 5

Progressive Disclosure

Well-organized self-contained single file with clear section headers and no dangling references, but at ~90 lines the pitfalls and cheat-sheet material overlap the decision-flow content and could be consolidated for tighter navigation.

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 description: third-person voice, explicit trigger conditions with verbatim user phrasings, enumerated concrete capabilities, and explicit do-not-use boundaries that deconflict against a sibling skill. The only gap is modest synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Enumerates five concrete actions ("checking today's or this week's agenda, spotting conflicts, creating meetings, rescheduling, or deleting events") under an explicit "query or modify real calendar data" umbrella — comprehensive coverage of the domain, not just several actions with gaps.

5 / 5

Completeness

Explicitly answers both what ("query or modify real calendar data" plus enumerated actions) and when ("Triggers when the user wants to…" with typical phrasings), mirroring the anchor-5 example structure.

5 / 5

Trigger Term Quality

Quotes genuinely natural user phrasings ("what time is my meeting tomorrow", "schedule a meeting", "book xx for me"), but common variants like "check my calendar", "free time", "appointments", or "move/cancel a meeting" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear calendar niche with explicit negative boundaries ("Do not use for… casually mentioning times or countdowns… or recurring background jobs… → schedule-ops-skill"), sharply separating it from the nearest competing skill.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.