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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured practitioner playbook with concrete, opinionated guidance and excellent progressive disclosure through verified reference files. It could be tightened by reducing the repeated keystone-framing prose and the closing manifesto.

Suggestions

Consolidate the any-time-friction / interrogation-gate / qualified-fast-path framing so it is defined once in its keystone section and referenced rather than restated in the intro and closing.

Trim the voice/manifesto prose ("The voice is the senior growth practitioner...", closing section) to reduce token cost without losing the opinionated stance.

Add one short worked example (e.g., a sample 4-field qualification set with matching routing rule) to push actionability from strong guidance toward copy-paste-ready specificity.

Dimension	Reasoning	Score
Conciseness	Largely efficient and assumes Claude's competence, but the any-time-friction/interrogation-gate framing is restated across the intro, keystone section, and closing, and the voice/manifesto prose adds minor padding that could be trimmed.	4 / 5
Actionability	Concrete, specific design guidance throughout (strong vs weak field lists, the five-field rule, four availability patterns with when-to-use, four routing dimensions), though as an instruction-only design skill it stops short of fully worked examples for every case.	4 / 5
Workflow Clarity	The 12-consideration framework and failure-mode diagnostic list provide a clear sequenced walkthrough for auditing or designing a scheduler, but it lacks explicit validation checkpoints/feedback loops (acceptable here since no destructive ops are involved).	4 / 5
Progressive Disclosure	The body is a clear overview with nine well-signaled, one-level-deep references (all verified to exist as real files) and a dedicated Reference files index section; no nested references.	5 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description that concretely names the skill's capabilities, lists natural trigger terms and scenarios, explicitly covers both what and when, and carves out a distinct niche. Minor verbosity in the pattern-illustration clauses does not detract from clarity.

Dimension	Reasoning	Score
Specificity	Names concrete capabilities ("qualify leads, set up calls well", "Availability logic, qualification gating, prep automation, follow-up sequencing") and three concrete named patterns, giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both "what" (designing schedulers/booking flows with the named subsystems) and "when" ("Triggers on... Also triggers when...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms ("scheduler design, meeting booking, demo scheduling, sales call scheduling, calendar tool, booking page, qualification flow") plus scenario triggers ("sales team complains about cold demos", "booking conversion is poor").	5 / 5
Distinctiveness Conflict Risk	Occupies a clear scheduler-and-booking niche with distinct triggers, and the body explicitly distinguishes it from sibling growth-tooling skills, minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Path: skills/scheduler-and-booking-design/SKILL.md
Commit: 0479242

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.