calendar-event-creator
Calendar Event Creator - Auto-activating skill for Business Automation. Triggers on: calendar event creator, calendar event creator Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/calendar-event-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak—it is essentially a skill name repeated with boilerplate category metadata. It provides no concrete actions, no natural trigger terms users would say, and no explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates calendar events, sets reminders, parses natural language dates and times, and generates .ics files.'
Add a 'Use when...' clause with natural trigger terms like 'schedule a meeting', 'add to my calendar', 'create an appointment', 'book a time slot', 'set a reminder', '.ics file'.
Remove the duplicated trigger term and replace with diverse, natural user phrases that would actually appear in requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Calendar Event Creator') but provides no concrete actions. There is no mention of what specific operations it performs—e.g., creating events, setting reminders, parsing dates, integrating with calendar APIs. It is essentially just a label repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond its name and does not provide any explicit 'when to use' guidance. The 'Triggers on' line just repeats the skill name and does not constitute meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'calendar event creator' repeated twice. It misses natural user phrases like 'schedule a meeting', 'add to my calendar', 'create an appointment', 'book a time slot', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'calendar event' is somewhat specific to a niche (calendar/scheduling), which reduces conflict with unrelated skills. However, the lack of detail means it could overlap with other scheduling or calendar-related skills without clear differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It repeatedly names 'calendar event creator' without ever defining what that means, how to do it, or what tools/APIs/formats are involved. It provides zero actionable guidance and would not help Claude perform any task.
Suggestions
Add concrete, executable code examples showing how to create calendar events (e.g., using Google Calendar API, .ics file generation, or Microsoft Graph API with specific code snippets).
Define a clear workflow with steps: parse event details from user input, validate required fields (date, time, title), generate the event in the target format, and verify the output.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than providing actionable instructions.
Include specific input/output examples showing what a user request looks like and what the generated calendar event should contain (e.g., an .ics file format or API request body).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'calendar event creator' excessively, and provides zero substantive information about how to actually create calendar events. | 1 / 3 |
Actionability | There are no concrete steps, no code examples, no commands, no API references, and no executable guidance whatsoever. The skill describes what it claims to do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The 'step-by-step guidance' mentioned in capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to disclose progressively. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.