What problem does it solve?
The booking Skill documents and explains the booking service that wraps the reverse-engineered Eversports API, removing guesswork when integrating court reservation, cancellation, and slot discovery into the squash-bot ecosystem.
Core Features & Use Cases
- Eversports client semantics: cookie-based session management, login retry via withAuth, and special 401 handling for CreateBooking.
- Serialized booking flow: CreateBooking is a 5-step, mutex-serialized operation to avoid duplicate reservations and to surface best-effort tracking without aborting successful bookings.
- HTTP API and per-credential dispatch: exposes health/version endpoints and a set of authenticated routes for matches, courts, slots, and facility lookups, with support for per-account client caching.
- Operational constraints: timezone-aware RFC3339 timestamps using facility local offsets, environment-driven configuration, and HTML parsing of calendar pages.
- Use Case: Integrate this Skill when adding or modifying booking logic, implementing auto-booking cron jobs, or troubleshooting booking failures caused by session, credential, or timezone issues.
Quick Start
Ask the booking skill to summarize the CreateBooking flow, required headers and credentials, retry and serialization behavior, and the timezone handling you must apply when calling the booking API.