calendar-event-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill calendar-event-creatorCalendar Event Creator - Auto-activating skill for Business Automation. Triggers on: calendar event creator, calendar event creator Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It only provides the skill name, a redundant trigger phrase, and a generic category label. It completely fails to describe what the skill does or provide meaningful guidance for when Claude should select it.
Suggestions
Add specific actions the skill performs, e.g., 'Creates calendar events, sets reminders, schedules recurring meetings, and generates .ics files'
Include 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'
Specify supported platforms or formats (Google Calendar, Outlook, .ics files) to improve distinctiveness and help users understand the skill's scope
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Calendar Event Creator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating events, setting reminders, managing schedules, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('calendar event creator, calendar event creator'). Missing natural user phrases like 'schedule a meeting', 'add to calendar', 'book appointment', 'set up a call', or file extensions like '.ics'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'calendar event' provides some specificity to distinguish from general document or code skills, but 'Business Automation' is very broad and could overlap with many other automation skills. Without specific actions, it's unclear how this differs from other calendar-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template that provides no actual value. It contains only generic placeholder text describing what a skill should do without any concrete implementation details, code examples, or actionable guidance for creating calendar events. The content would need to be completely rewritten with actual calendar event creation logic.
Suggestions
Add executable code examples showing how to create calendar events (e.g., using Google Calendar API, Outlook API, or iCal format)
Define the specific input format expected (event title, date/time, attendees, etc.) and output format produced
Include a concrete workflow: parse request -> validate inputs -> create event -> confirm success/handle errors
Remove all generic boilerplate text and replace with specific, actionable instructions for calendar event creation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The skill describes what it does in abstract terms but never shows how to actually create a calendar event or what format/API to use. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, validation checkpoints, or process descriptions. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no meaningful structure. There are no references to detailed documentation, examples, or related files that would provide actual implementation guidance. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.