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
Quality
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 provides only a skill name and category label without describing any actual capabilities, use cases, or natural trigger terms. Claude would have no meaningful basis for selecting this skill over others or knowing when it applies.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Schedules meetings, checks calendar availability, sends invites, finds optimal meeting times across participants').
Include a 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when the user asks to schedule a meeting, book a call, find available times, or coordinate calendars').
Specify what makes this skill distinct - what calendar systems it works with, what types of meetings it handles, or what unique scheduling capabilities it provides.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Meeting Scheduler Helper' is just a name, and 'Auto-activating skill for Business Automation' is vague category labeling with no actual capabilities described. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use cases or triggers beyond the skill name). Both components are missing or extremely weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'meeting scheduler helper' repeated twice, which is the skill name itself rather than natural user language. Users would say things like 'schedule a meeting', 'book a room', 'find available times', not the skill's technical name. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'Business Automation' could apply to dozens of skills, and 'Meeting Scheduler Helper' provides no specific differentiating details about what kind of scheduling, integrations, or unique capabilities it offers. | 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 content is essentially a placeholder template with no substantive guidance. It repeatedly references 'meeting scheduler helper' without ever explaining what that means or how to accomplish any meeting scheduling tasks. The content fails on all dimensions by providing abstract descriptions instead of actionable instructions.
Suggestions
Add concrete code examples showing how to interact with calendar APIs (Google Calendar, Outlook, etc.) to schedule meetings
Define a clear workflow with specific steps: check availability, propose times, send invites, handle conflicts
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific, actionable guidance
Include example inputs and outputs showing what a meeting scheduling request looks like and what the expected result should be
| 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 examples, no specific commands, and no actual instructions on how to schedule meetings. The content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' no actual steps are present. There are no processes, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 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
0c08951
- 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.