CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 conceptual playbook: sections are summaries that hand off to real, one-level-deep reference files; the guidance is specific and actionable (field rules, routing tiers, reminder cadences, a 12-step audit framework) despite containing no code, which is appropriate for this skill type. The main cost is verbosity — the keystone framing and closing recycle the same material, and the meta 'voice' paragraph adds tokens without adding instruction.

Suggestions

Cut the repeated restatements of the any-time-friction / interrogation-gate / qualified-fast-path framing — it appears in full in the intro, the keystone section, and the closing; state it once in the keystone section and reference it elsewhere.

Remove or compress the 'The voice is the senior growth practitioner...' paragraph — it describes the skill's tone rather than instructing the reader, adding tokens without actionable content.

Tighten the closing section, which currently restates the full framework and all 12 considerations already listed in 'The framework' section; a short synthesis paragraph would preserve the point at a fraction of the length.

DimensionReasoningScore

Conciseness

Mostly efficient — dense pattern lists with no basic-concept padding — but the keystone framing (any-time-friction / interrogation-gate / qualified-fast-path) is repeated nearly verbatim in the intro, its dedicated section, and the closing, and the 'The voice is the senior growth practitioner' paragraph describes tone rather than instructing, so the body could be tightened.

3 / 5

Actionability

Concrete, specific guidance throughout — the five-field rule, strong vs weak field lists, routing tiers ('SMB to SDRs, mid-market to AEs, enterprise to senior AEs'), reminder cadences ('24 hours and/or 1 hour'), and a 12-consideration audit framework with failure-mode diagnoses — which satisfies the instruction-only standard; minor gaps remain, e.g., no worked example of a qualified booking flow.

4 / 5

Workflow Clarity

There is a clear sequence (booking-flow decision first, then the 12 ordered considerations) with checkpoints like the litmus test ('Does the rep arrive at the call already knowing the prospect's situation?') and a quarterly audit; it falls short of a 5 because there is no explicit validate-and-correct feedback loop for the audit process.

4 / 5

Progressive Disclosure

The body is a well-organized overview where each section summarizes a topic and links to a one-level-deep reference file — all 9 referenced files exist in references/ — plus a consolidated 'Reference files' index; content is appropriately split and easy to navigate. It fits the 5 anchor better than 4 because content placement is clean, with only the trivial nit that scheduler-anti-patterns.md appears only in the index section.

5 / 5

Total

16

/

20

Passed

Description

88%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 description: concrete capability list, explicit and multi-trigger 'when' guidance in third person, and a clearly staked-out niche. Trigger coverage is broad and includes situational triggers beyond keyword matching. The only weaknesses are a couple of missing natural trigger variations and slight overlap risk with adjacent qualification/form-design skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'Availability logic, qualification gating, prep automation, follow-up sequencing' plus 'qualify leads, set up calls well, and convert at higher rates' — giving comprehensive coverage of the skill's capabilities, matching the score-5 anchor rather than the 4 anchor's 'minor gaps in coverage'.

5 / 5

Completeness

It explicitly answers both what ('Designing meeting schedulers and booking experiences that qualify leads...') and when ('Triggers on... Also triggers when...') with concrete trigger phrases, matching the score-5 anchor exactly.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would say ('scheduler design, meeting booking, demo scheduling, sales call scheduling, calendar tool, booking page') plus scenario triggers ('when sales team complains about cold demos'), but a few common variations like 'book a demo' or 'set up a call' are missing, placing it just below the comprehensive-coverage anchor.

4 / 5

Distinctiveness Conflict Risk

The scheduler/booking niche is distinct with dedicated triggers, but 'qualification flow' and the lead-qualification framing carry minor overlap risk with closely related form-design and lead-gen skills, fitting the 'mostly distinct; minor overlap risk' anchor rather than 'minimal conflict risk'.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.