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 is an extremely weak description that consists almost entirely of auto-generated boilerplate. It provides no concrete actions, no natural trigger terms, and no guidance on when Claude should select this skill. It fails on every dimension of the rubric.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Schedules meetings, checks participant availability, sends calendar invitations, finds optimal meeting times across time zones.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to schedule a meeting, find available times, book a conference room, send meeting invites, or coordinate calendars.'
Remove the duplicated trigger term and replace with diverse natural keywords users would actually say, such as 'schedule', 'book', 'calendar', 'availability', 'meeting invite', 'time slot'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Meeting Scheduler Helper') and a category ('Business Automation') without describing what it actually does—no mention of scheduling, calendar management, invitations, 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 natural 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 business automation, calendar, or scheduling skill. There are no distinct triggers or specific capabilities that would differentiate it from other similar skills. | 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 shell with no substantive content. It consists entirely of self-referential meta-descriptions that repeat the phrase 'meeting scheduler helper' without ever defining what that means or providing any concrete instructions, code, or workflows. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to actually schedule meetings (e.g., calendar API integration, email invitation generation, time zone handling).
Define a clear multi-step workflow for the meeting scheduling process, including validation steps such as checking for conflicts and confirming attendee availability.
Remove all meta-description sections (Purpose, When to Use, Example Triggers) that merely restate the skill name, and replace them with actionable instructions Claude doesn't already know.
If the skill involves multiple sub-tasks (e.g., finding available slots, sending invites, handling rescheduling), split them into referenced files with a concise overview in the main SKILL.md.
| 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 inputs/outputs. The skill describes itself in abstract terms without instructing Claude how to actually schedule meetings. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The 'step-by-step guidance' mentioned in Capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to supporting files, and no meaningful structural organization beyond boilerplate headings. | 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
c8a915c
- 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.