scheduler-and-booking-design
Designing meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic Calendly link. Availability logic, qualification gating, prep automation, follow-up sequencing. Honest about any-time-friction (no qualification, just a booking link), interrogation-gate (so much qualification it scares users off), and qualified-fast-path (just enough qualification to set up the call well) patterns. Triggers on scheduler design, meeting booking, demo scheduling, sales call scheduling, calendar tool, booking page, qualification flow. Also triggers when sales team complains about cold demos, when booking conversion is poor, or when scheduler is being scoped for the first time.
53
60%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/scheduler-and-booking-design/SKILL.mdQuality
Discovery
100%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 a strong, well-crafted skill description that clearly defines its niche in meeting scheduler and booking experience design with a sales qualification focus. It excels across all dimensions with specific actions, comprehensive trigger terms including situational triggers, explicit 'when' guidance, and a distinctive domain. The named anti-patterns and design patterns add valuable specificity that aids both selection accuracy and user understanding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: designing meeting schedulers, qualification gating, prep automation, follow-up sequencing, availability logic. Also names specific patterns (any-time-friction, interrogation-gate, qualified-fast-path) which add concrete detail. | 3 / 3 |
Completeness | Clearly answers both 'what' (designing meeting schedulers with qualification gating, prep automation, follow-up sequencing) and 'when' (explicit 'Triggers on...' clause with multiple trigger terms and situational triggers like poor booking conversion or first-time scoping). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'scheduler design', 'meeting booking', 'demo scheduling', 'sales call scheduling', 'calendar tool', 'booking page', 'qualification flow', 'cold demos', 'booking conversion'. Also includes situational triggers like 'sales team complains about cold demos' which are realistic user scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a very clear niche: meeting scheduler design with lead qualification focus. The specific patterns named (any-time-friction, interrogation-gate, qualified-fast-path) and the sales/booking context make it highly unlikely to conflict with generic calendar or scheduling skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a verbose thought-leadership essay on scheduler design philosophy rather than an actionable skill file. It repeatedly restates its core trichotomy, explains concepts Claude already knows, and provides no concrete templates, code, decision trees, or copy examples. The progressive disclosure structure is well-intentioned with 9 reference files, but the main file duplicates much of what should be in those references while the references themselves don't exist.
Suggestions
Cut the body by 60%+ by removing repeated explanations of the any-time-friction/interrogation-gate/qualified-fast-path framing, the closing restatement, and concept definitions Claude already knows.
Add concrete, actionable artifacts: a qualification form template with example fields and routing rules, a sample prep automation brief format, example reminder email copy, and a routing decision tree.
Move detailed pattern descriptions (availability logic, routing patterns, prep automation patterns) entirely into the referenced files and keep only a 1-2 line summary with link in the main skill.
Add validation checkpoints to the 12-consideration framework, such as 'After step 3, verify each field either routes or preps—remove any that do neither' to create a true workflow with feedback loops.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose for a skill file. Extensive philosophical framing, repeated restatements of the same concepts (the any-time-friction vs interrogation-gate vs qualified-fast-path trichotomy is explained at least 3 times), and explanations of concepts Claude already understands (what round-robin is, what a no-show is). The closing section restates the entire skill. Much of this content is descriptive rather than instructive. | 1 / 3 |
Actionability | No concrete code, commands, templates, or executable examples anywhere. The content describes concepts and patterns at a high level but never provides specific artifacts like a qualification form template, a routing logic decision tree, a prep automation script, or example reminder email copy. It reads as a thought-leadership essay rather than actionable instructions Claude can execute. | 1 / 3 |
Workflow Clarity | The 12-consideration framework provides a reasonable checklist sequence for designing or auditing a scheduler, and the failure modes section offers diagnostic patterns. However, there are no validation checkpoints, no explicit decision gates between steps, and no feedback loops for error recovery. The workflow is more of a consideration list than a step-by-step process. | 2 / 3 |
Progressive Disclosure | References to 9 separate reference files are well-organized and clearly signaled with one-level-deep links. However, no bundle files are provided, so all those references are broken/empty. The main file itself is excessively long with content that should have been pushed into those reference files rather than partially duplicated in the body. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- rampstackco/claude-skills
- Commit
8e70d03
- 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.