calendar

Calendar management and scheduling. Create events, manage meetings, and sync across calendar providers.

Quality

23%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/calendar/SKILL.md

Quality

Discovery

32%

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

The description provides a reasonable overview of calendar-related capabilities but suffers from missing explicit trigger guidance ('Use when...'), which is critical for skill selection. It names the domain and some actions but lacks the comprehensive action list and natural trigger terms that would make it highly effective for skill matching.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to schedule, book appointments, check availability, or manage calendar events'

Include more natural trigger terms users would say: 'appointment', 'book a meeting', 'schedule a call', 'free time', 'availability', 'Google Calendar', 'Outlook'

Expand the action list to be more comprehensive: 'Create, edit, and delete events, check availability, set reminders, handle recurring meetings, manage invitations'

Dimension	Reasoning	Score
Specificity	Names the domain (calendar management) and some actions (create events, manage meetings, sync), but lacks comprehensive detail about specific capabilities like editing events, setting reminders, checking availability, or handling recurring events.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'calendar', 'events', 'meetings', 'scheduling', and 'sync', but missing common variations users might say such as 'appointment', 'schedule a call', 'book a meeting', 'availability', or specific provider names like 'Google Calendar'.	2 / 3
Distinctiveness Conflict Risk	Calendar management is a reasonably specific domain, but 'scheduling' and 'meetings' could overlap with other skills like email management, project management, or communication tools. The mention of 'calendar providers' helps distinguish it somewhat.	2 / 3
	Total	7 / 12 Passed

Implementation

14%

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

This skill is essentially a feature list masquerading as documentation. It tells Claude what the skill can do but provides zero guidance on how to actually accomplish any of the listed tasks. There are no API calls, no tool usage patterns, no code examples, and no workflows for any of the three calendar providers mentioned.

Suggestions

Add executable code examples showing how to create events, query availability, and manage meetings for at least one provider (e.g., Google Calendar API calls)

Define clear workflows with validation steps for multi-step operations like 'schedule a meeting with multiple attendees' or 'sync calendars across providers'

Create separate reference files for each provider (GOOGLE.md, OUTLOOK.md, APPLE.md) and link to them from the main skill

Replace natural language 'Usage Examples' with actual tool invocations or API call patterns that Claude should use

Dimension	Reasoning	Score
Conciseness	The content is brief but lacks substance - it's concise by omission rather than efficiency. The feature list and provider list add little value without actionable guidance.	2 / 3
Actionability	No concrete code, commands, or executable guidance provided. The 'Usage Examples' are natural language prompts, not actionable instructions for how Claude should actually interact with calendar APIs or tools.	1 / 3
Workflow Clarity	No workflows defined at all. Creating events, scheduling meetings, and syncing calendars are multi-step processes that require clear sequences, but none are provided.	1 / 3
Progressive Disclosure	Content is a shallow overview with no references to detailed documentation. For a skill covering multiple providers and features, there should be links to provider-specific guides or API references.	1 / 3
	Total	5 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: 45f9fac

Reviewed: 27 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.