meeting-scheduler-helper
Meeting Scheduler Helper - Auto-activating skill for Business Automation. Triggers on: meeting scheduler helper, meeting scheduler helper Part of the Business Automation skill category.
33
0%
Does it follow best practices?
Impact
95%
1.01xAverage 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/meeting-scheduler-helper/SKILL.mdQuality
Discovery
0%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 with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It fails on every dimension of the rubric.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Schedules meetings by checking participant availability, sending calendar invites, resolving time zone differences, and booking conference rooms.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to schedule a meeting, find available time slots, send a calendar invite, book a room, or coordinate attendees.'
Remove the duplicate trigger term and replace with diverse natural keywords users would actually say, such as 'schedule', 'meeting', 'calendar', 'availability', 'book', 'invite', 'time slot'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Meeting Scheduler Helper') and its category ('Business Automation') without describing what it actually does—no mention of scheduling, calendar management, conflict resolution, or any specific capabilities. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of functionality beyond the skill name and category label. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'meeting scheduler helper' repeated twice, which is the skill's own name rather than natural keywords a user would say. Missing obvious terms like 'schedule a meeting', 'book a room', 'calendar', 'availability', 'invite', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any calendar, scheduling, or business automation skill. 'Business Automation' is extremely broad and provides no distinguishing detail. | 1 / 3 |
Total | 4 / 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/placeholder with no actual content. It repeatedly references 'meeting scheduler helper' without ever defining what that means, how to do it, or providing any actionable guidance. Every section is generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable code or commands for actual meeting scheduling tasks (e.g., calendar API integration, parsing availability, generating invite emails).
Define a clear workflow with specific steps, such as: 1) Parse participant availability, 2) Find overlapping time slots, 3) Generate calendar invite, 4) Send confirmation — with validation at each step.
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content like code examples, input/output formats, and specific tool usage.
Include at least one complete, copy-paste-ready example showing input (e.g., participant schedules) and expected output (e.g., a scheduled meeting object or calendar invite).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'meeting scheduler helper' excessively, and provides zero substantive information about how to actually schedule meetings. | 1 / 3 |
Actionability | There are no concrete steps, no code, no commands, no examples of inputs/outputs, and no specific guidance. Every section is vague and abstract — '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. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize. | 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.