slot-engine

Compute deterministic available time slots from schedules and booking constraints.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/andrmaz/blend --skill slot-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slot-engine
Source: https://github.com/andrmaz/blend/tree/main/packages/scheduling/docs/skills/slot-engine
Command: npx skills add https://github.com/andrmaz/blend --skill slot-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Slot engine computes available time slots for events given a schedule, busy intervals, and capacity constraints, enabling deterministic planning without manual checking.

Core Features & Use Cases

  • Deterministic slot generation: compute open slots from a weekly schedule, time zone, and buffers.
  • DST-safe, timezone-aware calculations: convert to UTC using the schedule's timezone before arithmetic and handle daylight saving changes.
  • Constraint enforcement: respect busy intervals, schedule availability, and per-slot booking limits to avoid overbooking.
  • Use Case: schedule a recurring meeting window across multiple days while avoiding conflicts and time-zone drift.

Quick Start

Provide a schedule, busy intervals, and a target time range to obtain available slots.

Frequently Asked Questions about slot-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compute available time slots from a weekly schedule across multiple timezones?

Available time slots are generated by validating a weekly schedule against busy intervals and capacity constraints. The engine performs DST-safe UTC conversion for the schedule's timezone before applying per-slot validation against overlaps and past times.

How do I prevent overbooking when scheduling events with per-slot capacity limits?

Preventing overbooking requires enforcing per-slot capacity limits during slot generation. The engine validates each slot against booking constraints and outputs seatsRemaining to indicate remaining capacity within each available time window.

Does the slot engine handle daylight saving time transitions when generating availability?

The slot engine handles daylight saving time by applying DST-safe UTC conversion using the schedule's specified timezone. This ensures deterministic slot generation remains accurate even when DST boundaries shift within the target date range.

Can I add buffer times between available slots to account for meeting transitions?

Buffer times are supported during slot generation to create gaps between available time windows. The engine applies buffers alongside schedule availability and busy intervals to ensure slots include required transition time between meetings.

What's the best way to generate deterministic availability for recurring meetings?

Generating deterministic availability requires supplying a weekly schedule, timezone, busy intervals, and date-range limits. The engine applies invariant checks and per-slot validation to produce consistent, reproducible Slot objects across multiple days.

Why are my available slots showing incorrect times after a timezone conversion?

Incorrect slot times often result from missing or mismatched timezone data during UTC conversion. The engine requires an explicit schedule timezone to perform DST-safe calculations and ensure slot start and end times remain accurate across date ranges.