calendar
Calendar management and scheduling. Create events, manage meetings, and sync across calendar providers.
29
23%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/calendar/SKILL.mdQuality
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 identifies a clear domain and lists a few concrete actions, but lacks an explicit 'Use when...' clause which is critical for skill selection. It would benefit from more specific trigger terms (e.g., specific provider names, common user phrases) and a broader enumeration of capabilities to help Claude distinguish this skill from related ones.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to schedule, reschedule, or cancel meetings, check availability, or manage calendar events.'
Include natural trigger terms users would say, such as 'appointment', 'book a meeting', 'schedule a call', 'Google Calendar', 'Outlook', 'availability', '.ics files'.
Expand the list of specific actions beyond 'create events' and 'manage meetings' to include update, delete, check conflicts, list upcoming events, send invitations, etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (calendar management/scheduling) and lists some actions (create events, manage meetings, sync across providers), but 'manage meetings' is somewhat vague and doesn't enumerate specific operations like delete, update, check availability, etc. | 2 / 3 |
Completeness | Describes what the skill does (create events, manage meetings, sync calendars) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'when' is entirely missing, not just implied, bringing it to 1-2 range. Given the rubric guideline, the missing 'Use when' clause caps this at 2, but the 'when' is completely absent so scoring at the lower end. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'calendar', 'scheduling', 'events', 'meetings', and 'calendar providers', but misses common user variations like 'appointment', 'schedule a call', 'book a meeting', 'Google Calendar', 'Outlook', or specific provider names. | 2 / 3 |
Distinctiveness Conflict Risk | Calendar management is a reasonably specific domain, but 'scheduling' and 'meetings' could overlap with project management or communication skills. The mention of 'sync across calendar providers' adds some distinctiveness but without naming specific providers it remains somewhat generic. | 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 placeholder or feature advertisement rather than an actionable skill document. It lists capabilities (create events, schedule meetings, sync calendars) without providing any concrete implementation details, API usage, code examples, authentication patterns, or tool-specific instructions. Claude gains no new knowledge or capability from this content.
Suggestions
Add concrete, executable code examples for at least one provider (e.g., Google Calendar API calls with authentication, event creation payloads, and response handling).
Define a clear workflow for common operations like creating an event: authenticate → check availability → create event → confirm creation → handle errors.
Specify which tools Claude should use (e.g., specific MCP tools, API endpoints, CLI commands) and include exact command syntax or function signatures.
Replace the natural language 'Usage Examples' with actual input/output examples showing the data structures and API calls involved in each operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively short but contains no actionable substance—it's essentially a feature list and marketing-style bullet points. While not verbose in the traditional sense, every token is wasted because none of it teaches Claude anything it doesn't already know about calendars. | 2 / 3 |
Actionability | There is zero concrete, executable guidance. No API calls, no code examples, no specific commands, no tool usage patterns, no authentication flows. The 'Usage Examples' are just natural language prompts, not actionable instructions for how Claude should actually implement calendar operations. | 1 / 3 |
Workflow Clarity | There are no workflows, no step sequences, no validation checkpoints. Creating calendar events, syncing across providers, and managing meetings are multi-step processes that require clear sequencing, but none is provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow document with no references to supporting files, no structured navigation, and no separation of concerns. There are no bundle files to reference, and the skill doesn't organize its (absent) content in any meaningful way. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
81%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
f45fcb5
- 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.