Team event types, round-robin assignment, collective bookings, host weights, and no-show calibration.
64
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./packages/scheduling/docs/skills/team-scheduling/SKILL.md| Strategy | How |
|---|---|
lowest-recent-bookings | (Default) host with fewest bookings in past 30d wins; tiebreak by priority, then weight, then email |
weighted | Weighted random pick; deterministic given the same seed |
calibrated | Weighted with no-show penalty (hosts with high no-show rates get fewer) |
Rows in event_type_hosts: {userEmail, isFixed, weight, priority, scheduleId?}. Fixed hosts always attend (like collective within a
round-robin set). Weight scales the relative share. Priority (lower =
higher) breaks ties.
Normally each host's default schedule is used for their slots. A
per-event-type-per-host override is possible via
set-host-availability-override.
OOO hosts are auto-excluded from round-robin for the duration of the OOO
window. Bookings can redirect to the OOO's redirectUserEmail.
event_type_host_groups lets you split hosts into groups — useful for
"collective within each group, round-robin across groups".
| User | Action |
|---|---|
| "Make a sales demo that rotates Alice / Bob / Carol" | create-event-type --schedulingType round-robin --teamId ..., then set-event-type-hosts |
| "Add Dave as a fixed host" | set-event-type-hosts with Dave as isFixed: true |
| "Stop routing to Alice while she's on PTO" | Insert an out_of_office_entries row for Alice's range |
e9a2f0e
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.