ClaudeSuperPower
SubmitLog in

scheduler-and-booking-design

Skill

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

0Productivity

Install

git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/scheduler-and-booking-design

What is 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.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~183 tokens of context used while enabled, before you invoke anything

Documentation

README · ~10 min read

Scheduler and Booking Design

A senior growth practitioner's playbook for designing meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic booking link. Availability logic, qualification gating, prep automation, follow-up sequencing. The discipline of building a scheduler that earns the booking by earning a better call.

Most schedulers fail in one of two ways. Generic booking links produce cold demos where reps know nothing about the person they are about to talk to. Conversion stays at the rate of unqualified raw demos. Or qualification forms with 12 fields scare users off before they can book; drop-off at the form approaches 90 percent; only the leads who happen to survive the form actually convert.

The schedulers that work do something different. Just enough qualification to set up the call well (3-5 strategic fields), context-aware availability (high-fit leads see senior reps; low-fit leads route differently), prep automation that briefs the rep before the call. The booking is honest about who the audience is; the call is set up to succeed.

The voice is the senior growth practitioner who has watched schedulers double demo conversion when redesigned and watched them collapse when more qualification was added. Practical, opinionated about which fields earn their place, willing to call out when the booking flow is the wrong tool.

When to use this skill: scoping a scheduler for the first time, auditing a booking flow with poor conversion or poor downstream call quality, designing the qualification gate that produces context without producing friction, or deciding routing logic that matches leads to the right reps.

What this skill covers

This skill spans meeting schedulers and booking experiences across acquisition and sales contexts. The growth-tooling distinctions:

  • multi-step-form-design is pre-signup data capture (forms before the user has access to anything). This skill is meeting-booking specifically; qualification fields exist but the goal is the call, not the data.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

obsidian-skills

Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.

43.6K stars

command-development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs gu

32.8K stars

plugin-settings

This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin

32.8K stars