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 in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates calendar events from natural language descriptions, sets reminders, specifies attendees, and handles recurring schedules.'
Add a 'Use when...' clause with natural trigger terms like 'schedule a meeting', 'add to my calendar', 'book an appointment', 'set a reminder', 'create an event', 'recurring meeting'.
Remove the duplicated trigger term and replace with diverse, natural user phrases that cover common variations of how users request calendar-related tasks.
| 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 the name itself, and there is no 'when should Claude use it' guidance. The 'Triggers on' line just repeats the skill name and provides no meaningful trigger context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'calendar event creator' repeated twice. There are no natural user phrases like 'schedule a meeting', 'add to my calendar', 'book an appointment', 'set up a reminder', or file/format references that users would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'calendar event' is somewhat specific to a niche (calendar/scheduling), which provides some distinctiveness. However, the lack of concrete actions or explicit scope means it could overlap with other scheduling or automation skills. | 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 a hollow placeholder with no substantive content. It repeatedly describes itself in abstract terms without providing any actual instructions, code, examples, or workflows for creating calendar events. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable code examples for creating calendar events (e.g., using Google Calendar API, ICS file generation, or Microsoft Graph API with specific code snippets).
Define a clear multi-step workflow: gather event details → validate inputs → create event via API → confirm creation, with error handling at each step.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual implementation guidance, input/output formats, and working examples.
Include specific input/output examples showing what a user request looks like and what the generated calendar event should contain (e.g., ICS format, API payload JSON).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill supposedly does without providing any actual instructions, code, or concrete guidance. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of calendar event creation. The 'capabilities' section lists abstract claims like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just vague promises of 'step-by-step guidance' that never materialize. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no quick-start section, and no navigation to deeper content. The sections are superficial headers over redundant text. | 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
3e83543
- 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.