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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill meeting-scheduler-helperOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It provides only a skill name, a vague category label, and redundant trigger terms that repeat the skill name. There are no concrete actions, no natural user language triggers, and no guidance on when Claude should select this skill.
Suggestions
Add specific concrete actions the skill performs, such as '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, like 'schedule a meeting', 'book a call', 'find a time to meet', 'calendar availability', 'set up a meeting'
Specify what makes this skill distinct from general calendar or automation skills, such as which platforms it integrates with or what specific scheduling scenarios it handles
| 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 so generic that it provides no clear niche. 'Business Automation' could overlap with countless other skills, and without specific capabilities or triggers, Claude cannot distinguish when to use this over other scheduling or automation tools. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content. It contains only generic boilerplate text that could apply to any skill, with no specific guidance on meeting scheduling, calendar APIs, or automation workflows. The content provides zero actionable value.
Suggestions
Add concrete code examples showing how to interact with calendar APIs (Google Calendar, Outlook, etc.) to create, read, and update meetings
Define a clear workflow with steps: check availability, propose times, send invites, handle conflicts, confirm attendance
Include specific input/output examples showing meeting request format and expected calendar event structure
Remove all generic boilerplate text and replace with actual meeting scheduling logic and constraints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 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 schedule a meeting or interact with any calendar system. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only describes vague capabilities without any process guidance. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to external files, examples, or deeper documentation exist. | 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.