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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill calendar-event-creator36
Quality
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/calendar-event-creator/SKILL.mdDiscovery
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 essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or natural trigger phrases. The redundant trigger terms and boilerplate category information add no value for Claude's skill selection process.
Suggestions
Add specific actions the skill performs (e.g., 'Creates calendar events with titles, times, locations, and attendees. Supports recurring events and reminders.')
Include a 'Use when...' clause with natural trigger phrases like 'schedule a meeting', 'add to my calendar', 'book an appointment', 'set up a recurring event'
Remove the redundant trigger term and add varied natural language alternatives users would actually say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Calendar Event Creator' without describing any concrete actions. It doesn't explain what the skill actually does (e.g., create events, set reminders, manage invites, sync calendars). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section is just the skill name repeated. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('calendar event creator' repeated twice) and miss natural user phrases like 'schedule meeting', 'add to calendar', 'book appointment', 'set up event', or 'create invite'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'calendar event' is somewhat specific to calendaring functionality, the lack of detail about what distinguishes this from other calendar-related skills (viewing, editing, deleting events) creates potential overlap risk. | 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 essentially a placeholder template with no actual content. It describes capabilities in abstract terms but provides zero actionable guidance for creating calendar events. The entire content could be replaced with a single executable code example that would be far more useful.
Suggestions
Add concrete, executable code showing how to create calendar events (e.g., using Google Calendar API, Outlook API, or ical format)
Include specific input/output examples showing event parameters (title, time, attendees, recurrence) and the resulting calendar entry
Define a clear workflow: 1) Parse event details, 2) Validate required fields, 3) Create event via API, 4) Confirm creation
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual implementation details
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps. The skill describes what it supposedly does but never shows how to actually create a calendar event. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, examples, or supporting documentation. No structure for discovery. | 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 | |
- 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.